reskill

Extract recurring patterns from agent charters and histories into shared skills.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill reskill-leep-gh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reskill
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/.copilot/skills/reskill
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill reskill-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams reduce per-agent context overhead by turning repeated charters and histories into reusable, shared skills.

Core Features & Use Cases

  • Audit charters and histories to identify boilerplate and recurring patterns.
  • Create or update skills at .copilot/skills/{skill-name}/SKILL.md following the prescribed template.
  • Trim charters and histories to keep documentation lean and promote reuse across agents.

Quick Start

Run a reskill pass to extract recurring patterns from current charters into new shared skills.

Frequently Asked Questions about reskill

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

FAQPage Schema
How do I reduce per-agent context overhead from repeated charters and histories?▼

To reduce per-agent context overhead, you can extract recurring patterns from charters and histories to create reusable, shared skills. This process trims documentation and promotes reuse across team-wide operations.

How do I extract recurring patterns from agent charters into new skills?▼

Run an audit-extract-trim-report workflow that audits charters and histories to identify boilerplate, extracts patterns into new skills stored under .copilot/skills, and trims the original documentation to keep it lean.

What format and structure do I need for skill creation in .copilot/skills?▼

Skill creation requires a SKILL.md file stored under .copilot/skills/{skill-name}/. The file must follow a prescribed template and enforce a specific frontmatter structure containing both name and description fields.

What's the best way to maintain lean documentation for team knowledge management?▼

The best way to maintain lean documentation is to apply team-wide pattern extraction that audits historical data, converts boilerplate into shared skills, and trims charters to prevent context bloat across agents.

When should I not use pattern extraction for team optimization?▼

You should avoid pattern extraction when charters and histories lack recurring boilerplate, as the audit-extract-trim-report workflow relies on identifying repeated patterns to effectively reduce per-agent context overhead.