Skip to content
cccskills
FreePublished on GitHub

reskill

Review agent charters and histories, extract repeated knowledge into shared skills, and shorten the original documents while preserving unique responsibilities. A before-and-after size report shows how much context each agent saves.

OriginalShow the original description

Team-wide charter and history optimization through skill extraction

See how to install

Good for

  • Reducing oversized agent charters
  • Extracting duplicated knowledge into shared skills
  • Condensing accumulated agent histories
  • Measuring document size reductions across a team

Files included (1)

  • SKILL.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Context

When the coordinator hears "team, reskill" (or similar: "optimize context", "slim down charters"), trigger a team-wide optimization pass. The goal: reduce per-agent context consumption by extracting shared patterns from charters and histories into reusable skills.

This is a periodic maintenance activity. Run whenever charter/history bloat is suspected.

Process

Step 1: Audit

Read all agent charters and histories. Measure byte sizes. Identify:

  • Boilerplate — sections repeated across ≥3 charters with <10% variation (collaboration, model, boundaries template)
  • Shared knowledge — domain knowledge duplicated in 2+ charters (incident postmortems, technical patterns)
  • Mature learnings — history entries appearing 3+ times across agents that should be promoted to skills

Step 2: Extract

For each identified pattern:

  1. Create or update a skill at .squad/skills/{skill-name}/SKILL.md
  2. Follow the skill template format (frontmatter + Context + Patterns + Examples + Anti-Patterns)
  3. Set confidence: low (first observation), medium (2+ agents), high (team-wide)

Step 3: Trim

Charters — target ≤1.5KB per agent:

  • Remove Collaboration section entirely (spawn prompt + agent-collaboration skill covers it)
  • Remove Voice section (tagline blockquote at top of charter already captures it)
  • Trim Model section to single line: Preferred: {model}
  • Remove "When I'm unsure" boilerplate from Boundaries
  • Remove domain knowledge now covered by a skill — add skill reference comment if helpful
  • Keep: Identity, What I Own, unique How I Work patterns, Boundaries (domain list only)

Histories — target ≤8KB per agent:

  • Apply history-hygiene skill to any history >12KB
  • Promote recurring patterns (3+ occurrences across agents) to skills
  • Summarize old entries into ## Core Context section
  • Remove session-specific metadata (dates, branch names, requester names)

Step 4: Report

Output a savings table:

AgentCharter BeforeCharter AfterHistory BeforeHistory AfterSaved

Include totals and percentage reduction.

Patterns

Minimal Charter Template (target format after reskill)

# {Name} — {Role}

> {Tagline — one sentence capturing voice and philosophy}

## Identity
- **Name:** {Name}
- **Role:** {Role}
- **Expertise:** {comma-separated list}

## What I Own
- {bullet list of owned artifacts/domains}

## How I Work
- {unique patterns and principles — NOT boilerplate}

## Boundaries
**I handle:** {domain list}
**I don't handle:** {explicit exclusions}

## Model
Preferred: {model}

Skill Extraction Threshold

  • 1 charter → leave in charter (unique to that agent)
  • 2 charters → consider extracting if >500 bytes of overlap
  • 3+ charters → always extract to a shared skill

Anti-Patterns

  • Don't delete unique per-agent identity or domain-specific knowledge
  • Don't create skills for content only one agent uses
  • Don't merge unrelated patterns into a single mega-skill
  • Don't remove Model preference line (coordinator needs it for model selection)
  • Don't touch .squad/decisions.md during reskill
  • Don't remove the tagline blockquote — it's the charter's soul in one line

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.

  • Locate team files across separate working directories
  • Record decisions that affect other agents
  • Request input from another specialist
github/gh-aw5.4KUpdated Oct 19, 2026

agent-conduct

FreeSummary

Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.

  • Share development rules across multiple agents
  • Keep team-specific agent names out of code and tests
  • Check affected tests before declaring work complete
github/gh-aw5.4KUpdated Oct 19, 2026

Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.

  • Designing a new workflow through questions
  • Investigating failed runs and recurring errors
  • Upgrading workflows and addressing deprecations
github/gh-aw5.4KUpdated Oct 19, 2026

Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.

  • Proposing a major architecture change
  • Replanning milestones after a foundation change
  • Comparing technical options before seeking approval
github/gh-aw5.4KUpdated Oct 19, 2026

Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.

  • Updating the firewall version used by gh-aw
  • Reviewing release notes for integration changes
  • Checking configuration schema differences
github/gh-aw5.4KUpdated Oct 19, 2026

Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.

  • Reviewing git operations after repository checkout
  • Checking tokens for private cross-repository access
  • Reviewing sparse and shallow checkout changes
github/gh-aw5.4KUpdated Oct 19, 2026

See all skills by github

Report a problem with this skill