Persona improvement
Skill event4u-app/agent-config/src/skills/persona-improvement
Universal AI Agent OS — audited skills, governance rules, replayable state. One contract, every host agent.
npx -y skills add event4u-app/agent-config --skill persona-improvementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
ONLY when the user explicitly asks to refine a persona from recent corrections — persona analog of skill-improvement-pipeline; tightens a persona's Unique Questions, governance-gated.
SKILL.md
3.8 KB, as published. Nobody here has run it
persona-improvement
The persona analog of skill-improvement-pipeline:
feed a persona a sample of recent corrections/failures where its review lens
should have caught something and didn't, and tighten its Unique Questions
so the lens fires next time. Access ergonomics, not new capability — it only
sharpens an existing persona, never creates one.
When to use
- The user explicitly says "improve / refine this persona" or "the <persona> lens keeps missing X".
- A correction sample exists (review misses, repeated feedback) that a persona's questions should have surfaced.
Do NOT use for:
- Creating a new persona (that is
persona-governance+ the authoring flow). - Editing a persona's identity/scope (a breaking change → new id per
persona-governance). - A one-off miss with no pattern — one anecdote is not a refinement signal.
Procedure
- Gather the correction sample. Collect the recent misses/corrections tied to this persona's domain (from the conversation, feedback notes, or a review log). If fewer than ~3 distinct misses, STOP — no pattern yet; say so.
- Locate the gap. For each miss, name the question the persona should have asked that would have surfaced it. Cluster the misses into ≤ 2 recurring gaps.
- Propose tightened
Unique Questions. Rewrite or add questions that close the gaps — concrete and answerable-from-the-diff, not vague ("does this add a second branch on the same enum?" beats "is the design good?"). Keep the section ≥ 3 questions (persona-governanceschema floor). - Governance gate (mandatory). Before writing, confirm with
persona-governance: the edit is a same-id refinement (not a scope/identity change — those need a new id); the persona keeps ≥ 1 skill citation; the file still passes the skill linter (tier/wing/section/line budget). A scope change is out of scope for this loop. - Apply + verify. Edit only the
Unique Questionssection; run./scripts-run src/scripts/skill_linteron the persona file and confirm 0 errors; show the before/after questions.
Output format
- Correction sample — the ≥ 3 misses, one line each.
- Gaps — the ≤ 2 recurring gaps the misses cluster into.
- Before/after
Unique Questions— the diff, with which gap each new question closes. - Governance confirmation — same-id refinement ✅, ≥ 1 citation intact ✅, linter 0-error ✅.
Gotcha
- The most common misuse is scope creep disguised as refinement: adding
questions that widen the persona into a second domain. That is a new persona
(per the per-domain cap), not a refinement — STOP and route to
persona-governance, do not grow the lens sideways.
Do NOT
- Do NOT refine on a single miss — a pattern needs ≥ 3.
- Do NOT touch identity, scope, tier, or wing — same-id
Unique Questionsonly; anything else is a new-id change underpersona-governance. - Do NOT drop below 3
Unique Questions(schema floor). - Do NOT commit or push — apply the edit locally, surface the diff.
Related Skills
skill-improvement-pipeline— the skill-side analog this mirrors.persona-governance— the four discipline checks this loop is gated by.