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

61%

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

65%Weight 40%Scale 1-5

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

A dense, well-structured reference for the skill lifecycle state model that is highly concrete and largely token-efficient. Its main weaknesses are the absence of validation feedback loops around destructive operations and a monolithic structure that inlines detail rather than pointing out to reference files.

Suggestions

Add an explicit validate-fix-retry feedback loop for destructive operations (yank, delete version), e.g. a checklist the agent runs before and after invoking SkillGovernanceService.deleteVersion or yankVersion.

Split the detailed transition, permission, and delete-constraint tables into reference files under references/ and keep SKILL.md as a concise overview that links to them, improving progressive disclosure.

Add a short 'Verify before committing' step to each destructive workflow so validation checkpoints are explicit rather than implied by preconditions.

Dimension	Reasoning	Score
Conciseness	The body is information-dense tables of enum values, transitions, and permissions with no concept-explanation fluff, though the permission-boundaries table mildly repeats information already in the key-transitions table.	4 / 5
Actionability	Concrete enum values, file paths such as domain/skill/SkillStatus.java, and method names like SkillGovernanceService.yankVersion give specific, executable guidance for an instruction-only skill, with only minor gaps (no code snippets, which is appropriate here).	4 / 5
Workflow Clarity	Transition tables and the numbered yank-pointer recalculation sequence are present with delete-version preconditions acting as validation, but there are no explicit validate-to-fix-to-retry feedback loops for destructive operations (yank, delete), which caps the score at 3.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but the skill is entirely monolithic with all detail inlined in SKILL.md and no reference files, so content that could be split out (transitions, permissions, delete constraints) is not progressively disclosed.	3 / 5
	Total	14 / 20 Passed

Description

58%Weight 40%Scale 1-5

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 clearly communicates what the skill covers and carves out a distinct niche, but it omits an explicit 'Use when...' trigger and leans on domain jargon over natural user phrasing. Adding trigger guidance would most improve it.

Suggestions

Append an explicit 'Use when...' clause naming concrete trigger situations, e.g. modifying publish/review/unpublish flows, adding status fields, or implementing hide/yank/archive governance actions.

Soften jargon by adding natural synonyms users would actually say (e.g. 'skill status', 'publishing a skill', 'reviewing a skill') alongside 'container states' and 'visibility overlay'.

Drop the filler adjective 'authoritative' to tighten the opening and free tokens for trigger phrasing.

Dimension	Reasoning	Score
Specificity	The description names the domain and lists several concrete components (container states, version states, review workflow states, visibility overlay, governance actions), with minor gaps; it stops short of score 5 because it enumerates a model's contents rather than concrete actions and 'authoritative' is mild fluff.	4 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent trigger guidance; 'Ensures agents don't introduce invalid states or transitions' is a purpose statement rather than a trigger, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Relevant keywords like 'skill lifecycle', 'review', and 'governance' are present, but terms such as 'visibility overlay' and 'container states' are domain-internal jargon and common natural synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	The skill occupies a clear niche (skill lifecycle governance) and is mostly distinct, with only minor overlap risk against general skill-management skills; it lacks the distinct trigger phrasing needed for a 5.	4 / 5
	Total	14 / 20 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: b896c69

Reviewed: 5 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.