Claude-skill-registry fabric
Native Fabric pattern execution for Claude Code. USE WHEN processing content with Fabric patterns (extract_wisdom, summarize, analyze_claims, threat modeling, etc.). Patterns run natively in Claude's context - no CLI spawning needed. Only use fabric CLI for YouTube transcripts (-y) or pattern updates (-U).
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/fabric-blackpwnguin-personal-ai" ~/.claude/skills/majiayu000-claude-skill-registry-fabric && rm -rf "$T"
manifest:
skills/data/fabric-blackpwnguin-personal-ai/SKILL.mdsource content
Fabric Skill - Native Pattern Execution
The Key Insight
Fabric patterns are just markdown prompts. Instead of spawning
fabric -p pattern_name for every task, Claude Code reads and applies patterns directly from tools/patterns/. This gives you:
- Your Claude subscription's full power - Opus/Sonnet intelligence, not Fabric's default model
- Full conversation context - Patterns work with your entire session
- No CLI overhead - Faster execution, no process spawning
- Same 248 patterns - All the patterns you know, just applied natively
When to Use Native Patterns (Default)
For any pattern-based processing:
- Read
tools/patterns/{pattern_name}/system.md - Apply the pattern instructions directly to the content
- Return results without external CLI calls
Examples:
User: "Extract wisdom from this transcript" → Read tools/patterns/extract_wisdom/system.md → Apply pattern to content → Return structured output (IDEAS, INSIGHTS, QUOTES, etc.) User: "Create a threat model for this API" → Read tools/patterns/create_threat_model/system.md → Apply pattern to the API description → Return threat model User: "Summarize this article" → Read tools/patterns/summarize/system.md → Apply pattern to article → Return summary
When to Still Use Fabric CLI
Only use the
fabric command for operations that require external services:
| Operation | Command | Why CLI Needed |
|---|---|---|
| YouTube transcripts | | Downloads video, extracts transcript |
| Update patterns | | Pulls from GitHub |
| List patterns | | Quick reference |
For everything else, use native patterns.
Pattern Categories (248 Total)
Threat Modeling & Security
- General threat modelingcreate_threat_model
- STRIDE methodologycreate_stride_threat_model
- Threat scenario generationcreate_threat_scenarios
- Threat report analysisanalyze_threat_report
- SIGMA detection rulescreate_sigma_rules
- Nuclei scanner templateswrite_nuclei_template_rule
- Semgrep static analysis ruleswrite_semgrep_rule
Summarization
- General summarizationsummarize
- Ultra-concise summarycreate_5_sentence_summary
- Academic paper summarysummarize_paper
- Meeting notessummarize_meeting
- Video summaryyoutube_summary
Wisdom Extraction
- General wisdom extractionextract_wisdom
- Key insightsextract_insights
- Core messageextract_main_idea
- Actionable recommendationsextract_recommendations
- High-value insightsextract_alpha
Analysis
- Claim verificationanalyze_claims
- Code analysisanalyze_code
- Malware analysisanalyze_malware
- Academic paper analysisanalyze_paper
- Debate analysisanalyze_debate
Content Creation
- Product Requirements Documentcreate_prd
- Design documentationcreate_design_document
- Mermaid diagramscreate_mermaid_visualization
- Essay writingwrite_essay
- Security findingscreate_report_finding
Improvement
- Writing enhancementimprove_writing
- Prompt engineeringimprove_prompt
- Code reviewreview_code
- Humanize AI texthumanize
Updating Patterns
Run the update script to sync latest patterns from upstream:
./tools/update-patterns.sh
This will:
- Run
to fetch upstream updatesfabric -U - Sync patterns to
tools/patterns/
Requirements:
fabric CLI must be installed (go install github.com/danielmiessler/fabric@latest)
Pattern Structure
Each pattern directory contains:
- The main prompt/instructions (this is what gets applied)system.md
- Documentation (optional)README.md
- Example user input (optional)user.md
Why Native > CLI
| Aspect | Native Patterns | fabric CLI |
|---|---|---|
| Model | Your subscription (Opus/Sonnet) | Fabric's configured model |
| Context | Full conversation history | Just the input |
| Speed | Instant (no process spawn) | ~1-2s CLI overhead |
| Integration | Seamless with Claude Code | External tool call |
The patterns are identical. The difference is execution context and model power.
Full Pattern List
See all available patterns:
ls tools/patterns/
Or browse:
tools/patterns/{pattern_name}/system.md