Style Extraction Skill

Style extraction analyzes your existing documents to identify consistent patterns in voice, tone, sentence structure, and word choice, then generates reusable style guides saved to rules/style/. Provide 3-5 substantial source documents and the skill prioritizes corporate voice first, then content-type voices like technical or blog styles.

Create style guides from your own content using style extraction to capture your corporate voice and content-type conventions. Store these guides in rules/style/ and apply them to new content to maintain consistency across teams and projects without manual documentation.

Yes. The skill discovers corporate voice first, then extracts separate style patterns for specific content types—technical documentation, blog posts—and optionally individual author voices. Each discovery is saved as a distinct style guide for targeted application.

Provide new source documents and invoke the skill with updated paths. It adds new findings incrementally without overwriting existing guides, allowing your style guides to evolve as your content and brand voice develop over time.

No. The skill auto-discovers style patterns directly from your source content, making it useful when no style guide exists yet. It can optionally compare findings against existing guides to validate or refine them during project setup or content updates.

The skill processes content stored in /sources/ or accessible file paths. It requires substantive documents as input and outputs structured style guides to rules/style/ with metadata including analyzed document sources, processing date, and the command used.