skill-lifecycle

The authoritative skill lifecycle state model including container states, version states, review workflow states, visibility overlay, and governance actions. Ensures agents don't introduce invalid states or transitions.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/skill-lifecycle/SKILL.md

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a dense, well-organized reference with concrete file paths, enum values, and transition tables that assume Claude's competence and avoid concept padding. The only gap is the absence of explicit verify-after feedback loops around destructive governance actions.

Dimension	Reasoning	Score
Conciseness	Lean, table-driven reference with no padding or explanations of concepts Claude already knows; the 'Design-vs-code note' and 'Common Pitfalls' add domain-specific value Claude would not infer, so every section earns its place.	3 / 3
Actionability	Highly concrete guidance: exact enum values, file paths (e.g. domain/skill/SkillStatus.java), service methods (SkillGovernanceService.yankVersion), and precise sort orders (publishedAt DESC, then createdAt DESC, then id DESC) — copy-ready for the stated purpose of preventing invalid states.	3 / 3
Workflow Clarity	Sequences are present (the numbered Yank Pointer Recalculation, the Key Transitions table, and documented Delete Version constraints), but destructive operations (yank, delete version) lack explicit verify-after feedback loops, capping workflow clarity at 2 per the destructive-operations guidance.	2 / 3
Progressive Disclosure	Single-file skill with no bundle directories and no nested references; the body is well-organized into clearly headed sections and tables, which warrants a 3 for a self-contained reference with no need for external file references.	3 / 3
	Total	11 / 12 Passed

Description

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific to a clear niche and lists covered components, but it lacks an explicit 'Use when...' trigger clause and leans on technical jargon over natural user phrasings. Adding explicit trigger guidance and natural keyword variations would raise its score.

Suggestions

Add an explicit 'Use when...' trigger clause naming common user situations, e.g. 'Use when modifying skill publish, review, or unpublish flows, or adding skill/version status fields.'

Include natural keyword variations users would actually say (e.g. 'skill states', 'version status', 'review workflow', 'yank/hide/archive a skill') to improve trigger_term_quality.

Drop the over-claim 'authoritative' and reframe the listed categories as concrete capabilities to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete components ('container states, version states, review workflow states, visibility overlay, and governance actions'), but these are category nouns rather than concrete actions, and 'authoritative' is a mild over-claim — closer to the anchor that names domain/some actions than to the multiple-concrete-actions anchor.	2 / 3
Completeness	Clearly answers 'what' (the state model and its covered areas) and states a purpose ('Ensures agents don't introduce invalid states or transitions'), but there is no explicit 'Use when...' trigger clause, so 'when' is only implied — capping completeness at 2 per the guideline.	2 / 3
Trigger Term Quality	Contains relevant domain keywords ('skill lifecycle', 'review workflow', 'governance actions', 'states', 'transitions') but they lean technical and lack common natural variations; no explicit trigger phrasing users would naturally say.	2 / 3
Distinctiveness Conflict Risk	'Skill lifecycle state model' is a clear, narrow niche tied to skill platform governance; it is unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: iflytek/skillhub
Path: .agents/skills/skill-lifecycle/SKILL.md
Commit: ac46ad5

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.