CtrlK
BlogDocsLog inGet started
Tessl Logo

reskill

Team-wide charter and history optimization through skill extraction

54

Quality

61%

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

68%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 well-structured, actionable instruction skill with concrete thresholds and templates, but its batch/destructive workflow lacks an explicit validation or feedback-loop checkpoint, capping workflow clarity at 3.

Suggestions

Insert an explicit validation step in Step 3 (e.g. 'Before saving, verify each trimmed charter still contains Identity, What I Own, and Boundaries, and that no unique per-agent knowledge was removed; if it was, restore and re-trim').

Add a worked before/after example showing one charter transformed by the trim rules to make the guidance copy-paste concrete.

Consider moving the Minimal Charter Template into a references/ file and linking to it from the body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, using concrete byte thresholds and crisp bullets with no padding of known concepts; only minor narrative framing keeps it from a 5.

4 / 5

Actionability

Guidance is concrete and specific (exact thresholds, byte targets, a copy-paste minimal charter template, a savings-table format), but a worked before/after example of a trimmed charter would close the gap to 5.

4 / 5

Workflow Clarity

The Audit→Extract→Trim→Report sequence is clearly ordered, but this is a batch and destructive operation (editing all agents' charters/histories) with no explicit validation or fix-and-retry checkpoint, so workflow clarity is capped at 3 per the rubric.

3 / 5

Progressive Disclosure

Content is well-organized into Context, Process, Patterns, and Anti-Patterns with clear headers and no nested references; the full charter template could plausibly live in a separate reference file, which keeps it at 4 rather than 5.

4 / 5

Total

15

/

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 a concise noun phrase naming a distinct niche and one concrete mechanism, but it lacks an explicit 'Use when…' trigger clause and the natural trigger terms users would say, capping completeness and trigger quality at 3.

Suggestions

Add an explicit 'Use when…' clause naming the natural triggers, e.g. 'Use when the coordinator says "team, reskill", "optimize context", or "slim down charters".'

Expand the action list beyond 'skill extraction' to cover the full flow (audit, extract, trim, report) for more comprehensive specificity.

Include common synonyms like 'reskill' and 'slim down charters' so the description matches the phrases users naturally say.

DimensionReasoningScore

Specificity

Names the domain ('charter and history optimization') and one concrete action ('skill extraction'), but offers only a single action rather than comprehensive coverage, matching the score-3 anchor.

3 / 5

Completeness

The description gives a clear 'what' but no 'Use when…' clause or equivalent trigger guidance, so per the rubric cap completeness is held at 3.

3 / 5

Trigger Term Quality

Relevant keywords ('charter', 'history', 'skill extraction') are present, but the natural trigger phrases users actually say ('reskill', 'slim down charters', 'optimize context') are missing, so it stops at 3.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche (team-wide charter/history meta-optimization) with only minor overlap risk against general skill-creation skills, fitting the score-4 anchor rather than 5 since triggers are not fully concrete.

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.

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.