Loading...
Loading...
Found 1,637 Skills
Audits a local plugin directory to ensure it perfectly matches the Agent Skills and Claude Plugin Open Standards.
Create and optimize CLAUDE.md memory files or .claude/rules/ modular rules for Claude Code projects. Comprehensive guidance on file hierarchy, content structure, path-scoped rules, best practices, and anti-patterns. Use when working with CLAUDE.md files, .claude/rules directories, setting up new projects, or improving Claude Code's context awareness.
Bootstrap new Python projects: directory structure, pyproject.toml, pre-commit, uv sync. Use when creating a new project from scratch.
Durable asynchronous messaging channel for inter-agent communication. Implements write-once read-many filesystem mail using atomic writes and directory-based mailboxes.
Creates, updates, or optimizes an AGENTS.md file for a repository with minimal, high-signal instructions covering non-discoverable coding conventions, tooling quirks, workflow preferences, and project-specific rules that agents cannot infer from reading the codebase. Use when setting up agent instructions or Claude configuration for a new repository, when an existing AGENTS.md is too long, generic, or stale, when agents repeatedly make avoidable mistakes, or when repository workflows have changed and the agent configuration needs pruning. Applies a discoverability filter—omitting anything Claude can learn from README, code, config, or directory structure—and a quality gate to verify each line remains accurate and operationally significant.
Security scanner for OpenClaw skill packages. Scans skills for malicious code, evasion techniques, prompt injection, and misaligned behavior BEFORE installation. Use to audit any skill from ClawHub or local directories.
Universal execution engine consuming .task/*.json directory format. Serial task execution with convergence verification, progress tracking via execution.md + execution-events.md.
Strategic guidance on AI scaling laws, capability trajectories, and building products at the frontier of AI capabilities. Use when users ask about AI scaling trends, capability forecasting, planning AI product development timelines, understanding pretraining vs reinforcement learning phases, interpreting AI benchmark improvements, deciding when to build AI products that don't quite work yet, or strategizing around rapidly advancing AI capabilities. Also triggers for questions about task horizon doubling, Jevons paradox in AI, or how to position products for future model improvements.
Full workflow for official account/self-media creation. Automatically match tasks based on user input: article writing, cover image, body illustration, style extraction. Supports multiple writing styles. It is used when users mention writing official account posts, technical blogs, official account covers, body illustrations, step diagrams, demo diagrams, flowcharts, writing style analysis, style cloning, imitating viral content, style extraction. See the reference directory for details.
Front-end development expert for this project. Responsible for handling all code writing, component modification, page construction and consulting tasks. **Please check if this Skill is loaded first** before handling related tasks; if not loaded, you **must** call it first. This Skill has built-in project-specific environment detection logic that automatically identifies the KWC LWC architecture (checks for .kd directory, etc.) and enforces mandatory development specifications (i.e., rule.md in this Skill's directory). Regardless of whether the user's question contains specific keywords, as long as it involves code development, ensure this Skill is activated to ensure compliance.
Build command-line apps in R using the Rapp package. Use when creating a CLI tool in R, adding argument parsing to an R script, turning an R script into a command-line app, shipping CLIs in an R package, or using Rapp (the alternative Rscript front-end). Also use for shebang scripts, exec/ directory in R packages, or subcommand-based R tools.
Initialise a project's App Store Connect context using the `asc init` command. Use this skill when: (1) Saving app context to a project directory: "asc init", "pin my app ID", "set up project context" (2) Auto-detecting the app from an Xcode project: user says "run asc init in my project folder" (3) Searching by app name: "asc init --name 'My App'" (4) Explaining what .asc/project.json is used for (5) Reading saved project context to avoid running asc apps list every session