Verified source command
OpenClaw Setup
Use this profile when the main outcome is getting OpenClaw running with sane defaults, channel bindings, and a clear operator handoff.
curl -fsSL https://openclaw.ai/install.sh | bashSkills directory
Find agent skills you can actually evaluate and use
This directory now prioritizes profiles with verified source commands, visible risk context, and clear paths into guides, manuals, and related OpenClaw workflows. Do not expect fake install snippets or thin mirror pages.
Command-ready now
Command-ready profiles
These profiles currently expose verified upstream commands or setup paths.
Verified command directory
Verified source command
OpenClaw Channel Operations
Use this profile when OpenClaw has to coordinate across messaging channels, browser actions, and everyday operator interventions.
npm install -g openclaw@latestHow to use this directory
Command first
Open profiles with verified source commands when you need something directly usable instead of conceptual copy.
Review before trust
Use review categories and methodology before treating any public skill or command as production-safe.
Route into workflows
After choosing a skill, continue into OpenClaw, guides, or comparisons instead of bouncing back to the homepage.
Curated resources
AI Coding Tools: Practical Selection Guide for Product Teams
Use this playbook to choose coding assistants that improve delivery speed safely.
AI Research Tools: Selection Guide for Market and Product Teams
Use this guide to pick research assistants that support confident decision-making.
AI Productivity Tools: How to Build a Lean, High-Impact Stack
Use this playbook to avoid tool sprawl and keep only tools that improve execution.
OpenClaw Setup
Use this profile when the main outcome is getting OpenClaw running with sane defaults, channel bindings, and a clear operator handoff.
OpenClaw Security Hardening
Use this profile when OpenClaw is moving beyond local experiments and you need clear isolation, credential, and review controls.
OpenClaw Channel Operations
Use this profile when OpenClaw has to coordinate across messaging channels, browser actions, and everyday operator interventions.
Categories
OpenClaw
Profiles for setup, rollout, and daily operating patterns around OpenClaw.
Use this category when the main job is getting OpenClaw deployed safely and keeping it usable in everyday channels.
Channel Operations
Profiles for keeping multi-channel assistants stable across gateway and message workflows.
Use this category when the work spans Telegram, WhatsApp, Discord, browser automation, or internal operator loops.
Skill Authoring
Profiles that help teams write, review, and maintain reusable skills.
Use this category when the goal is to standardize prompts, workflow definitions, and review criteria before distributing them to operators.
Claude Code Workflows
Profiles for Git, MCP, subagents, and day-to-day Claude Code operating patterns.
Use this category when the goal is to improve how Claude Code integrates into your development workflow — commits, reviews, parallel agents, and external tool connections.
Language & Frameworks
Profiles optimized for specific languages or frameworks: TypeScript, Next.js, Python, and more.
Use this category when you need Claude Code guidance that is specific to a language or framework conventions, toolchain, and ecosystem.
Prompt Engineering
Profiles for writing better Claude Code instructions, CLAUDE.md configuration, and system prompt patterns.
Use this category when the work is about improving how you instruct Claude — not just using Claude, but getting it to behave correctly and consistently across your project.
Decision strip
Use this strip when you already know the next job and just need the fastest handoff.
Newsletter
Claude Code & Agent Skills Weekly
每周精选：值得安装的 skills、workflow 技巧、安全提醒。Bruce Yang 亲测推荐。
Bruce Tested
Personally reviewed and tested by Bruce Yang
Source instructions only
Claude Code Skills Packages
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.
Source instructions only
CLAUDE.md Setup
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.
Source instructions only
Subagents Workflow
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.
Community Curated
Verified source command
OpenClaw Setup
Use this profile when the main outcome is getting OpenClaw running with sane defaults, channel bindings, and a clear operator handoff.
curl -fsSL https://openclaw.ai/install.sh | bashSource instructions only
OpenClaw Security Hardening
Use this profile when OpenClaw is moving beyond local experiments and you need clear isolation, credential, and review controls.
Verified source command
OpenClaw Channel Operations
Use this profile when OpenClaw has to coordinate across messaging channels, browser actions, and everyday operator interventions.
npm install -g openclaw@latestEditorial profile
Skill Safety Review
Use this profile when a team needs a repeatable way to screen public skills for hidden assumptions, risky permissions, or maintenance gaps.
Editorial profile
Skill Authoring Blueprint
Use this profile when the goal is to turn repeated prompts into stable, reviewable skills rather than one-off automation sprawl.
Source instructions only
MCP Server Setup
Use this profile when Claude Code needs live access to databases, APIs, file systems, or operator tools through MCP and you want the connection model to stay legible.
Source instructions only
Claude Code Git Workflow
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.
Source instructions only
AI Code Review Skill
Use this profile when the main goal is diff analysis: spotting regressions, missing tests, risky assumptions, or release-boundary mistakes before a change merges.
Source instructions only
Security Audit Skill
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.
Source instructions only
TypeScript Project Skill
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.
Source instructions only
Next.js App Router Skill
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.
Source instructions only
Prompt Engineering Skill
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.
Source instructions only
claude-code-skillforge
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.
Source instructions only
claude-code
Use this profile when you need a general Claude Code operating pattern rather than one narrow sub-workflow. It is useful for teams wiring Claude Code into daily development and repo maintenance.
Source instructions only
claude-expert
Use this profile when the problem is less about installation and more about getting consistently strong Claude Code output. It fits operators who want better prompt framing, review habits, and session control.
Source instructions only
claude-forge
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.
Source instructions only
wave-planner-claude
Use this profile when a task is too large for one flat execution pass and needs staged planning. It is useful for operators who want Claude Code to break delivery into deliberate waves before implementation.
Source instructions only
claude-code-hook
Use this profile when you need Claude Code to trigger structured actions around development events such as setup, validation, or workflow handoff. It is most useful when hook behavior needs to stay predictable and reviewable.
Source instructions only
claude-project-setup
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.
Source instructions only
claude-code-project-config
Use this profile when Claude Code already runs in a repo but the project-level config is weak, inconsistent, or drifting. It is helpful for teams refining hooks, instructions, and repo defaults after the first install.
Source instructions only
update-claude-md
Use this profile when a repository already has Claude instructions but they are outdated, incomplete, or drifting from reality. It is especially useful after toolchain changes, workflow shifts, or repeated assistant mistakes.
Source instructions only
memory-management-working-memory-format-claudemd
Use this profile when the challenge is not creating CLAUDE.md but deciding how to format persistent working memory inside it. It fits teams that want repo instructions, plans, and context blocks to stay readable for both humans and Claude Code.
Source instructions only
gstack
Use this profile when you need Claude Code to operate with a more opinionated execution stack for QA, review, or shipping workflows. It is a good fit for teams that want repeatable command flows instead of improvising every task from scratch.
Source instructions only
ai-coding-workflow
Use this profile when you want a general development workflow for Claude Code rather than a narrow skill or tool integration. It is useful for operators standardizing how AI-assisted coding moves from spec to implementation to validation.
Source instructions only
mcp-servers
Use this profile when the main question is which MCP servers to add and how they fit into a Claude Code workflow. It helps when a team is moving from simple chat usage toward tool-connected automation.
Source instructions only
mcp-apps-builder
Use this profile when you are building an app experience that depends on MCP rather than only adding one server. It fits teams shaping product flows where Claude Code or another agent coordinates multiple MCP-backed capabilities.
Source instructions only
flowstudio-power-automate-mcp
Use this profile when Claude Code or another agent needs to participate in a Power Automate oriented toolchain through MCP. It is useful for teams bridging agent workflows with enterprise automation systems.
Source instructions only
mcp-builder
Use this profile when the work is about authoring an MCP integration from scratch or shaping a new server around existing systems. It is useful for developers who need Claude-compatible tooling that does not exist yet.
Source instructions only
mcp-cli
Use this profile when the main need is to inspect, run, or manage MCP behavior from a terminal-oriented workflow. It is useful for developers who prefer a direct CLI layer over app-specific setup surfaces.
Source instructions only
ap2-mcp-server
Use this profile when an agent workflow needs payment-related capabilities through MCP rather than only local dev tools. It is useful for builders connecting commerce or transaction flows to Claude-compatible tooling.
Source instructions only
acp-checkout-mcp
Use this profile when an MCP integration needs to represent checkout steps inside a commerce workflow. It is useful for builders exposing purchase actions to agents in a more structured way.
Source instructions only
ucp-checkout-mcp
Use this profile when an agent needs to participate in checkout flows through a dedicated commerce MCP toolset. It helps when you want checkout steps to be agent-addressable without opening up the entire commerce system.
Source instructions only
webmcp-mcp-bridge
Use this profile when an agent needs MCP-mediated access in browser-heavy or web automation contexts. It fits teams connecting interactive web workflows to model-accessible tools.
Source instructions only
configure-canvas-mcp
Use this profile when MCP needs to support Canvas app configuration or similar low-code admin flows. It is helpful for teams bringing app-configuration work into an agent-friendly tool surface.
Source instructions only
clude-memory-mcp
Use this profile when Claude-oriented workflows need shared memory or persistent context beyond the current session. It is useful for teams experimenting with memory-backed agent tooling and prompt persistence.
Source instructions only
read-write-workflow
Use this profile when an OpenClaw or Claude-style workflow benefits from clearly separating context gathering from mutation steps. It is useful for operators who want safer execution in workspaces where reading and writing should not blur together.
Source instructions only
subagent-testing
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.
Source instructions only
weapon-add-workflow
Use this profile when a repo has a repeatable flow for introducing new weapon-related data, content, or logic and you want Claude Code to follow that path consistently. It fits domain workflows where new entries should be added with the same review pattern every time.
Source instructions only
character-add-workflow
Use this profile when a repo has a standard process for introducing new character-related content, data, or logic and you want Claude Code to follow it consistently. It works best for structured content systems where additions should conform to an existing pattern.
Source instructions only
subagent-driven-development
Use this profile when implementation work naturally splits into bounded subtasks that can be delegated to subagents. It is useful for teams trying to turn parallel Claude Code execution into a repeatable development pattern.
Source instructions only
moleworks-subagent-orchestrator
Use this profile when the main challenge is not spawning one subagent, but coordinating several of them cleanly. It is useful for teams designing a more formal orchestration layer on top of delegated Claude workflows.
Source instructions only
vc-workflow
Use this profile when a team has a named internal workflow and wants Claude Code to follow it consistently across tasks. It is useful when the value comes from reusing a house process rather than inventing a new prompt each time.
Source instructions only
subagent-gen
Use this profile when you want to create new subagents more systematically instead of hand-authoring each one from scratch. It is useful for teams scaling a subagent library and needing a more repeatable generation flow.
Source instructions only
ss-subagent-driven-development
Use this profile when delegated implementation work should stay tied to a stronger specification or planning layer. It is useful for teams combining subagent execution with a more formal delivery method.
Source instructions only
scoping-context-for-subagents
Use this profile when subagent quality problems come from context overload, missing inputs, or fuzzy task boundaries. It is useful for teams that already use delegated workflows and now need sharper context discipline.