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.

75

Quality

92%

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

85%

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

The body is highly actionable with a clear, well-validated workflow and clean single-file organization. Its main weakness is mild verbosity in a few explanatory callouts that restate intent.

Suggestions

Tighten the 'Important' and explanatory callouts (e.g., step 1's 'you need the full picture to make good ordering and grouping decisions') to remove restated intent.

The 'Tip' on CLI aliases could be trimmed or moved to a short reference table, since 'facts --help' already documents them.

Consolidate the repeated manual-fact verification guidance (covered in both steps 4 and 5) into one place to reduce redundancy.

DimensionReasoningScore

Conciseness

Mostly actionable and focused, but several callouts re-explain intent (e.g., the 'Important' notes and 'Read and understand all facts — you need the full picture...') that could be tightened without losing clarity.

2 / 3

Actionability

Concrete, copy-paste-ready commands throughout (facts list/check/edit/add) plus a worked example session leave no ambiguity about what to run.

3 / 3

Workflow Clarity

A clear 6-step sequence with validation checkpoints (facts check at steps 2 and 5) and explicit recovery guidance for ambiguity, impossible facts, and broken commands.

3 / 3

Progressive Disclosure

No bundle files exist and none are referenced; the single file is well-organized into clear sections (Goal, Process, Guidelines, Example), appropriate for a cohesive workflow skill.

3 / 3

Total

11

/

12

Passed

Description

100%

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 concise and concrete, clearly answering both what the skill does and when to use it, with natural trigger phrasings and a distinct niche. No significant weaknesses.

DimensionReasoningScore

Specificity

Lists concrete actions ('implement them in code, then tag @implemented') alongside multiple implementation phrasings, with no vague language.

3 / 3

Completeness

Explicitly states what ('Operate on @spec facts — implement them in code, then tag @implemented') and when ('Use when asked to implement facts...') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Natural phrasings a user would actually say ('implement the spec', 'make facts true', 'work through unimplemented requirements') give good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped to the @spec → @implemented lifecycle with fact-specific triggers, distinguishing it from sibling skills like facts-refine and facts-discover.

3 / 3

Total

12

/

12

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.

Validation16 / 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.