Loading...
Loading...
Found 23 Skills
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
Analyze the current session and propose improvements to skills. **Proactively invoke this skill** when you notice user corrections after skill usage, or at the end of skill-heavy sessions. Also use when user says "reflect", "improve skill", or "learn from this".
This skill should be used at natural checkpoints (after completing complex tasks, at session end, or when friction occurs) to reflect on skill and process execution and identify targeted improvements. Use when experiencing confusion, repeated failures, or discovering new patterns that should be codified into skills for smoother future operation.
Skills retrospective and improvement. Use when: - User asks to "review", "retrospect", "summarize" or "复盘" skills - User wants to analyze skills issues from the conversation - User requests skills optimization or improvement - End of conversation or after significant skill usage
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, generating a personalized growth report with actionable recommendations.
Distill session insights into reusable knowledge: Claude rules, skill improvements, and justfile recipes. Use at the end of a session to capture learnings, update existing artifacts, and avoid reinventing solutions. Prioritizes updating over adding.
Iteratively improve skill frontmatter compliance using the Ralph loop pattern. USE FOR: run sensei, sensei help, improve skill, fix frontmatter, skill compliance, frontmatter audit, improve triggers, add anti-triggers, batch skill improvement, check skill tokens. DO NOT USE FOR: creating new skills (use skill-authoring), writing skill content, token optimization only (use markdown-token-optimizer), or non-frontmatter changes.
Improve an existing prompt or skill with targeted, minimal-diff edits that preserve its core intent, and return the revised artifact plus a short changelog and tradeoffs note. Use this whenever the user wants to refine, sharpen, tighten, or upgrade an existing prompt or skill, asks to "make it better," or wants a small high-leverage edit instead of a full rewrite — even if they don't explicitly mention tuning.
This skill should be used when the user asks to "improve a skill", "make this skill better", "add features to a skill", "this skill is missing something", "upgrade my skill", "what's missing from this skill", "the skill doesn't do X", "make this more useful", or wants to improve skill effectiveness rather than structural correctness. Not for structural fixes — use repair-skill. Not for agents.
Use when reviewing how skills performed during a session, when the user wants to analyze skill invocations and identify improvements, or when the user says "skill retro", "review skills", "how did skills do", "improve this skill", or "skill retrospective".
Analyze coding agent session transcripts to improve existing skills or create new ones. Use when asked to improve a skill based on a session, or extract a new skill from session history.