fabric▌
supercent-io/skills-template · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Fabric is an open-source AI prompt orchestration framework by Daniel Miessler. It provides a library of reusable AI prompts called Patterns — each designed for a specific real-world task — wired into a simple Unix pipeline with stdin/stdout.
Fabric
Fabric is an open-source AI prompt orchestration framework by Daniel Miessler. It provides a library of reusable AI prompts called Patterns — each designed for a specific real-world task — wired into a simple Unix pipeline with stdin/stdout.
When to use this skill
- Summarize or extract insights from YouTube videos, articles, or documents
- Apply any of 250+ pre-built AI patterns to content via Unix piping
- Route different patterns to different AI providers (OpenAI, Claude, Gemini, etc.)
- Create custom patterns for repeatable AI workflows
- Run Fabric as a REST API server for integration with other tools
- Process command output, files, or clipboard content through AI patterns
- Use as an AI agent utility — pipe any tool output through patterns for intelligent summarization
Instructions
Step 1: Install Fabric
# macOS/Linux (one-liner)
curl -fsSL https://raw.githubusercontent.com/danielmiessler/fabric/main/scripts/installer/install.sh | bash
# macOS via Homebrew
brew install fabric-ai
# Windows
winget install danielmiessler.Fabric
# After install — configure API keys and default model
fabric --setup
Step 2: Learn the core pipeline workflow
Fabric works as a Unix pipe. Feed content through stdin and specify a pattern:
# Summarize a file
cat article.txt | fabric -p summarize
# Stream output in real time
cat document.txt | fabric -p extract_wisdom --stream
# Pipe any command output through a pattern
git log --oneline -20 | fabric -p summarize
# Process clipboard (macOS)
pbpaste | fabric -p summarize
# Pipe from curl
curl -s https://example.com/article | fabric -p summarize
Step 3: Discover patterns
# List all available patterns
fabric -l
# Update patterns from the repository
fabric -u
# Search patterns by keyword
fabric -l | grep summary
fabric -l | grep code
fabric -l | grep security
Key patterns:
| Pattern | Purpose |
|---|---|
summarize |
Summarize any content into key points |
extract_wisdom |
Extract insights, quotes, habits, and lessons |
analyze_paper |
Break down academic papers into actionable insights |
explain_code |
Explain code in plain language |
write_essay |
Write essays from a topic or rough notes |
clean_text |
Remove noise and formatting from raw text |
analyze_claims |
Fact-check and assess credibility of claims |
create_summary |
Create a structured, markdown summary |
rate_content |
Rate and score content quality |
label_and_rate |
Categorize and score content |
improve_writing |
Polish and improve text clarity |
create_tags |
Generate relevant tags for content |
ask_secure_by_design |
Review code or systems for security issues |
capture_thinkers_work |
Extract the core ideas of a thinker or author |
create_investigation_visualization |
Create a visual map of complex investigations |
Step 4: Process YouTube videos
# Summarize a YouTube video
fabric -y "https://youtube.com/watch?v=VIDEO_ID" -p summarize
# Extract key insights from a video
fabric -y "https://youtube.com/watch?v=VIDEO_ID" -p extract_wisdom
# Get transcript only (no pattern applied)
fabric -y "https://youtube.com/watch?v=VIDEO_ID" --transcript
# Transcript with timestamps
fabric -y "https://youtube.com/watch?v=VIDEO_ID" --transcript-with-timestamps
Step 5: Create custom patterns
Each pattern is a directory with a system.md file inside ~/.config/fabric/patterns/. The body should follow this structure:
mkdir -p ~/.config/fabric/patterns/my-pattern
cat > ~/.config/fabric/patterns/my-pattern/system.md << 'EOF'
# IDENTITY AND PURPOSE
You are an expert at [task]. Your job is to [specific goal].
Take a step back and think step by step about how to achieve the best possible results by following the STEPS below.
# STEPS
1. [Step 1]
2. [Step 2]
# OUTPUT INSTRUCTIONS
- Only output Markdown.
- [Format instruction 2]
- Do not give warnings or notes; only output the requested sections.
# INPUT
INPUT:
EOF
Use it immediately:
echo "input text" | fabric -p my-pattern
cat file.txt | fabric -p my-pattern --stream
Step 6: Multi-provider routing and advanced usage
# Run as REST API server (port 8080 by default)
fabric --serve
# Use web search capability
fabric -p analyze_claims --search "claim to verify"
# Per-pattern model routing in ~/.config/fabric/.env
FABRIC_MODEL_PATTERN_SUMMARIZE=anthropic|claude-opus-4-5
FABRIC_MODEL_PATTERN_EXTRACT_WISDOM=openai|gpt-4o
FABRIC_MODEL_PATTERN_EXPLAIN_CODE=google|gemini-2.0-flash
# Create shell aliases for frequently used patterns
alias summarize="fabric -p summarize"
alias wisdom="fabric -p extract_wisdom"
alias explain="fabric -p explain_code"
# Chain patterns
cat paper.txt | fabric -p summarize | fabric -p extract_wisdom
# Save output
cat document.txt | fabric -p extract_wisdom > insights.md
Step 7: Use in AI agent workflows
Fabric is a powerful utility for AI agents — pipe any tool output through patterns for intelligent analysis:
# Analyze test failures
npm test 2>&1 | fabric -p analyze_logs
# Summarize git history for a PR description
git log --oneline origin/main..HEAD | fabric -p create_summary
# Explain a code diff
git diff HEAD~1 | fabric -p explain_code
# Summarize build errors
make build 2>&1 | fabric -p summarize
# Analyze security vulnerabilities in code
cat src/auth.py | fabric -p ask_secure_by_design
# Process log files
cat /var/log/app.log | tail -100 | fabric -p analyze_logs
REST API server mode
Run Fabric as a microservice and call it from other tools:
# Start server
fabric --serve --port 8080
# Call via HTTP
curl -X POST http://localhost:8080/chat \
-H "Content-Type: application/json" \
-d '{"prompts":[{"userInput":"Summarize this","patternName":"summarize"}]}'
Best practices
- Run
fabric -ubefore first use and regularly to get the latest community patterns. - Use
--streamfor long content to see results progressively instead of waiting. - Create shell aliases (
alias wisdom="fabric -p extract_wisdom") for your most-used patterns. - Use per-pattern model routing to optimize cost vs. quality for each task type.
- Keep custom patterns in
~/.config/fabric/patterns/— they persist across updates. - For YouTube, transcript extraction works best with videos that have captions enabled.
- Chain patterns with Unix pipes for multi-step processing workflows.
- Follow the IDENTITY → STEPS → OUTPUT INSTRUCTIONS structure when creating custom patterns.
References
How to use fabric on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add fabric
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches fabric from GitHub repository supercent-io/skills-template and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate fabric. Access the skill through slash commands (e.g., /fabric) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★41 reviews- ★★★★★Shikha Mishra· Dec 16, 2024
fabric reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Soo Perez· Dec 12, 2024
I recommend fabric for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Aditi Sethi· Nov 3, 2024
Keeps context tight: fabric is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Aanya Mensah· Oct 22, 2024
fabric is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★William Martinez· Sep 17, 2024
fabric fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Rahul Santra· Sep 13, 2024
I recommend fabric for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Aditi Chawla· Sep 13, 2024
Solid pick for teams standardizing on skills: fabric is focused, and the summary matches what you get after install.
- ★★★★★Advait Choi· Sep 13, 2024
I recommend fabric for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Advait Huang· Aug 8, 2024
We added fabric from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Pratham Ware· Aug 4, 2024
Useful defaults in fabric — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 41