CtrlK
BlogDocsLog inGet started
Tessl Logo

facts-refine

Operate on @draft facts — collaboratively refine them into precise, actionable @spec facts. Resolve ambiguities, fill gaps, eliminate contradictions, and sharpen labels until every fact is ready to implement. Use when asked to refine facts, clarify the spec, review facts for quality, or "work on facts" with the user.

77

Quality

96%

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

100%

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

A well-structured instruction skill with concrete, executable CLI guidance, a clear multi-step process including validation over destructive operations, and clean single-file organization. It respects Claude's intelligence and avoids concept padding.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept explanations, just the skill-specific issue taxonomy, commands, and rules; every section earns its tokens. Not level 2 because there is no unnecessary explanation to trim.

3 / 3

Actionability

Provides fully executable commands ('facts edit <id> --label ... --remove-tag "draft" --add-tag "spec"', 'facts remove <id>') and a copy-paste-ready example session; not level 2 because the guidance is concrete and complete rather than pseudocode.

3 / 3

Workflow Clarity

Clear 5-step sequence with explicit validation checkpoints ('facts check', 'facts lint', 'Confirm each change landed correctly before moving on') over destructive/batch operations; not level 2 because validation and feedback steps are explicit.

3 / 3

Progressive Disclosure

No bundle files exist; the single file is organized into well-signaled sections (When to use, Process, Guidelines, Example) with no need for external references, satisfying the simple-skill note; not level 2 because organization is clean and navigation is trivial.

3 / 3

Total

12

/

12

Passed

Description

92%

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, specific description with explicit triggers and concrete actions, written in correct third-person imperative voice. Its only weakness is overlap with a sibling facts skill on the broader 'review/work on facts' phrasings, which it does not explicitly disambiguate.

Suggestions

Add a brief disambiguating clause distinguishing this skill from the general facts skill, e.g. 'Use this instead of the facts skill when refining existing @draft facts rather than adding new ones.'

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Resolve ambiguities, fill gaps, eliminate contradictions, and sharpen labels' — matching the 'lists multiple specific concrete actions' anchor; not level 2 because the actions are comprehensive rather than partial.

3 / 3

Completeness

Explicitly answers both what ('Operate on @draft facts — collaboratively refine them into precise, actionable @spec facts') and when ('Use when asked to refine facts...'); not level 2 because the trigger clause is explicit, not merely implied.

3 / 3

Trigger Term Quality

'refine facts, clarify the spec, review facts for quality, or "work on facts"' gives good coverage of natural phrasings a user would say; not level 2 because common variations are well represented rather than missing.

3 / 3

Distinctiveness Conflict Risk

The @draft→@spec lifecycle framing gives a clear niche, but 'review facts for quality' and 'work on facts' overlap a sibling facts skill (the body itself notes 'that's the facts skill's job, not yours') and the description does not disambiguate; not level 3 because the overlap risk is not eliminated, not level 1 because the lifecycle framing is a real niche.

2 / 3

Total

11

/

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.