CtrlK
BlogDocsLog inGet started
Tessl Logo

facts-discover

Scan the codebase and classify every fact by lifecycle stage — tag @draft, @spec, or @implemented based on what the code actually shows. Add missing facts, fix inaccurate ones, remove obsolete ones. Use when asked to discover facts, bootstrap or update a fact sheet, scan the codebase for truths, sync facts to match the code, or audit the fact sheet for accuracy.

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

The content is highly actionable with a clear, validated workflow and excellent concrete examples, but it is a long single-file skill with no progressive disclosure — several substantial sections (command-quality heuristics, domain-ontology construction) are inlined rather than split into reference files.

Suggestions

Extract the 'What makes a command meaningful / useless' heuristic block (Process 3b) into a references/commands.md file and link to it one level deep, keeping only the core falsifiability test inline in SKILL.md.

Move the `## domain` ontology construction walkthrough and its example/anti-example blocks into a references/domain.md reference, summarizing the pattern inline.

De-duplicate the 'behavioral facts over structural ones' and 'use domain vocabulary' guidance that recurs across Goal, Process 4, and Guidelines into a single canonical statement.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence, but the 'behavioral over structural' and 'command quality / falsifiability' guidance is restated across the Goal, Process 3b, Process 4, and Guidelines sections, which could be tightened.

4 / 5

Actionability

Provides copy-paste-ready commands throughout — `facts list`, `facts edit <id> --add-tag "implemented"`, concrete grep/test/jq examples for both good and bad commands — plus a full worked example session covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced 6-step process with explicit validation checkpoints (`facts check` at load and again at the end) and a feedback loop (check failures → fix/remove → recheck), with destructive operations (removing facts) given explicit decision guidance.

5 / 5

Progressive Disclosure

The skill is a ~300-line monolith with no bundle files; self-contained material that could live in references (the command-quality guide, the domain-ontology walkthrough) is inlined, and there are no one-level-deep reference links to offload detail.

3 / 5

Total

17

/

20

Passed

Description

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

The description is specific, complete, and well-triggered, naming concrete actions and natural phrases a user would say while explicitly distinguishing the skill from its sibling. It is a model concise description with no vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'classify every fact by lifecycle stage', 'tag @draft, @spec, or @implemented', 'Add missing facts, fix inaccurate ones, remove obsolete ones' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (scan, classify, tag, add, fix, remove) and 'when' with a concrete 'Use when...' clause enumerating trigger scenarios.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms — 'discover facts, bootstrap or update a fact sheet, scan the codebase for truths, sync facts to match the code, or audit the fact sheet for accuracy' — covering the ways a user would actually phrase the request.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (lifecycle classification and sync) and explicitly disambiguates from the related `facts` skill ('If the user says work on facts... use the facts skill instead'), minimizing conflict risk.

5 / 5

Total

20

/

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.