history-hygiene

Record final outcomes to history.md, not intermediate requests or reversed decisions

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

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

The content is a tight, well-organized instruction skill with concrete directives, an explicit confirmation checkpoint, and copy-paste-ready examples, with no padding of known concepts.

Dimension	Reasoning	Score
Conciseness	The body is lean across Context, Patterns, Examples, and Anti-Patterns and does not explain concepts Claude already knows; every section earns its place, matching the score-3 lean-and-efficient anchor.	3 / 3
Actionability	Concrete directives ("Wait for confirmation before writing to history", "If a decision reverses, update the entry immediately") plus copy-paste-ready example strings give specific, actionable guidance appropriate for an instruction-only skill.	3 / 3
Workflow Clarity	The behavioral spec is unambiguous for this single-purpose skill and includes an explicit checkpoint ("Wait for confirmation before writing to history"), satisfying the simple-skill exception and matching the score-3 anchor.	3 / 3
Progressive Disclosure	At under 50 lines with no need for external references, the well-organized sections (Context, Patterns, Examples, Anti-Patterns) meet the score-3 bar for short single-purpose skills; no bundle files exist to verify.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 and occupies a distinct niche, but lacks an explicit "Use when..." trigger clause and broad natural keyword coverage, leaving the "when" only implied.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when writing or updating history.md / decision logs after a confirmed outcome") to lift completeness above 2.

Broaden trigger terms with natural variations users would say, such as "decision log", "record outcomes", or "update history".

Keep the concise negation ("not intermediate requests or reversed decisions") as it sharpens distinctiveness and specificity.

Dimension	Reasoning	Score
Specificity	Names a concrete action ("Record final outcomes"), the specific target file ("history.md"), and explicit exclusions ("not intermediate requests or reversed decisions"), matching the multiple-specific-actions anchor rather than the score-2 domain-only anchor.	3 / 3
Completeness	The "what" is clear (record final outcomes to history.md), but there is no "Use when..." clause or equivalent explicit trigger, so "when" is only implied — the rubric caps completeness at 2 for a missing explicit trigger.	2 / 3
Trigger Term Quality	Relevant keywords like "history.md", "outcomes", and "decisions" appear, but coverage is narrow with no common variations a user might say (e.g. "decision log", "update history"), fitting the score-2 anchor of some-but-missing keywords rather than the broad score-3 coverage.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (history-file hygiene) and the negation ("not intermediate requests or reversed decisions") makes it unlikely to trigger for unrelated skills, matching the score-3 clear-niche anchor.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: bradygaster/squad
Path: .copilot/skills/history-hygiene/SKILL.md
Commit: e23dd92

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.