Skill category
Use this category when the goal is to standardize prompts, workflow definitions, and review criteria before distributing them to operators.
Profiles that help teams write, review, and maintain reusable skills.
Use the hub when you need a wider choice set, review methodology, or a different workflow path. Return to the skills overview
Use this profile when a team needs a repeatable way to screen public skills for hidden assumptions, risky permissions, or maintenance gaps.
1 source signals • Last reviewed 2026-03-11
Review source reputation and update history before installation.
Use this profile when the goal is to turn repeated prompts into stable, reviewable skills rather than one-off automation sprawl.
1 source signals • Last reviewed 2026-03-11
Prefer explicit triggers and clear boundaries over magic behavior.
Use this profile when you are comparing Claude Code skill collections and need a clear mental model for what a package is, how SKILL.md-based bundles work, and how to evaluate them before installation.
3 source signals • Last reviewed 2026-04-01
Do not blindly install unreviewed skills from SkillsMP or any other public directory.
Use this profile when Claude Code keeps missing project conventions, architecture context, or operating rules and you need to structure CLAUDE.md files deliberately instead of relying on repeated prompts.
3 source signals • Last reviewed 2026-04-01
Do not put API keys, passwords, or other secrets in any CLAUDE.md file.
Use this profile when one Claude Code session is becoming a bottleneck and the work can be split into parallel, scoped subtasks with cleaner context boundaries.
3 source signals • Last reviewed 2026-04-01
Each subagent has its own tool permissions, so define scope and allowed actions explicitly before delegation.
Use this profile when Claude Code is part of a real Git workflow and you need the collaboration pattern around branching, reviewing, and landing work to stay disciplined.
3 source signals • Last reviewed 2026-04-01
Avoid letting Claude Code automatically push to main or perform force pushes without an explicit human checkpoint.
Use this profile when the main goal is diff analysis: spotting regressions, missing tests, risky assumptions, or release-boundary mistakes before a change merges.
2 source signals • Last reviewed 2026-04-01
AI review is an assistive layer and cannot replace human review for security-sensitive, compliance-critical, or high-blast-radius code paths.
Use this profile when you need an AI-assisted security pass across application code, dependencies, secrets handling, and release surfaces before shipping or inheriting a codebase.
3 source signals • Last reviewed 2026-04-01
Audit output requires human validation before remediation or sign-off because Claude Code can miss context, overstate issues, or invent risk where none exists.
Use this profile when the repo is TypeScript-first and you want the agent to respect tsconfig boundaries, type inference, strictness, and the build scripts that already define correctness.
3 source signals • Last reviewed 2026-04-01
Do not weaken strict compiler settings just to make an AI-generated patch pass quickly.
Use this profile when the repository is built on Next.js App Router and you want Claude Code to follow the framework's routing, data-fetching, and server-client boundaries correctly.
3 source signals • Last reviewed 2026-04-01
Do not blur server-only and client-only code paths when moving logic across App Router boundaries.
Use this profile when the quality bottleneck is not installation but instruction design: project rules, system framing, few-shot examples, and stable prompt patterns that Claude Code can reuse.
3 source signals • Last reviewed 2026-04-01
Do not encode secrets, private credentials, or sensitive customer data into reusable system prompts or CLAUDE.md files.
Use this profile when you want to author, package, and iterate on Claude Code skills instead of keeping workflow logic trapped in ad-hoc prompts. It fits teams standardizing repeatable development flows across repositories.
1 source signals • Last reviewed 2026-04-02
Review any generated skill for shell commands, file writes, and tool permissions before treating it as reusable automation.
Use this profile when you want to shape Claude Code into a repeatable build system for prompts, hooks, and project bootstrap steps. It fits teams formalizing how new repos get AI-ready defaults.
1 source signals • Last reviewed 2026-04-02
Audit any bootstrap step that writes files, installs dependencies, or edits repo config before shipping it to teammates.
Use this profile when you are initializing Claude Code for a new or messy repository and need the project-level setup to become explicit. It is a good fit for teams standardizing CLAUDE.md, conventions, and baseline workflow files.
1 source signals • Last reviewed 2026-04-02
Do not copy a generic setup bundle into every repo without checking whether the project actually uses those tools, scripts, and permissions.
Use this profile when you are authoring or refining subagent workflows and need a repeatable way to verify them. It is useful for teams that treat subagents as reusable operational units rather than one-off experiments.
1 source signals • Last reviewed 2026-04-02
Test subagents against realistic tasks so they expose scope leaks, missing context, or confusing handoff behavior before wider rollout.
Need broader discovery? Skills overview
Need OpenClaw context? OpenClaw workflow