claude-skills-factory
CLAUDE.md1 starsChanged 11 months agoMITView on GitHub
A curated collection of high-quality Claude Code skills for AI-assisted development workflows. Skills are modular components that extend Claude's capabilities for specific tasks. Each skill follows a standard structure: Planned skills: - API Documentation Generator - Test Case Generator - Refactoring Assistant - Performance Profiler - Security Auditor - Database Query Optimizer - Git Commit Message Generator - Architecture Analyzer MIT License - free to use in any project.
In this repository4 other files it gives its agents.
- code-review-assistantSkill
- excalidrawSkill
- mail-imap-smtpSkill
- server-auditSkill
The file
We split this CLAUDE.md into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 75
Create directory with kebab-case name: mkdir my-new-skill
- Very specific: line 76
Add SKILL.md with frontmatter (name, description)
- Distinctive: line 77
Add README.md with usage instructions
- Distinctive: line 80
Update root README.md with new skill entry
- Distinctive: line 88
Tested: Verify triggers and output format
- Distinctive: line 97
Use standard library only when possible
- Distinctive: line 102
Use emoji sparingly and consistently
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude Skills Factory
Project Overview
A curated collection of high-quality Claude Code skills for AI-assisted development workflows. Skills are modular components that extend Claude's capabilities for specific tasks.
Project Structure
claude-skills-factory/
├── README.md # Main project documentation
├── CONTRIBUTING.md # Contribution guidelines
├── LICENSE # MIT License
├── .gitignore
├── code-review-assistant/ # Code review skill
│ ├── SKILL.md # Skill definition (required)
│ ├── README.md # User documentation
│ └── scripts/ # Helper scripts
│ └── complexity_checker.py
└── excalidraw/ # Architecture diagram generator
├── SKILL.md # Skill definition
└── README.md # User documentationSkill Architecture
Each skill follows a standard structure:
skill-name/
├── SKILL.md # Main skill definition (required)
├── README.md # Skill documentation (optional)
├── scripts/ # Helper scripts (optional)
│ └── *.py, *.sh
└── examples/ # Usage examples (optional)SKILL.md Format
---
name: skill-name
description: Brief English description. 中文描述
---
# Skill ContentAvailable Skills
| Skill | Description |
code-review-assistant | Code review for PRs and snippets (6-dimension analysis) |
excalidraw | Generate architecture diagrams as .excalidraw files from codebase analysis |
Development Commands
# Install skill locally (symlink)
ln -s $(pwd)/skill-name ~/.claude/skills/skill-name
# Install all skills
for skill in */; do
ln -s $(pwd)/$skill ~/.claude/skills/$skill
done
# Copy skill to Claude skills directory
cp -r ./skill-name ~/.claude/skills/
# Run complexity checker (code-review-assistant)
python code-review-assistant/scripts/complexity_checker.py /path/to/codeCreating New Skills
- Create directory with kebab-case name:
mkdir my-new-skill - Add
SKILL.mdwith frontmatter (name, description) - Add
README.mdwith usage instructions - (Optional) Add helper scripts in
scripts/ - (Optional) Add examples in
examples/ - Update root
README.mdwith new skill entry
Skill Guidelines
- Naming: lowercase, hyphen-separated (e.g.,
code-review-assistant) - Bilingual: Include English and Chinese in description/content
- Focused: One skill = one specific task
- Documented: Clear usage instructions and examples
- Tested: Verify triggers and output format
Coding Standards
Python Scripts
- Python 3.6+ compatible
- PEP 8 style
- Include shebang:
#!/usr/bin/env python3 - Handle errors gracefully with helpful messages
- Use standard library only when possible
Markdown
- ATX-style headers (
#) - Fenced code blocks with language tags
- Use emoji sparingly and consistently
Roadmap
Planned skills:
- API Documentation Generator
- Test Case Generator
- Refactoring Assistant
- Performance Profiler
- Security Auditor
- Database Query Optimizer
- Git Commit Message Generator
- Architecture Analyzer
Key Files
| File | Purpose |
README.md | Project overview and installation |
CONTRIBUTING.md | Detailed contribution guidelines |
*/SKILL.md | Skill definition files |
*/README.md | Individual skill documentation |
License
MIT License - free to use in any project.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

