aif-archive

Archive completed plans and roadmap milestones. Moves finished plans to the archive directory and optionally trims closed milestones from ROADMAP.md. Use when user says "archive plans", "clean up plans", "archive completed", or "trim roadmap".

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%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.

The body is a thorough, well-sequenced workflow with strong validation for destructive/batch operations. Its weaknesses are length with minor repetition and a monolithic structure that inlines detail a larger skill might split into referenced files.

Suggestions

Consolidate the duplicate collision-check logic (roadmap snapshot vs. archive operation) into a single shared section to trim repetition and tighten conciseness toward a 5.

Extract the Completion Detection Algorithm and ultra-bundle validation rules into a referenced file (e.g., references/completion-rules.md) to improve progressive disclosure and shorten the main body.

Replace the abstract 'YYYY-MM-DD' and git-log fallback for completion-date inference with a concrete copy-paste command example to push actionability to a 5.

Dimension	Reasoning	Score
Conciseness	Dense and operational with no conceptual padding, assuming Claude's competence throughout, but ~340 lines with slightly repetitive collision-check descriptions across the roadmap and archive-operation sections keep it from a clean 5.	4 / 5
Actionability	Provides exact config keys, glob patterns, mv/mkdir commands, frontmatter and comment formats, and templated log/error messages — mostly executable — but date placeholders and a git-log fallback for completion dates are not fully copy-paste ready.	4 / 5
Workflow Clarity	Destructive/batch operations are explicitly sequenced with validation checkpoints: collision checks before moves, ultra-bundle validation before moving, a guard against editing ROADMAP.md unless the snapshot write succeeds, and confirmation gates for --all and --roadmap.	5 / 5
Progressive Disclosure	Well-organized with clear section headers, but as a ~340-line monolithic file with no bundle files or external references, substantial operational detail (completion-detection algorithm, ultra-bundle validation rules) is inlined rather than split out.	3 / 5
	Total	16 / 20 Passed

Description

92%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 is strong: it states concrete capabilities in third person and provides explicit 'Use when' trigger phrases a user would naturally say. The only minor gap is trigger-term coverage leans on exact quoted phrases rather than synonyms and extensions.

Dimension	Reasoning	Score
Specificity	Names three concrete actions — 'Archive completed plans and roadmap milestones', 'Moves finished plans to the archive directory', and 'optionally trims closed milestones from ROADMAP.md' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (archiving plans and trimming roadmap milestones) and 'when' with concrete 'Use when user says...' trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes four natural quoted trigger phrases ('archive plans', 'clean up plans', 'archive completed', 'trim roadmap'), but these are exact phrases rather than a spread of synonyms and file extensions, missing common variations like 'archive done plans' or 'clean up roadmap'.	4 / 5
Distinctiveness Conflict Risk	A clear niche (archiving AI Factory plans / trimming the roadmap) with distinct, skill-specific trigger vocabulary and minimal overlap with related planning skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: lee-to/ai-factory
Path: skills/aif-archive/SKILL.md
Commit: e144f95

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.