reskill

To reduce context overhead from boilerplate in agent charters, you can identify recurring patterns and promote them into reusable skills stored under .squad/skills. This standardizes knowledge across the team and trims input documents to essential context.

The best way to extract reusable skills from agent histories is to audit the histories for recurring actionable patterns and shared knowledge, then convert them into new skills using a consistent template at .squad/skills/{skill-name}/SKILL.md.

Yes, you can standardize team knowledge across multiple agent charters by auditing them for shared patterns, promoting those patterns into standardized skills, and then trimming the original charters to maintain only essential context.

You can trim agent charters to meet target size limits by first extracting recurring boilerplate and shared knowledge into reusable skills, then removing that redundant content from the input documents while preserving core context.

Skill extraction from team charters audits your existing files for recurring patterns, creates or updates skill definitions in .squad/skills, and trims the original input documents to reduce context overhead while maintaining essential operational knowledge.

You should avoid extracting shared patterns into separate skills if your agent charters do not contain recurring boilerplate or if trimming input documents would remove context critical to unique agent operations rather than redundant shared knowledge.