claude-skills
CLAUDE.md0 starsChanged 8 months agoMITView on GitHub
This is a comprehensive skills library for Claude AI - reusable, production-ready skill packages that bundle domain expertise, best practices, analysis tools, and strategic frameworks. The repository provides modular skills that teams can download and use directly in their workflows. Current Scope: 53 production-ready skills across 8 domains with 87+ Python automation tools. Key Distinction: This is NOT a traditional application. It's a library of skill packages meant to be extracted and deployed by users into their own Claude workflows.
- Reads credentials
- Installs packages
- Commits and pushes
2 other projects use a version of this.
Adopted by
Most recently taken up by
- theandyalvarez7-ruby/claude-skillsword for word, first seen Oct 25, 2026
- robertbstillwell/marketing-skillsword for word, first seen Mar 2, 2026
Other versions2 projects use a version of this.
Word for word · 2
- robertbstillwell/marketing-skills★ 26100% same
- theandyalvarez7-ruby/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- agents/CLAUDE.mdCLAUDE.md
- business-growth/CLAUDE.mdCLAUDE.md
- c-level-advisor/CLAUDE.mdCLAUDE.md
- finance/CLAUDE.mdCLAUDE.md
- marketing-skill/CLAUDE.mdCLAUDE.md
- product-team/CLAUDE.mdCLAUDE.md
- project-management/CLAUDE.mdCLAUDE.md
- ra-qm-team/CLAUDE.mdCLAUDE.md
- standards/CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
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
- Distinctive: line 110
Use standard library only (minimal dependencies)
- Distinctive: line 113
No ML/LLM calls (keeps skills portable and fast)
- Very specific: line 116
Keep scripts runnable with minimal setup (pip install package at most)
- Very specific: line 117
Document all dependencies in SKILL.md
- Distinctive: line 118
Prefer standard library implementations
- Distinctive: line 156
Algorithm over AI: - Use deterministic analysis (code) vs LLM calls
- Distinctive: line 170
Creating New Skills: Follow the appropriate domain's roadmap and CLAUDE.md guide (see Navigation Map above).
≈ “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.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Purpose
This is a comprehensive skills library for Claude AI - reusable, production-ready skill packages that bundle domain expertise, best practices, analysis tools, and strategic frameworks. The repository provides modular skills that teams can download and use directly in their workflows.
Current Scope: 53 production-ready skills across 8 domains with 87+ Python automation tools.
Key Distinction: This is NOT a traditional application. It's a library of skill packages meant to be extracted and deployed by users into their own Claude workflows.
Navigation Map
This repository uses modular documentation. For domain-specific guidance, see:
| Domain | CLAUDE.md Location | Focus |
| Agent Development | agents/CLAUDE.md | cs-* agent creation, YAML frontmatter, relative paths |
| Marketing Skills | marketing-skill/CLAUDE.md | Content creation, SEO, demand gen, campaign analytics Python tools |
| Product Team | product-team/CLAUDE.md | RICE, OKRs, user stories, UX research tools |
| Engineering | engineering-team/CLAUDE.md | Scaffolding, fullstack, AI/ML, data tools |
| C-Level Advisory | c-level-advisor/CLAUDE.md | CEO/CTO strategic decision-making |
| Project Management | project-management/CLAUDE.md | Atlassian MCP, Jira/Confluence integration |
| RA/QM Compliance | ra-qm-team/CLAUDE.md | ISO 13485, MDR, FDA compliance workflows |
| Business & Growth | business-growth/CLAUDE.md | Customer success, sales engineering, revenue operations |
| Finance | finance/CLAUDE.md | Financial analysis, DCF valuation, budgeting, forecasting |
| Standards Library | standards/CLAUDE.md | Communication, quality, git, security standards |
| Templates | templates/CLAUDE.md | Template system usage |
Current Sprint: See documentation/delivery/sprint-11-05-2025/ for active sprint context and progress.
Architecture Overview
Repository Structure
claude-code-skills/
├── agents/ # cs-* prefixed agents (in development)
├── marketing-skill/ # 6 marketing skills + Python tools
├── product-team/ # 5 product skills + Python tools
├── engineering-team/ # 18 engineering skills + Python tools
├── c-level-advisor/ # 2 C-level skills
├── project-management/ # 6 PM skills + Atlassian MCP
├── ra-qm-team/ # 12 RA/QM compliance skills
├── business-growth/ # 3 business & growth skills + Python tools
├── finance/ # 1 finance skill + Python tools
├── standards/ # 5 standards library files
├── templates/ # Reusable templates
└── documentation/ # Implementation plans, sprints, deliverySkill Package Pattern
Each skill follows this structure:
skill-name/
├── SKILL.md # Master documentation
├── scripts/ # Python CLI tools (no ML/LLM calls)
├── references/ # Expert knowledge bases
└── assets/ # User templatesDesign Philosophy: Skills are self-contained packages. Each includes executable tools (Python scripts), knowledge bases (markdown references), and user-facing templates. Teams can extract a skill folder and use it immediately.
Key Pattern: Knowledge flows from references/ → into SKILL.md workflows → executed via scripts/ → applied using assets/ templates.
Git Workflow
Branch Strategy: feature → dev → main (PR only)
Branch Protection Active: Main branch requires PR approval. Direct pushes blocked.
Quick Start
# 1. Always start from dev
git checkout dev
git pull origin dev
# 2. Create feature branch
git checkout -b feature/agents-{name}
# 3. Work and commit (conventional commits)
feat(agents): implement cs-{agent-name}
fix(tool): correct calculation logic
docs(workflow): update branch strategy
# 4. Push and create PR to dev
git push origin feature/agents-{name}
gh pr create --base dev --head feature/agents-{name}
# 5. After approval, PR merges to dev
# 6. Periodically, dev merges to main via PRBranch Protection Rules:
- ✅ Main: Requires PR approval, no direct push
- ✅ Dev: Unprotected, but PRs recommended
- ✅ All: Conventional commits enforced
See documentation/WORKFLOW.md for complete workflow guide. See standards/git/git-workflow-standards.md for commit standards.
Development Environment
No build system or test frameworks - intentional design choice for portability.
Python Scripts:
- Use standard library only (minimal dependencies)
- CLI-first design for easy automation
- Support both JSON and human-readable output
- No ML/LLM calls (keeps skills portable and fast)
If adding dependencies:
- Keep scripts runnable with minimal setup (
pip install packageat most) - Document all dependencies in SKILL.md
- Prefer standard library implementations
Current Sprint
Active Sprint: sprint-11-05-2025 (Nov 5-19, 2025) Goal: Skill-Agent Integration Phase 1-2 Status: ✅ COMPLETE - All 6 days finished, 5 agents deployed
Deliverables:
- 5 production agents: cs-content-creator, cs-demand-gen-specialist, cs-ceo-advisor, cs-cto-advisor, cs-product-manager
- 1 agent template for future development
- Modular documentation structure (main + 9 domain CLAUDE.md files)
- Branch protection and workflow documentation
Progress Tracking:
- Sprint Plan - Day-by-day execution plan
- Sprint Context - Goals, scope, risks
- Sprint Progress - Real-time auto-updating tracker
Roadmap
Phase 1-2 Complete: 53 production-ready skills deployed
- Marketing (6), C-Level (2), Product (5), PM (6), Engineering (18), RA/QM (12), Business & Growth (3), Finance (1)
- 87+ Python automation tools, 104+ reference guides
- Complete enterprise coverage from marketing through regulatory compliance, sales, customer success, and finance
Next Priorities:
- Phase 3 (Q2 2026): Marketing expansion - SEO optimizer, social media manager, growth marketer
- Phase 4 (Q3 2026): Specialized domains - Mobile, blockchain, web3, advanced analytics
Target: 60+ skills by Q3 2026
See domain-specific roadmaps in each skill folder's README.md or roadmap files.
Key Principles
- Skills are products - Each skill deployable as standalone package
- Documentation-driven - Success depends on clear, actionable docs
- Algorithm over AI - Use deterministic analysis (code) vs LLM calls
- Template-heavy - Provide ready-to-use templates users customize
- Platform-specific - Specific best practices > generic advice
Anti-Patterns to Avoid
- Creating dependencies between skills (keep each self-contained)
- Adding complex build systems or test frameworks (maintain simplicity)
- Generic advice (focus on specific, actionable frameworks)
- LLM calls in scripts (defeats portability and speed)
- Over-documenting file structure (skills are simple by design)
Working with This Repository
Creating New Skills: Follow the appropriate domain's roadmap and CLAUDE.md guide (see Navigation Map above).
Editing Existing Skills: Maintain consistency across markdown files. Use the same voice, formatting, and structure patterns.
Quality Standard: Each skill should save users 40%+ time while improving consistency/quality by 30%+.
Additional Resources
- .gitignore: Excludes .vscode/, .DS_Store, AGENTS.md, PROMPTS.md, .env*
- Standards Library: standards/ - Communication, quality, git, documentation, security
- Implementation Plans: documentation/implementation/
- Sprint Delivery: documentation/delivery/
Last Updated: February 2026 Current Sprint: sprint-11-05-2025 (Skill-Agent Integration Phase 1-2) Status: 53 skills deployed, agent system in development
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.

