sw:skill-gen

Detect recurring patterns in living docs and generate project-specific SKILL.md files.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Sjdjdiejdrirhdkjej/Summachat-V2 --skill sw-skill-gen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sw:skill-gen
Source: https://github.com/Sjdjdiejdrirhdkjej/Summachat-V2/tree/main/.claude/skills/skill-gen
Command: npx skills add https://github.com/Sjdjdiejdrirhdkjej/Summachat-V2 --skill sw-skill-gen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect recurring patterns across living docs and increments and convert them into reusable, project-specific skills that accelerate alignment and standardization.

Core Features & Use Cases

  • On-demand skill generation from observed signals, using a project-local skill-creator.
  • Writes SKILL.md files under .claude/skills/{pattern-slug} with frontmatter for discovery and operative guidance.
  • Updates and tracks skill signals to avoid duplicates and support reuse across increments.

Quick Start

Run sw:skill-gen to generate a new project skill from detected living-doc patterns.

Frequently Asked Questions about sw:skill-gen

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

FAQPage Schema
How do I turn recurring patterns in living docs into reusable skills?

To turn recurring patterns into reusable skills, run the skill generation process to identify signals across increment closures and automatically write SKILL.md files with frontmatter under .claude/skills/{pattern-slug} for project alignment.

What is skill generation from living docs used for?

Skill generation from living docs is used to detect recurring patterns across multiple increments and convert them into standardized project skills, accelerating team alignment and avoiding duplicate efforts through tracked skill signals.

How do I generate a project skill from detected patterns step by step?

To generate a project skill from detected patterns, run the skill generator to apply detection across increment closures, use the skill-creator plugin to build frontmatter and evaluation scaffolding, and update the skill-signals.json store to track the new entry.

Can I use this skill generation without external dependencies?

Yes, you can use this skill generation without external dependencies because it relies on a project-local skill-creator plugin to generate frontmatter and evaluation scaffolding, writing all outputs directly to the local .claude/skills directory.

How does pattern detection avoid creating duplicate project skills?

Pattern detection avoids creating duplicate project skills by updating and tracking skill signals in a dedicated skill-signals.json store, ensuring recurring patterns across increment closures are matched against existing entries before generating new SKILL.md files.

What is the best way to standardize recurring workflows across increment closures?

The best way to standardize recurring workflows across increment closures is to detect living-doc patterns and convert them into project-specific SKILL.md files, enabling on-demand skill creation that standardizes alignment for project teams and stakeholders.