reskill

Extract recurring patterns from team charters into shared SKILL.md files.

3|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/quaid-app/quaid --skill reskill-quaid-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reskill
Source: https://github.com/quaid-app/quaid/tree/main/.copilot/skills/reskill
Command: npx skills add https://github.com/quaid-app/quaid --skill reskill-quaid-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces per-agent context load by extracting recurring patterns from team charters and histories into reusable skills.

Core Features & Use Cases

  • Audit charters and histories to identify boilerplate, common patterns, and knowledge duplicates.
  • Promote patterns into shared skills and store them at .squad/skills/{skill-name}/SKILL.md with clear naming, documentation, and confidence tagging.
  • Trim charters and histories to improve efficiency while preserving unique per-agent context and accountability.

Quick Start

Identify recurring patterns and create or update shared skills under .squad/skills/{skill-name}/SKILL.md.

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 load from recurring patterns in team charters?

Reduce per-agent context load by auditing team charters and histories to identify boilerplate and recurring patterns, then promoting those patterns into shared, reusable skills to eliminate duplication.

What is the process for extracting reusable skills from team histories?

Skill extraction from team histories involves identifying common patterns, promoting them into documented skills with proper naming and confidence levels, then writing them to .squad/skills/{skill-name}/SKILL.md files.

How do I trim charters and histories to improve team optimization without losing accountability?

Trim charters and histories by removing extracted boilerplate while preserving unique per-agent context, ensuring accountability is maintained and per-agent efficiency improves across the charter history lifecycle.

Does knowledge management for charter management require specific governance rules for skill extraction?

Yes, knowledge management for charter management requires extraction to follow governance rules, ensuring updated SKILL.md files are properly written with clear naming, documentation, and confidence tagging for secure reuse.

What's the best way to document promoted patterns for reuse across the charter history lifecycle?

Document promoted patterns by storing them at .squad/skills/{skill-name}/SKILL.md with clear naming, documentation, and confidence levels, ensuring they are accessible and traceable for reuse across the charter history lifecycle.