Agent skill · Security

fabric

Intelligent pattern selection for Fabric CLI. Automatically selects the right pattern from 242+ specialized prompts based on your intent - threat modeling, analysis, summarization, content creation, extraction, and more. USE WHEN processing content, analyzing data, creating summaries, threat modeling, or transforming text.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill buttercupck-bcck-vault-claude-skills-fabric-skill --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 13 KB
Bundled scripts: none
Path: skills/analysis/buttercupck-bcck-vault-claude-skills-fabric-skill/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Fabric Skill ## Setup Check - Fabric Repository **IMPORTANT: Before using this skill, verify the Fabric repository is available:** ```bash # Check if Fabric repo exists if [ ! -d "$HOME/.claude/skills/fabric/fabric-repo" ]; then echo "Fabric repository not found. Cloning..." cd "$HOME/.claude/skills/fabric" git clone https://github.com/danielmiessler/fabric.git fabric-repo echo "Fabric repository cloned successfully." else echo "Fabric repository found at $HOME/.claude/skills/fabric/fabric-repo" fi ``` **If the repo doesn't exist, clone it immediately before proceeding with any pattern selection.** ## When to Activate This Skill **Primary Use Cases:** - "Create a threat model for..." - "Summarize this article/video/paper..." - "Extract wisdom/insights from..." - "Analyze this [code/malware/claims/debate]..." - "Improve my writing/code/prompt..." - "Create a [visualization/summary/report]..." - "Rate/review/judge this content..." **The Goal:** Select the RIGHT pattern from 242+ available patterns based on what you're trying to accomplish. ## 🎯 Pattern Selection Strategy When a user requests Fabric processing, follow this decision tree: ### 1. Identify Intent Category **Threat Mod

What's inside
Steps it walks through
  1. Setup Check - Fabric Repository
  2. When to Activate This Skill
  3. 🎯 Pattern Selection Strategy
  4. 1. Identify Intent Category
  5. 2. Execute Pattern
  6. 📚 Pattern Categories (242 Total)
  7. Threat Modeling & Security (15 patterns)
  8. Summarization (20 patterns)
  9. Extraction (30+ patterns)
  10. Analysis (35+ patterns)
  11. Creation (50+ patterns)
  12. Improvement (10 patterns)
  13. Rating/Judgment (8 patterns)
  14. 🔄 Updating Patterns
Ships with 1 file
  • metadata.json
Commands it runs
Check if Fabric repo exists
if [ ! -d "$HOME/.claude/skills/fabric/fabric-repo" ]; then
echo "Fabric repository not found. Cloning..."
cd "$HOME/.claude/skills/fabric"
git clone https://github.com/danielmiessler/fabric.git fabric-repo
echo "Fabric repository cloned successfully."
else
echo "Fabric repository found at $HOME/.claude/skills/fabric/fabric-repo"
fi
Basic format
More from claude-skill-registry
All skills →
About this skill
What does the fabric skill do?

Intelligent pattern selection for Fabric CLI. Automatically selects the right pattern from 242+ specialized prompts based on your intent - threat modeling, analysis, summarization, content creation, extraction, and more. USE WHEN processing content, analyzing data, creating summaries, threat modeling, or transforming text.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill buttercupck-bcck-vault-claude-skills-fabric-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going