Skills
97,501 packaged capabilities and playbooks for agents. Install any of them with one command.
Agent workflows
Automated iterative agent runner for spec-based development in Kiro. Wraps kiro-cli in a self-correcting bash loop that picks up tasks from a Kiro spec, implements them one at a time, verifies against exit criteria, and accumulates corrections and codebase patterns across iterations. Use this skill when the user mentions "ralph loop", "ralph", "spec loop", "iterative spec runner", "run my spec tasks automatically", "kiro spec automation", "self-correcting agent loop", "implement spec tasks in a loop", "run kiro-cli in a loop", "automated task implementation", or wants to drive a Kiro spec to completion through repeated agent iterations. Also use when the user wants to set up, configure, troubleshoot, or understand the Ralph Loop workflow — including progress tracking, corrections, codebase patterns, timing logs, and the summary dashboard.
Use when reporting progress in autonomous loop iterations. Triggers at the end of every autonomous loop iteration, when the autonomous-loop skill completes a BUILD phase, when progress reporting is needed for monitoring or exit evaluation, or when producing machine-parseable RALPH_STATUS blocks with exit signal protocol.
Use when the user needs prompt design, optimization, few-shot examples, chain-of-thought patterns, structured output, evaluation metrics, or prompt versioning. Triggers: new prompt creation, prompt optimization, few-shot example design, structured output specification, A/B testing prompts, evaluation framework setup.
Create and manage Claude Code skills following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns, file paths, content patterns), enforcement levels (block, suggest, warn), hook mechanisms (UserPromptSubmit, PreToolUse), session tracking, and the 500-line rule.
Converts Opus-quality skills into deterministic Haiku-executable workflows via trace-driven distillation and cross-model validation. Triggers on: "distill this skill", "make this skill work on Haiku", "cross-model optimization", "optimize skill for cost". NOT for code simplification, use code-refiner.
Use when creating skill repositories, standardizing or validating skill repo structure, setting up composer/release workflows, configuring split licensing (MIT + CC-BY-SA-4.0), fixing plugin.json / SKILL.md validation or version-parity errors, writing, changing or validating evals/evals.json assertions and samples (graded as POSIX ERE by grep -qiE), or releasing a skill version (version bump, tagging)
Authoritative framework for reviewing any proposed solution (code, config, process, tooling, or architecture decision) before implementation. Covers four core dimensions (effectiveness, side-effects/risks, feasibility, spec compliance) plus five strategic dimensions that catch decision-level failures the core four miss: reversibility calibration (Bezos one-way/two-way doors), failure-mode analysis (FMEA), operability (SRE Production Readiness Review), cost-vs-value (CBAM/WSJF), and team cognitive fit (Team Topologies). Use this skill whenever you need to review, validate, stress-test, or approve a proposed solution, plan, design doc, or approach — before any code is written or change is applied. Triggers — 「审查方案」「方案审查」「评估方案」「方案评估」「review proposal」「方案可行吗」「这个方案靠谱吗」「方案有没有风险」「方案评审」「设计评审」「决策评审」 / solution review, proposal review, design review, decision review, stress-test a plan, validate an approach.
Builds professional Claude Code skills through a smart interview, automated construction, and real eval testing. Use when a user wants to create a new skill, build a skill, turn a workflow into automation, or translate a business need into a working AI process. Also handles raw, half-baked ideas and turns them into complete skills. Triggers on: "build me a skill", "create a skill", "I want a skill that", "make a skill for", "turn this into a skill", "automate", "build a skill", "skill skiller".
Use this skill when creating, editing, or reviewing an Unreal Engine Agent Skill, a named bundle of instructions registered with the unreal-mcp server (distinct from Claude Code's harness skills under `.claude/skills/`). Trigger when the user wants to add or change a skill that the in-editor agent will load. Concrete triggers: 'create a new Agent Skill', 'add a skill for X workflow', 'edit/update this skill', 'review my skill', 'make a Python skill class', 'create a skill UAsset', 'register a skill so Claude picks it up'; writing or editing a `SKILL.md` inside a UE plugin's `Skills/` or `Python/skills/` folder; defining a Python skill class registered with the skill registry; calling `CreateSkill`, `ListSkills`, or `GetSkills` MCP tools; designing a skill's name, description, or instruction body. SKIP for: authoring a toolset (use create-toolset), invoking an existing skill at runtime (use unreal-mcp), editing harness-level Claude Code skills under `.claude/skills/` or `~/.claude/skills/`, or generic uses of the word 'skill'.
Use when you need the user to answer a batch of structured multiple-choice questions in a browser form — brainstorm decisions, picking from options, questionnaires, A/B/C choices with notes and an "Other". Requires the Playwright MCP. Not for mockups, diagrams, or visual design comparisons.
Check and update the YETONG skill bundle in the currently installed instance. Use when the user says “update Ye Tong skills,” “upgrade YETONG,” “check for a new version,” or requests a skill bundle update within YETONG. Verify the complete runtime files against the fixed official GitHub repository, back up before updating, update only files registered to this bundle, and preserve character profiles and other skills. Character DNA activation is not required.
Refactor bloated AGENTS.md/CLAUDE.md-style instruction files into a compact router plus focused on-demand docs. Use when users ask to apply progressive disclosure, split agent rules into docs, reduce instruction bloat, or turn one large rule file into an entrypoint.
arkcli shared execution protocol: first-time setup entry point, the authentication gate before running business commands, command routing and selection order, and output/security/confirmation rules. Deep details (identity resolution, AK-SK boundaries, API Key recovery, real-name gate, profile defaults and drift, temporary data-plane execution context, version checks and explicit upgrades, global flags, failure triage) are loaded on demand from references/. Triggered when the user uses arkcli for the first time, hits a not-logged-in/auth failure, asks whether the version is the latest or requests an arkcli upgrade, needs to decide between product commands and raw api, or when any arkcli-* skill needs shared context.
Use when creating or developing Laravel features, before writing code or implementation plans - refines rough ideas into fully-formed Laravel designs through collaborative questioning, alternative exploration, and incremental validation.
Claude Code config optimization skill. Use when: - Editing CLAUDE.md, rules/, skills/, agents/, commands/ - User asks about config best practices - Checking optimization status - User says "claude code changelog" or "claude code updates" - User asks about new features or breaking changes in Claude Code
Use this skill whenever the user wants to use Grok or xAI through the grok-cli command line, including chat, X search, image generation/editing, video generation/editing/extension, text-to-speech, speech-to-text, OAuth login/status, or local usage stats. This skill should also be used when grok-cli may need to be installed first; it runs the user's requested grok-cli command directly when possible, repairs install/auth/permission problems only after an actual failure, retries the original task after recovery, and returns Grok/grok-cli results without assistant-side rewriting unless the user explicitly asks for transformation.
Harness Engineering phase two: set up cross-session state management so the agent stops forgetting everything between conversations. Creates three files: tasks.json (task list), progress.md (progress log), and init.sh (environment setup script). Use immediately when the user says "set up task management", "make the agent remember progress", "create tasks.json", "keep state across sessions", "the agent never remembers what it did last time", "create a progress file", or "initialize state management". Prerequisite: harness-step1 and harness-step2 are complete (the project has AGENTS.md and a docs/ knowledge base).
Use for product feature work that explicitly needs discovery, a PRD, gated implementation planning, or stakeholder approval before code changes. Trigger for ambiguous, cross-cutting, client-requested, or high-risk functionality changes. Do not trigger for small direct code edits, routine refactors, bug fixes, security scans, documentation-only work, or questions about existing code.
The step-by-step procedure for running this repo's Promptfoo evals with a generator and a judge over provider APIs. Use when starting a new skill and needing a baseline before writing content, when a run stalls or returns no data, when a provider rate-limits, or when deciding whether an edit needs a retest.
Expert MCP (Model Context Protocol) orchestration with n8n workflow automation. Master bidirectional MCP integration, expose n8n workflows as AI agent tools, consume MCP servers in workflows, build agentic systems, orchestrate multi-agent workflows, and create production-ready AI-powered automation pipelines with Claude Code integration.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.