Loading...
Loading...
Found 5,791 Skills
Expert guidance for contributing to and using the Awesome Claude Code repository, a curated collection of Claude Code skills, agents, hooks, and resources.
Deploy and run automated Attack-with-Defense (AWD) competitions where LLM-powered agents compete in real-time cybersecurity challenges
Provides MaxCompute SQL intelligent generation capabilities for AI agents, covering text2sql conversion principles, dialect syntax differences (DQL/DDL/DML), common query pattern templates (Top N, PIVOT, window functions, etc.), and ODPS error code diagnostics. Use when generating, debugging, or migrating MaxCompute / ODPS SQL.
Benchmark CodeGraph retrieval quality on a real codebase by comparing agent behavior with vs without CodeGraph. Use when the user runs /agent-eval or asks to test, benchmark, audit, or validate a codegraph version (the local dev build or a published npm version) against a language's repo.
This skill should be used when the user asks to "fix my skill" or "audit this skill". Make sure to use this skill whenever the user mentions skill quality, structural issues, broken skills, or skill diagnostics — even if they don't explicitly say "repair-skill". Not for adding features or improving effectiveness — use improve-skill. Not for agents — use repair-agent.
Build high-quality Agent Skills for Claude following official Anthropic best practices. Covers SKILL.md structure, frontmatter, description writing, progressive disclosure, testing, patterns, troubleshooting, and distribution across all surfaces (Claude.ai, Claude Code, API, Agent SDK). Use when creating new skills, reviewing skill quality, debugging skill triggering, structuring skill directories, writing skill descriptions, or improving existing skills. Triggers on "build a skill", "create a skill", "skill structure", "SKILL.md", "skill best practices", "skill not triggering", "skill quality".
Interactive QA session where users report bugs or issues through conversation, and the agent creates GitHub issues. Explore the codebase in the background to obtain context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
Use only to generate or update a governance skill card for a specified existing agent skill directory. Do not use for explaining, listing, comparing, or discussing skill capabilities.
Route agents to the right web access method only when built-in web access tools are unavailable or insufficient for the task. Use for public search/fetch, browser interaction, authenticated browsing, screenshots, web app testing, or Electron app control when built-in tools cannot handle the requirement.
Audit an AI agent skill for security risks before installing or trusting it. Runs a deterministic scanner (regex patterns, Python AST analysis, source-to-sink taint tracking, and YARA signatures) and then reasons about intent — catching prompt injection, credential exfiltration, persistence, memory poisoning, malicious code, supply-chain risks, and description-vs-behavior mismatch. Make sure to use this skill whenever the user wants to scan, audit, vet, review, or check the safety of a skill, plugin, SKILL.md, or agent tool — whether it is a local folder, a zip/.skill file, or a cloned repo — and whenever someone asks "is this skill safe to install?".
Use before any Luma / 拾光 / 拾光智能体 / 拾光工具 production workflow. Defines common luma-cli rules for auth, tool discovery, projects, artifacts, runtime resources, and safe agent behavior.
The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.