GitHub
report-findings
This skill should be used when synthesizing multi-source research, presenting findings with attribution, or when "report", "findings", or "synthesis" are mentioned.
☆ 21Voir le skill
Explorer
Explorez des skills pour le développement, le contenu, les données et la productivité. Comparez les descriptions et dépôts.
Catégories
Explorer
GitHub
security-engineering
This skill should be used when auditing code for security issues, reviewing authentication/authorization, evaluating input validation, analyzing cryptographic usage, or reviewing dependency security. Provides O...
☆ 21Voir le skill
GitHub
software-architecture
This skill should be used when designing systems, evaluating architectures, making technology decisions, or planning for scale. Provides technology selection frameworks, scalability planning, and architectural...
☆ 21Voir le skill
GitHub
skills-development
This skill should be used when creating skills, writing SKILL.md files, or when "create skill", "new skill", "validate skill", or "SKILL.md" are mentioned.
☆ 21Voir le skill
GitHub
status-reporting
This skill should be used when checking project status, starting sessions, reviewing activity, or when "sitrep", "status report", or "what's changed" are mentioned.
☆ 21Voir le skill
GitHub
cli-development-guidelines
REDIRECT: Use cli-dev:cli-development-guidelines instead. CLI development skills live in the cli-dev plugin.
☆ 21Voir le skill
GitHub
scenario-testing
This skill should be used when validating features end-to-end without mocks, testing integrations, or when "scenario test", "e2e test", or "no mocks" are mentioned.
☆ 21Voir le skill
GitHub
claude-command-authoring
This skill should be used when creating slash commands, writing command files, or when "/command", ".claude/commands", "$ARGUMENTS", or "create command" are mentioned.
☆ 21Voir le skill
GitHub
research-and-report
This skill should be used when researching best practices, evaluating technologies, comparing approaches, or when "research", "evaluation", or "comparison" are mentioned.
☆ 21Voir le skill
GitHub
version-control
This skill should be used when working with GitButler, virtual branches, `but` commands, or when `--gitbutler` or `--but` flags are mentioned.
☆ 21Voir le skill
GitHub
hono-dev
This skill should be used when building APIs with Hono, using hc client, implementing OpenAPI, or when "Hono", "RPC", or "type-safe API" are mentioned.
☆ 21Voir le skill
GitHub
multi-agent
This skill should be used when coordinating multiple agents, parallel development, agent handoffs, or when multi-agent, concurrent agents, or parallel agents are mentioned.
☆ 21Voir le skill
GitHub
claude-plugin-development
This skill should be used when creating plugins, publishing to marketplaces, or when "plugin.json", "marketplace", "create plugin", or "distribute plugin" are mentioned.
☆ 21Voir le skill
GitHub
pathfinding
This skill should be used when requirements are unclear, brainstorming ideas, or when "pathfind", "brainstorm", "figure out", "clarify requirements", or "work through" are mentioned.
☆ 21Voir le skill
GitHub
claude-rules-authoring
This skill should be used when creating rule files, organizing conventions, or when ".claude/rules/", "FORMATTING.md", "create rule", or "project conventions" are mentioned.
☆ 21Voir le skill
GitHub
stack-workflows
This skill should be used when creating stacked branches, dependent features, reviewable PR breakdown, or when stack, stacked branches, or `--anchor` are mentioned.
☆ 21Voir le skill
GitHub
pattern-analysis
This skill should be used when recognizing recurring themes, codifying best practices, extracting reusable workflows, or when "pattern", "recurring", or "repeated" are mentioned.
☆ 21Voir le skill
GitHub
react-dev
This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React...
☆ 21Voir le skill
GitHub
software-engineering
This skill should be used when making design decisions, evaluating trade-offs, assessing code quality, or when "engineering judgment" or "code quality" are mentioned.
☆ 21Voir le skill
GitHub
complexity-analysis
This skill should be used when evaluating complexity, planning features, or when "over-engineering", "simpler", "is this overkill", or "keep it simple" are mentioned.
☆ 21Voir le skill
GitHub
generating-rbs
Generates RBS type signatures from Ruby source files. Triggers when creating type definitions, adding types to Ruby code, or generating .rbs files for classes/modules without existing RBS signatures.
☆ 21Voir le skill
GitHub
technical-spec
Write clear, unambiguous system requirements using the EARS (Easy Approach to Requirements Syntax) methodology. Use this skill when writing system requirements, creating technical specifications, validating req...
☆ 21Voir le skill
GitHub
reference
Research reference material from URLs and create comprehensive documentation. Use this skill when users provide URLs to research, need to gather and synthesize information from web sources, or want to create st...
☆ 21Voir le skill
GitHub
git-commit-guardian
Enforces Conventional Commits format, validates message quality (72 char subject, 80 char body), and BLOCKS Claude Code pollution (co-author/generated-by markers). Use when committing, creating commits, git com...
☆ 21Voir le skill
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.