CtrlK
BlogDocsLog inGet started
Tessl Logo

facts

Manage .facts files — atomic, validatable truth statements about a project. Install, check, list, add, edit, remove, and lint facts via the CLI. ALWAYS read this skill when the user mentions facts in any capacity.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/facts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 CLI skill body with clear sequenced workflows and an explicit validation feedback loop, held back only by modest verbosity in the conceptual sections and implicit rather than spelled-out error-recovery loops.

Suggestions

Tighten the conceptual sections (Core idea, Domain vocabulary) to reduce prose while keeping the concrete examples.

Make the error-recovery loop explicit after "facts check" (e.g., a numbered "if a fact fails: fix code or command, re-run check" step) to strengthen the validation feedback loop.

DimensionReasoningScore

Conciseness

The body is efficient and mostly concrete commands with examples; a few conceptual sections (Core idea, Writing good facts, Domain vocabulary) could be tightened but are domain-specific knowledge that earns its place.

4 / 5

Actionability

Provides copy-paste-ready executable commands throughout ("facts ll", "facts check", "facts add \"users can sign up\" --section features/auth") covering the common cases with concrete flags and arguments.

5 / 5

Workflow Clarity

The Agent workflows section gives clearly sequenced procedures (start, define spec, track lifecycle, maintain accuracy) with the "facts check" validation feedback loop, though error-recovery steps are implied rather than spelled out as an explicit numbered retry loop.

4 / 5

Progressive Disclosure

Well-organized into clear sections with no nested references and detailed flag reference delegated to "facts <command> --help"; the single self-contained file is appropriate for a CLI skill, with only minor length that could invite splitting.

4 / 5

Total

17

/

20

Passed

Description

77%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 with a clear what/when structure and a comprehensive action list, weakened mainly by a narrow, generic trigger vocabulary and a broad "in any capacity" trigger that raises conflict risk.

Suggestions

Add natural synonyms or file extensions to broaden trigger coverage (e.g. "fact sheets", ".facts files", "fact-driven development").

Tighten the trigger from "mentions facts in any capacity" to a more specific condition to reduce overlap with casual uses of the word "facts".

DimensionReasoningScore

Specificity

Lists multiple concrete CLI actions — "Install, check, list, add, edit, remove, and lint facts" — giving comprehensive coverage of the skill's capabilities rather than vague language.

5 / 5

Completeness

Explicitly answers both what ("Manage .facts files ... Install, check, list, add, edit, remove, and lint facts via the CLI") and when ("ALWAYS read this skill when the user mentions facts in any capacity") with a concrete trigger phrase.

5 / 5

Trigger Term Quality

The only natural trigger term is "facts" / ".facts files", which is a generic everyday word; no synonyms or file-extension variants are provided beyond the single root term.

3 / 5

Distinctiveness Conflict Risk

The .facts niche is fairly distinct, but the trigger "when the user mentions facts in any capacity" is broad enough that the generic word "facts" could overlap with unrelated conversational uses.

3 / 5

Total

16

/

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.

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.