reskill

Audit agent charters and histories to extract repeated patterns into shared skills.

209|27|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dotnet/maui-labs --skill reskill-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reskill
Source: https://github.com/dotnet/maui-labs/tree/main/src/Comet/.copilot/skills/reskill
Command: npx skills add https://github.com/dotnet/maui-labs --skill reskill-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces per-agent context bloat by identifying repeated charter/history patterns and promoting them into reusable shared skills, making coordination faster and leaner.

Core Features & Use Cases

  • Periodic Charter/History Audit: Measures charter and history sizes and flags repeated boilerplate, duplicated domain knowledge, and recurring learnings.
  • Skill Extraction Workflow: Creates or updates skills so shared patterns move out of individual charters/histories and into .squad/skills/{skill-name}/SKILL.md.
  • Context Trimming & Promotion Rules: Enforces target size limits (≤1.5KB charters, ≤8KB histories) and promotes entries appearing across 2+ or 3+ agents.
  • Savings Reporting: Produces a savings table showing before/after sizes per agent and overall reduction.

Quick Start

Run reskill as a team-wide maintenance pass whenever charter or history growth is suspected to extract repeated content into shared skills and then trim each agent to the target size limits.

Frequently Asked Questions about reskill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce agent context overhead caused by repeated charter and history patterns?

To reduce agent context overhead, you can audit agent charters and histories to identify repeated boilerplate, duplicated domain knowledge, and recurring learnings, then extract those repeated patterns into shared skills. This shrinks agent charters and makes coordination leaner.

What is the best way to extract recurring learnings into shared skills for multiple agents?

The best way to extract recurring learnings is to measure byte sizes and select extraction candidates by overlap thresholds, such as content appearing across 2 or 3 agents. You then update `.squad/skills/{skill-name}/SKILL.md` with the required structure to promote these shared patterns out of individual agents.

What are the size limits for trimming agent charters and histories?

The target size limits for trimming agent charters and histories are charters at 1.5KB or less and histories at 8KB or less. Enforcing these context trimming rules ensures per-agent context bloat is minimized across the team.

When should I perform a team-wide charter and history audit?

You should perform a team-wide charter and history audit whenever charter or history growth is suspected across multiple agents. If repeated content occurs in several places, this maintenance pass flags boilerplate and promotes entries appearing across 2 or more agents into shared skills.

Does extracting shared skills provide a report on context savings?

Extracting shared skills generates a savings report showing before and after sizes per agent and the overall reduction. This before/after savings table helps quantify the context optimization achieved by moving duplicated domain knowledge out of individual agent charters and histories.

Why does my agent history keep growing with duplicated domain knowledge?

Agent history grows with duplicated domain knowledge when recurring learnings and repeated boilerplate are not promoted into shared skills. Running a periodic charter and history audit identifies these repeated patterns and extracts them into `.squad/skills/` to prevent ongoing context bloat.