extract-rules-from-vault

Extract tribal knowledge from document artifacts into draft rules and skills.

31|20|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/mycelium-hq/ai-brain-starter --skill extract-rules-from-vault
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract-rules-from-vault
Source: https://github.com/mycelium-hq/ai-brain-starter/tree/main/skills/extract-rules-from-vault
Command: npx skills add https://github.com/mycelium-hq/ai-brain-starter --skill extract-rules-from-vault

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Walk a company's existing artifacts (Slack export, Notion export, GDocs, markdown vault, or any folder of documents) and emit draft hookify rules, draft skills, and a draft CLAUDE.md so a new install does not start empty. Structured-signal-first: parse what is deterministic (channels, users, headings, paths, recurring phrases) before asking the model to infer. The model's job is synthesis on residuals, not classification of everything. Use when onboarding a new company, founder, or team to ai-brain-starter and you want their tribal knowledge encoded as rules from day one.

Core Features & Use Cases

  • Read and analyze Slack/Notion/GDocs/Markdown vaults or any document folder to extract recurring patterns and decisions.
  • Produce draft hookify rules, CLAUDE.md draft, and candidate skills so a fresh install is not empty.
  • Outputs are designed for founder review and refinement before formal live deployment.

Quick Start

Provide the path to your document dump and run the extractor to generate initial drafts for review.

Frequently Asked Questions about extract-rules-from-vault

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

FAQPage Schema
How do I extract tribal knowledge from a Notion or Slack export to generate AI rules?

To extract tribal knowledge from a Notion or Slack export, this Skill parses deterministic signals like channels, headings, and recurring phrases before synthesis. It outputs draft hookify rules and a CLAUDE.md file for immediate founder review.

What is the best way to populate a new Claude install with existing company documentation?

Populating a new Claude install with company documentation involves walking a folder of markdown or GDocs artifacts to emit draft skills and memory files. This approach ensures your fresh install starts with encoded rules rather than an empty state.

Can I generate draft hookify rules directly from a folder of markdown vault files?

Yes, you can generate draft hookify rules directly from a folder of markdown vault files. The extractor operates in a structured-signal-first mode, deriving deterministic signals from file paths and headings before synthesizing reusable drafts.

How do I convert document exports into structured signals and draft skills?

Converting document exports into structured signals and draft skills requires parsing deterministic artifacts like users and paths first. The model then performs synthesis on residual data to produce candidate skills and a signals.json file for review.

What outputs should I expect when extracting patterns from company artifacts for AI onboarding?

When extracting patterns from company artifacts for AI onboarding, outputs include a CLAUDE.md.draft, hookify-rules, candidate skills, signals.json, and an extraction-report. These files include a REVIEW.md gate for final acceptance before live deployment.

Do I need to review draft CLAUDE.md files generated from Slack exports before deployment?

Yes, you need to review draft CLAUDE.md files generated from Slack exports before deployment. The outputs are specifically designed for founder review and refinement, utilizing a REVIEW.md gate to ensure formal live acceptance of the extracted rules.