CtrlK
BlogDocsLog inGet started
Tessl Logo

reskill

Team-wide charter and history optimization through skill extraction

59

Quality

68%

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/reskill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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 strong, dense, operational instruction skill with concrete targets, thresholds, and templates, scoring top marks on conciseness, actionability, and organization. Its one weak spot is workflow clarity: a destructive team-wide trim operation proceeds with no verification checkpoint or rollback guidance.

Suggestions

Add a validation checkpoint after the Trim step (e.g., confirm no unique per-agent identity/domain knowledge was removed and that savings targets were met) before reporting.

Include a brief feedback/rollback loop — what to restore if a trim is found to have removed unique content — to satisfy the destructive/batch-operation expectation.

DimensionReasoningScore

Conciseness

The body is lean and operational: concrete byte targets (≤1.5KB, ≤8KB, >12KB) and thresholds (≥3 charters, <10% variation, 3+ times) with no concept-explaining fluff, and every section earns its place.

3 / 3

Actionability

As an instruction-only skill it gives highly concrete guidance — specific thresholds, file paths (.copilot/skills/{skill-name}/SKILL.md), a full charter template, and a report table format — so the absence of code is not penalized.

3 / 3

Workflow Clarity

The Audit→Extract→Trim→Report sequence is clearly ordered, but this is a destructive batch operation (removing charter sections across all agents) with no validation/verification checkpoint or feedback loop, capping the score at 2.

2 / 3

Progressive Disclosure

The skill is self-contained with no bundle files, well-sectioned (Context, Process, Patterns, Anti-Patterns), and free of nested references, so clear section organization suffices for a top score.

3 / 3

Total

11

/

12

Passed

Description

50%

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 conveys a clear domain and high-level action but is uniformly mid-tier: it states what the skill does without explicit when-to-use triggers, natural user phrasings, or concrete-enough actions. Adding a 'Use when...' clause with the natural trigger words used in the body would lift every dimension.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the coordinator says "reskill", "optimize context", or "slim down charters", or when charter/history bloat is suspected.'

Replace abstract verbs ('optimization', 'skill extraction') with concrete actions such as 'audits charters and histories, extracts shared patterns into reusable skills, trims per-agent context, and reports savings.'

Surface the natural trigger terms ('reskill', 'slim down charters', 'optimize context') directly in the description rather than only in the body.

DimensionReasoningScore

Specificity

The phrase 'charter and history optimization through skill extraction' names the domain and two action areas, but the actions ('optimization', 'extraction') are abstract rather than a comprehensive list of concrete capabilities.

2 / 3

Completeness

It clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 2.

2 / 3

Trigger Term Quality

It includes relevant keywords (charter, history, optimization, skill) but omits the natural phrasings a user would actually say ('reskill', 'slim down charters', 'optimize context'), which only appear in the body.

2 / 3

Distinctiveness Conflict Risk

The charter/history niche is fairly specific, but the abstract 'optimization' framing and absence of distinct trigger terms leave some overlap risk with generic optimization skills.

2 / 3

Total

8

/

12

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.

Validation15 / 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.