GITHUB AGENT SKILLS / 技能收录
给你的 AI 助手
装上专业技能
我们从 GitHub 持续收录、审核并分类优质的 Agent Skills,按职业与使用场景整理,复制一行命令即可安装到 Claude Code、Cursor 等智能体。
按职业浏览 Agent Skills
为不同岗位挑选的高频技能
按使用场景浏览 Agent Skills
从你要完成的任务出发
按创作者浏览 Agent Skills
按 GitHub Stars 排序的优秀创作者
Microsoft
@microsoftopenclaw
@openclawAnthropic
@anthropicsOpenAI
@openaiThe Apache Software Foundation
@apacheGitHub
@githubAutoGPT
@Significant-GravitasGarry Tan
@garrytan全部 Skills 482556
runtype-external-agents
Connect agents that run outside Runtype (Flue, Cloudflare Agents SDK, Vercel AI SDK, LangGraph, OpenAI Agents SDK, Mastra, OpenClaw, Hermes, Pi, custom loops) through OpenTelemetry/OTLP trace export or an A2A or runtype-stream endpoint, to get runs, traces, eval capture, Persona chat, or surfaces; not Runtype-hosted execution.
runtype-build-product
Build, deploy, validate, or modify Runtype-hosted AI products, agents, flows, tools, surfaces, schedules, and eval suites, including from example templates.
runtype-admin
Inspect, debug, or manage a live Runtype account through MCP or CLI; mutate only within the requested scope.
audit-agency-continuity
Run a read-only continuity and evidence audit of a persistent or autonomous agent workspace. Use when Codex must assess whether goals, memory, corrections, authority boundaries, commercial claims, schedules, or restart recovery are durable and verifiable; when an agent claims it can continue unattended; or before trusting a long-running multi-agent system after a session or machine restart.
manage-tmcra-memory
Manage and troubleshoot TMCRA long-term memory through the bundled MCP tools and Codex device authorization. Use when a user explicitly asks to remember, recall, inspect, verify, or wait for memory; configure local Writer or organizer providers; asks why a memory was used; asks to persist an important project decision; or needs to connect or reauthorize the installed Codex plugin.
manage-tmcra-memory
Recall, store, and verify long-term project memory with the TMCRA MCP tools. Use when a user explicitly asks to remember information, recover prior project context, continue work across sessions or supported agent tools, inspect an asynchronous memory write, or retry a pending write. Also use when an MCP host needs the explicit prepare-answer-commit lifecycle. Do not invoke it merely because TMCRA Hooks already supplied automatic context for an ordinary Codex turn.
why
Explain why code exists in its current form by sending one investigator to each reachable evidence source and returning a cited, confidence-graded answer. Use for "why does this exist", "why was it built this way", "where did this limit come from", "is this dead code".
unslop
Rewrite prose so it stops reading as machine-generated, using EndoStack's numbered catalog of AI-writing tells. Use on /unslop, "de-AI this", "clean up this draft", "make this plain", and whenever another skill sends text here for a slop pass.
typescript-best-practices
Sixteen type-safety rules for writing and reviewing TypeScript, with do and don't examples in references/patterns.md. Use whenever you open or edit a .ts or .tsx file, or on /typescript-best-practices.
try-endostack
Five-minute EndoStack demo. Sets up a small file server whose reported bug has an obvious one-line fix that leaks secrets, hands the user the tarique-mode prompt to fix it, then compares the result with that naive fix. Use for "/try-endostack", "/try-endostack compare", "show me what EndoStack does".
threat-model
Build a threat model for a change, feature, or system. Maps data flows, trust boundaries, assets, and entry points (including agent tool calls, retrieved documents, MCP servers, and memory), then ranks abuse paths and ties each mitigation to a test that proves it. Use for "threat model this" or "what could an attacker do here".
technical-writing
Write or review technical prose (docs, design RFCs, READMEs, PR bodies, commit messages) against four stacked public standards, then run unslop. Use on /technical-writing or any request to write, edit, or review documentation or a PR or commit message.
teach
Teach someone a diff, subsystem or idea in the code by combining how and why into a plain, paced conversation with diagrams that build up one piece at a time. Use for "teach me", "help me understand", "walk me through this change". Never edits code.
tdd
When a bug can be caught by an inexpensive local test, write that narrow failing test before the fix, check that it fails because of the bug, then fix the code and watch the test pass. Use on /tdd, "write a failing test first", "add a regression test", or when a bug has an obvious inexpensive test location.
tarique-mode
Operating mode for the rest of the chat. Routes every task to a playbook, binds always-on triggers to helper skills, sets autonomy, subagent and model-tier policy, security gates, and reply style. Load only when the user types /tarique-mode or asks to work in Tarique's mode.
tarique-help
Route questions about EndoStack (installing it, running setup, prompting tarique-mode, picking a skill, recovering from a bad run, customizing it) to the right file, and hand back one ready prompt plus a source link without starting the work. Use for "/tarique-help" or "which EndoStack skill should I use".
swarm
Launch many independent workers at once, each on its own slice of a job or all racing on one brief, then return one combined pass, problems, or blocked report. Use for "swarm this", one worker per package or directory, model races, check gauntlets, and wide exploration.
statechart
Model-check a TLA+ spec with TLC and turn the result into a reader-labeled Mermaid state diagram plus a report of the shortest path to every violated rule. Use on /statechart, to explain a bug as a walk through states, or to read any TLA+ result (formal verify skills route here).