reskill

Audit charters and histories to extract recurring patterns into reusable skills.

2|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/PlagueHO/plagueho.learn --skill reskill-plagueho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reskill
Source: https://github.com/PlagueHO/plagueho.learn/tree/main/.copilot/skills/reskill
Command: npx skills add https://github.com/PlagueHO/plagueho.learn --skill reskill-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces team cognitive load by auditing charters and histories to identify boilerplate, duplicated knowledge, and patterns that can be turned into reusable skills.

Core Features & Use Cases

  • Audit charters and histories to surface boilerplate, shared knowledge patterns, and mature learnings.
  • Extract identified patterns into skills under .squad/skills/{skill-name}/SKILL.md with a standardized, frontmatter-driven template.
  • Trim charters and histories to target sizes (charters ≤ 1.5KB per agent, histories ≤ 8KB) and promote recurring content to skills.

Quick Start

Run the reskill workflow to audit charters, extract recurring patterns into skills, and trim histories for efficiency.

Frequently Asked Questions about reskill

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

FAQPage Schema
How do I extract reusable knowledge from agent charters and histories?

You can extract recurring patterns from charters by auditing content for boilerplate and shared knowledge, then saving them as reusable skills. This process trims future charters to target sizes and reduces overall team context.

What is the target size for agent charters and histories after knowledge extraction?

Target sizes are charters at 1.5KB per agent and histories at 8KB or less. Trimming content to these constraints involves promoting mature learnings and duplicated knowledge into reusable skills.

How do I create a reusable skill template with frontmatter?

You create reusable skills at .squad/skills/{skill-name}/SKILL.md using a standardized, frontmatter-driven template with a name and description. This ensures extracted patterns are consistently formatted across the team.

What is the best way to reduce team cognitive load from duplicated context?

To reduce team cognitive load from duplicated context, audit charters and histories for shared knowledge patterns, extract them into reusable skills, and update the original files to remove the boilerplate.

When should I audit agent histories for boilerplate extraction?

Audit agent histories for boilerplate extraction when context sizes exceed 8KB or when recurring patterns duplicate across agents. This captures shared knowledge as reusable skills and restores context efficiency.