CtrlK
BlogDocsLog inGet started
Tessl Logo

history-hygiene

Record reconciled final outcomes to history.md, not intermediate requests or obsolete claims

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.copilot/skills/history-hygiene/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is a tight, well-organized behavioral skill that models correct and incorrect entries with concrete examples and no wasted tokens. Its main weakness is that the patterns read as parallel rules rather than an ordered workflow with an explicit validation checkpoint before writing.

DimensionReasoningScore

Conciseness

The ~35-line body is lean with no padding or re-teaching of concepts Claude already knows; every line is either a rule, a correct/incorrect example, or an anti-pattern, matching the 'every token earns its place' anchor.

5 / 5

Actionability

As an instruction-only skill, the guidance is concrete ('Wait for confirmation before writing to history', 'follow the current package.json engines.node requirement') with correct/incorrect examples, but there is no fully executable step-by-step procedure for writing or updating an entry.

4 / 5

Workflow Clarity

For a simple single-purpose skill the rules are unambiguous, but the body lists parallel patterns rather than an explicit reconcile -> confirm -> record sequence with a validation checkpoint, leaving a minor gap.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clear Context / Patterns / Examples / Anti-Patterns sections, which the rubric explicitly allows to score 5.

5 / 5

Total

18

/

20

Passed

Description

53%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 concise and names a specific artifact and action, but it functions as a one-line rule rather than a triggerable skill description. It lacks any 'Use when...' guidance and natural trigger terms, which limits when it would be surfaced.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when writing to history.md, recording project decisions or outcomes, or updating memory/history files after a task completes.'

Include natural trigger terms and synonyms users would say, such as 'history file', 'memory', 'record outcomes', 'log decisions', or 'update history.md'.

List a couple more concrete actions to broaden capability coverage, e.g. 'Update or strike reversed decisions and replace obsolete claims with the current source of truth.'

DimensionReasoningScore

Specificity

The description names the target artifact ('history.md') and one concrete action ('Record reconciled final outcomes'), but stops short of listing several specific actions, matching the anchor for naming a domain with 1-2 concrete actions.

3 / 5

Completeness

It clearly answers 'what' (record reconciled final outcomes to history.md) but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like 'history.md', 'final outcomes', and 'obsolete claims' are present, but there are no natural trigger phrases or synonyms a user would say when needing this skill.

3 / 5

Distinctiveness Conflict Risk

The specific reference to 'history.md' gives it a clear niche with low overlap risk against unrelated skills, though the absence of explicit distinct triggers keeps it from a 5.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
bradygaster/squad
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.