facts-implement

Operate on @spec facts — implement them in code, then tag @implemented. Use when asked to implement facts, implement the spec, build from the fact sheet, make facts true, or work through unimplemented requirements.

Quality

85%

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

Quality

Content

87%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 well-structured, highly actionable implementation skill with a clear sequenced workflow, explicit validation checkpoints, and copy-paste-ready commands. It is token-efficient and assumes competence, with only minor redundancy between the Process and Guidelines sections.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes Claude's competence, with a few sections (e.g. the behavioral-fidelity guidance repeated in both Process and Guidelines) that could be trimmed for tighter token efficiency.	4 / 5
Actionability	Concrete executable commands (facts list/check/edit/add with exact flag combinations) and copy-paste-ready snippets throughout make the guidance fully actionable across common cases.	5 / 5
Workflow Clarity	A clearly numbered six-step process with explicit validation checkpoints (facts check passing, manual verification per fact, final facts list --tags "spec" confirmation) and feedback loops for batch/destructive transitions, satisfying the verification requirement.	5 / 5
Progressive Disclosure	Well-organized into clear sections with inline commands and a pointed tip referencing facts --help for deeper detail; no bundle files exist so the single-file structure is appropriate, though one-level-deep external references are absent.	4 / 5
	Total	18 / 20 Passed

Description

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

A tight, third-person description with a strong 'Use when' clause and concrete lifecycle-specific actions. It scores well on completeness and trigger quality, with only minor room to broaden action coverage and reinforce distinctiveness from related facts-* skills.

Dimension	Reasoning	Score
Specificity	Concrete actions ('implement them in code, then tag @implemented') name the lifecycle transition precisely, but only one primary action is described rather than a list of several specific operations.	4 / 5
Completeness	It explicitly states both what it does ('implement them in code, then tag @implemented') and when to use it via a clear 'Use when asked to implement facts...' clause with multiple concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrases like 'implement the spec', 'build from the fact sheet', and 'work through unimplemented requirements' are present and relevant, though a few common synonyms or extensions are absent.	4 / 5
Distinctiveness Conflict Risk	The @spec→@implemented lifecycle framing carves a clear niche, though it could marginally overlap with sibling facts-* skills (refine/discover) that share the fact vocabulary.	4 / 5
	Total	17 / 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: av/harbor
Path: .agents/skills/facts-implement/SKILL.md
Commit: 67cbe66

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