CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable process guidance: every step is backed by exact CLI commands and validation checkpoints, and the verify step's behavioral-intent review is a standout. Weaknesses are minor — slight repetition of the behavioral-fidelity point and a modest length that could be tightened by merging overlapping Guidelines into the Process steps.

DimensionReasoningScore

Conciseness

Lean and competence-assuming — it never explains what facts or implementation are — with only minor trimmable redundancy: behavioral fidelity is stated twice, in step 5's 'Behavioral review' and the Guidelines' 'Behavioral fidelity over literal compliance'.

4 / 5

Actionability

Fully executable throughout: exact commands ('facts list --tags "spec"', 'facts edit <id> --remove-tag "spec" --add-tag "implemented"', 'facts add ... --section domain') plus a concrete example session with fact IDs and a subagent split.

5 / 5

Workflow Clarity

Six clearly sequenced steps with explicit validation checkpoints — 'facts check' before and after implementation, cross-referencing already-passing facts, and 'confirm no @spec facts remain' — plus feedback loops (fix broken validation commands with 'facts edit <id> --command') and explicit handling of ambiguity and impossible facts.

5 / 5

Progressive Disclosure

A single-file skill with no bundle files and no content that clearly belongs in a separate file; sections are well organized (Goal, Process, Guidelines, Example session), but at ~130 lines with some overlap between the Process and Guidelines sections it falls just short of the clean-split top anchor.

4 / 5

Total

18

/

20

Passed

Description

82%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 strong description: it states the concrete lifecycle transition (implement @spec facts in code, tag @implemented) and pairs it with an explicit, multi-phrase 'Use when' trigger clause. The only weakness is that the 'what' covers just two actions and the triggers omit an artifact-level term like '.facts'.

DimensionReasoningScore

Specificity

Names its domain ('@spec facts') and two concrete actions — 'implement them in code, then tag @implemented' — but lists only 1-2 actions, matching the 'not comprehensive' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

Explicitly answers both 'what' ('Operate on @spec facts — implement them in code, then tag @implemented') and 'when' with a concrete 'Use when...' clause listing five trigger phrases.

5 / 5

Trigger Term Quality

Good natural-phrase coverage ('implement facts', 'implement the spec', 'build from the fact sheet', 'make facts true', 'work through unimplemented requirements') with synonyms, but a few natural terms are missing, such as a file-extension/artifact trigger like '.facts'.

4 / 5

Distinctiveness Conflict Risk

Clear niche in the facts lifecycle with implementation-specific triggers ('implement the spec', 'work through unimplemented requirements') that are distinguishable from sibling skills like facts-refine or facts-discover; minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

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
Reviewed

Table of Contents

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.