Loading...
Loading...
Found 5,792 Skills
Scaffold a new integration-type "seed skill" — a SKILL.md with reference assets and prompts.jsonl entries that teach an agent to generate working, testable integration code from scratch. - Use when: developer wants to create a new skill for an SDK or framework integration that agents should be able to implement and test - Ask first: Is this an integration skill (code generation + tests) or a tool skill (CLI wrapper with no tests)? Only proceed with this skill for integration-type skills.
Replace with a description of what this skill does and when Claude should use it. Include keywords that help agents discover and activate this skill.
How agents discover and use skills. Use to understand skill invocation protocol.
Terminal-Bench integration for Mux agent benchmarking and failure analysis
Global Agent rules, including language, response style, debugging priority, engineering quality baseline, mandatory code metric limits, security baseline, test verification standards and Skills routing table. Applicable to all programming tasks.
Send USDC from the t2000 agent wallet to another address on Sui. Use when asked to pay someone, transfer funds, send money, tip a creator, or make a payment to a specific Sui address. Do NOT use for API payments — use t2000-pay for x402-protected services.
Open standards and governance rules for Agent Skills. It is used for creation, modification, refactoring, migration, audit and maintenance of skills, and provides platform-independent structural standards, frontmatter specifications, progressive disclosure and quality gates.
Documentation-driven development specification that requires Agent to consult official documentation and examples before generating code or fixing bugs, including API verification processes, search strategies and MCP invocation rules. It is applicable to scenarios such as accessing third-party libraries, troubleshooting API errors, and version changes.
Deep persona design for Agentforce agents with 50-point scoring. TRIGGER when: user designs agent personas, defines agent personality/identity, creates persona documents, encodes persona into Agent Builder fields, or asks about agent tone/voice/register. DO NOT TRIGGER when: building agent metadata (use sf-ai-agentforce), testing agents (use sf-ai-agentforce-testing), or Agent Script DSL (use sf-ai-agentscript).
Universal Assistant — Automatically analyzes scenarios, takes inventory of ECC resources, intelligently routes to the optimal agent pipeline, and completes complex workflows with one click.
(Industry standard: Routing Agent / Orchestrator Pattern) Primary Use Case: Analyzing an ambiguous trigger and routing it to one of the specific specialized implementations. Routes triggers to the appropriate agent-loop pattern. Use when: assessing a task, research need, or work assignment and deciding whether to run a simple learning loop, red team review, dual-loop delegation, or parallel swarm. Manages shared closure (seal, persist, retrospective, self-improvement).
Bootstrap, install, and operate an external task-management CLI as the source of truth for agent execution tracking (instead of built-in todos). Provides the abstraction layer between spec-management intent (implementation plans and tasks) and concrete CLI commands. MUST be invoked when any implementation-tier artifact (SPEC, STORY, BUG) comes up for implementation — create a tracked plan before writing code. Optional but recommended for complex SPIKEs. For coordination-tier artifacts (EPIC, VISION, JOURNEY), spec-management must decompose into implementable children first — this skill tracks the children, not the container. Also use for standalone tasks that require backend portability, persistent progress across agent runtimes, or external supervision. Use this skill whenever the user asks to track tasks, create an implementation plan, check what to work on next, see task status, manage dependencies between work items, or close/abandon tasks — even if they don't mention "execution tracking" explicitly.