Extracts procedural knowledge from agent charters into shared reusable skills to optimize context budget. Audits charters for step-by-step procedures and checklists, identifies duplicates across agents, and produces slimmed-down charters under 1.5KB. Use when agent charters are too large, consolidating duplicated procedures, or reducing token usage by converting inline instructions into shared skill references.
78
67%
Does it follow best practices?
Impact
96%
1.12xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.squad/skills/reskill/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates specific capabilities, provides explicit trigger conditions via a 'Use when...' clause, and occupies a distinct niche. It uses third person voice consistently, avoids vague language, and includes concrete details like the 1.5KB target that help differentiate it from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Audits charters for step-by-step procedures and checklists', 'identifies duplicates across agents', 'produces slimmed-down charters under 1.5KB', and 'converting inline instructions into shared skill references'. These are detailed, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (extracts procedural knowledge, audits charters, identifies duplicates, produces slimmed charters) and 'when' with an explicit 'Use when...' clause covering three trigger scenarios: charters too large, consolidating duplicates, or reducing token usage. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'agent charters', 'too large', 'duplicated procedures', 'token usage', 'context budget', 'shared skill references', 'checklists', '1.5KB'. These cover the domain well and match how users would describe the problem. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on agent charter optimization and skill extraction. The combination of 'agent charters', 'context budget', 'shared reusable skills', and the 1.5KB target makes this very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level workflow for charter optimization but lacks the concrete, actionable detail needed for reliable execution. It reads more like a project brief or task assignment than a reusable skill — there are no templates, examples of before/after charters, criteria for identifying extractable procedures, or validation steps to ensure quality. The directive tone ('Run this now') is inappropriate for a skill definition.
Suggestions
Add a concrete before/after example showing a charter section being extracted into a skill and replaced with a reference
Include a validation checklist for verifying slimmed charters still contain necessary identity/ownership/behavioral content
Provide a template or schema for the metrics report (e.g., expected output format with bytes before/after, skills created)
Remove the imperative 'Run this now' directive — skills should describe how to do something, not command execution
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably concise at ~15 lines, but includes some unnecessary directive language ('Run this now') and could be tighter. The objective statement is somewhat redundant given the skill description. | 2 / 3 |
Actionability | The steps are high-level descriptions rather than concrete, executable guidance. There are no code examples, no specific commands, no templates for metrics reporting, and no examples of what extracted skills or slimmed charters should look like. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence, but there are no validation checkpoints — no way to verify extractions are correct, no feedback loop for checking that slimmed charters still contain necessary information, and no explicit criteria for what qualifies as 'procedural knowledge' vs identity/behavioral rules. | 2 / 3 |
Progressive Disclosure | References its own path (.squad/skills/reskill/SKILL.md) which is self-referential and confusing. No links to examples, templates, or supplementary materials that would help with the extraction process. The content is short enough to not need splitting, but lacks any supporting references. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
1bd9b17
Table of Contents
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.