skill-lifecycle-manager
Skill Lifecycle Manager
Manage skill work as a lifecycle, not as isolated one-off edits. This skill is a thin router: it figures out which lifecycle stage matters now, runs only those stages, and hands off deep specialist work to the right sub-skill or helper instead of re-embedding every workflow inline.
The default design bias is:
- Use OpenAI-style structure discipline for authoring, packaging boundaries, and progressive disclosure
- Use Anthropic-style evaluation discipline for realistic test prompts, baseline comparisons when warranted, and separate trigger optimization
- Use repo-local conventions for
skill.json,CHANGELOG.md, categories, generated catalogs, and validation commands
Outputs
Depending on the requested stage, produce one or more of:
- An invocation posture decision for the target skill:
manual-first,hybrid, orauto-first, with rationale - A new or updated skill folder with
SKILL.md,skill.json,CHANGELOG.md, and any required references/scripts/assets - A fusion brief or source inventory explaining what to borrow from existing skills
- A validation report with concrete failures and fixes
- An evaluation plan or iteration workspace path under
workspaces/<skill-name>/ - A seeded evaluation workspace with
with-skilland optionalbaselineslots
More from liqiongyu/my-agents
brainstorming
Manual-first brainstorming workflow for turning ambiguous ideas or competing directions into an approved decision before planning or implementation. Activate when the user explicitly asks to brainstorm, explore options, compare approaches, or pressure-test a direction. Do not activate for clarification, review, detailed planning, or straightforward execution once a direction is already chosen.
10deep-research
Use when the user explicitly asks for comprehensive, citation-backed research such as a deep dive, due diligence, market analysis, or a multi-source comparison/report. Do not activate for quick factual lookups, ordinary coding tasks, or routine content generation unless the user first asks for research or source verification.
7project-documentation
>
6readme-craftsman
Create, update, or review a repository README when the user explicitly asks for README work. Use it to draft a new README, refresh an existing README after project changes, or audit a README against the current repository. Do not use it for general documentation, API docs, architecture docs, or documentation tasks that do not specifically target a README file.
5prompt-engineering
>
5review
>
4