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%

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

Highly actionable and well-sequenced content with concrete commands and clear validation checkpoints. Its main weakness is length and redundancy — several key principles (command quality, behavioral-over-structural facts) are restated across multiple sections and could be consolidated.

Suggestions

Consolidate the command-quality guidance: the 'What makes a command meaningful/useless' material in Step 3b overlaps heavily with the Guidelines section — state it once and reference it.

Merge the repeated 'behavioral facts over structural ones' advice (Steps 2, 4, and Guidelines) into a single canonical statement to cut length without losing the point.

Consider extracting the long good/bad command-example blocks into a reference file so the main process flow stays lean, improving token efficiency on every invocation.

DimensionReasoningScore

Conciseness

The body is dense and mostly respects Claude's competence, but at ~300 lines it repeats the same guidance in multiple places — command-quality advice appears in Step 3b and again in Guidelines, and behavioral-over-structural is restated across Steps 2, 4, and Guidelines — which could be tightened.

2 / 3

Actionability

Concrete, executable `facts` commands and real shell examples (both good and bad) appear throughout — e.g. `facts edit <id> --add-tag "implemented"`, `grep -q '^clap' Cargo.toml`, `jq -e '.scripts.test' package.json` — copy-paste ready.

3 / 3

Workflow Clarity

A clear numbered sequence (1→2→2b→3→3b→4→5→6) with validation checkpoints via `facts check` at both the start (Step 1) and the end (Step 6), plus an explicit feedback loop for failing facts.

3 / 3

Progressive Disclosure

A single self-contained file with no bundle references and well-organized sections; there is no nested or deep reference structure to navigate, so organization is appropriate for a cohesive instruction 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.

A strong description: third-person, concise, with concrete actions and an explicit trigger clause covering natural user phrasings. It distinguishes itself clearly from sibling skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Scan the codebase and classify every fact by lifecycle stage", "tag @draft, @spec, or @implemented", "Add missing facts, fix inaccurate ones, remove obsolete ones" — matching the multi-action anchor.

3 / 3

Completeness

It explicitly states what the skill does (scan/classify/tag/add/fix/remove) and provides an explicit "Use when..." trigger clause, satisfying both the what and the when.

3 / 3

Trigger Term Quality

The "Use when" clause covers natural phrasings a user would actually say — "discover facts", "bootstrap or update a fact sheet", "scan the codebase for truths", "sync facts to match the code", "audit the fact sheet for accuracy" — giving strong keyword coverage.

3 / 3

Distinctiveness Conflict Risk

The narrow lifecycle-tagging niche ("@draft, @spec, or @implemented") plus concrete trigger phrasing makes it unlikely to fire for unrelated skills; the body further disambiguates it from the sibling `facts` skill.

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.