archival-integrity

Preserve content when moving entries between tracked Squad state files

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./.copilot/skills/archival-integrity/SKILL.md

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 skill body is well-structured, concise, and action-oriented with strong validation feedback loops for a destructive operation. It is an instruction-only skill whose concrete function references and gating rules make it highly actionable.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with no concept-padding; a few sentences could be tightened further, so it is not a clean 5.	4 / 5
Actionability	Concrete function names (archiveEntries, prepareInboxBodyForMerge, formatArchivalReport) with exact file paths and specific heading-demotion rules give mostly executable guidance; minor gaps keep it below 5.	4 / 5
Workflow Clarity	The numbered Patterns sequence has explicit validation checkpoints (re-read destination, prove headings present, count-match gating before trim) plus Stop-condition feedback loops for this destructive operation.	5 / 5
Progressive Disclosure	Under 50 lines with well-organized sections (Context, Scope, Patterns, Stop conditions, Examples, Anti-Patterns) and no need for external bundle references.	5 / 5
	Total	18 / 20 Passed

Description

46%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 states a clear, specific purpose but omits an explicit 'Use when...' trigger and leans on domain jargon rather than natural user phrases. It is reasonably distinct within its niche.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger scenarios (e.g., 'Use when archiving decisions, summarizing history, or merging inboxes').

Soften jargon with natural synonyms a user might actually say (e.g., 'decision logs', 'history files') alongside 'Squad state files'.

List one or two more concrete actions (e.g., 'append, re-read, and trim') to broaden coverage beyond 'preserve' and 'move'.

Dimension	Reasoning	Score
Specificity	Names the domain ('tracked Squad state files') and 1-2 concrete actions ('Preserve content', 'moving entries') but coverage is not comprehensive.	3 / 5
Completeness	The 'what' is clear (preserve content when moving entries), but there is no 'Use when...' trigger clause, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'tracked Squad state files' is jargon-heavy and misses the natural phrases a user would say; only generic technical terms are present.	2 / 5
Distinctiveness Conflict Risk	The Squad-specific 'tracked state files' niche is mostly distinct with only minor overlap risk against closely related skills.	4 / 5
	Total	12 / 20 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/archival-integrity/SKILL.md
Commit: 29e69f5

Reviewed: 5 days 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.