GITHUB AGENT SKILLS / 技能收录

给你的 AI 助手
装上专业技能

我们从 GitHub 持续收录、审核并分类优质的 Agent Skills,按职业与使用场景整理,复制一行命令即可安装到 Claude Code、Cursor 等智能体。

01 /

按职业浏览 Agent Skills

为不同岗位挑选的高频技能

全部职业
02 /

按使用场景浏览 Agent Skills

从你要完成的任务出发

全部场景
03 /

按创作者浏览 Agent Skills

按 GitHub Stars 排序的优秀创作者

全部创作者

全部 Skills 482556

AgentParadise
AgentParadise/agent-paradise-standards-system

code-review

Review source changes for defects.

开发工程师代码审查
★ 3
AgentParadise
AgentParadise/agent-paradise-standards-system

code-review

Review source changes for defects.

开发工程师代码审查
★ 3
AgentParadise
AgentParadise/agent-paradise-standards-system

releasing-apss

Use when cutting, gating, tagging, or publishing a release of this APSS repo, or when explaining how releases work here. Trigger phrases: "cut a release", "release APSS", "publish to crates.io", "create a release PR", "main to release", "promote main to release", "bump versions for the release", "tag a release", "run the release gate", "how do releases work here", "what gets published", "ship a new version", "publish a new crate for the first time", "403 Forbidden publishing to crates.io", "this token does not have the required permissions", "CARGO_REGISTRY_TOKEN", "publish-new scope", "the publish job failed", "half the crates published". Covers the trunk-based main -> release branch flow, the Release Gate checks (source-branch, version-bump, changelog, QA, APS validation, security), release-create.yml tagging plus tiered crates.io publishing, and the one-time manual first publish a NEW crate name requires because the CI token is deliberately scoped publish-update only. Do NOT use for routine feature PRs into main (those need no release and no version bump), mid-feature version bumps, authoring standards, or consumer-side `apss install` (see the adopt/visualize runbooks).

★ 3
Grimblaz
Grimblaz/agent-orchestra

webapp-testing

Playwright end-to-end testing guidance for web apps, with practical patterns and setup steps. Use when creating or improving browser-based E2E coverage, test stability, and CI execution. DO NOT USE FOR: React component tests (use ui-testing), canvas game interaction (use browser-canvas-testing), TDD workflow (use test-driven-development), debugging failures (use systematic-debugging), or randomized property tests (use property-based-testing).

测试与质量前端开发
★ 3
Grimblaz
Grimblaz/agent-orchestra

verification-before-completion

Evidence-based verification checklist before marking work complete. Use before PRs, releases, marking tickets done, or any "I'm finished" declaration; also when naming a baseline commit for a differential suite claim, when designing a mutation campaign or red-run evidence, when making an absence claim, a universal claim, or a one-time demonstration offered as a standing guarantee, when attributing a measurement or claiming a sweep or verification loop is complete, and when stating what a check or a CI suite will do about a change. DO NOT USE FOR: post-merge cleanup or archival (use post-pr-review) or processing GitHub review comments (use code-review-intake).

★ 3
Grimblaz
Grimblaz/agent-orchestra

validation-methodology

Reusable validation and review methodology for staged validation, failure triage, and prosecution-depth setup. Use when running validation ladders, triaging failures, or executing adversarial review passes. DO NOT USE FOR: CE Gate orchestration, specialist dispatch ownership, or step execution flow (keep those in Code-Conductor).

★ 3
Grimblaz
Grimblaz/agent-orchestra

upstream-onboarding

Shared opening-phase protocol for upstream agents (Experience-Owner, Solution-Designer, Issue-Planner) and Code-Conductor when invoked on an existing GitHub issue. Renders a scaled context brief and runs a standards check on inherited work at each phase boundary. Use when a user-invocable agent receives a request referencing an existing GitHub issue and must load solution-authoring and upstream-onboarding at the opening phase. DO NOT USE FOR: subagent dispatches (which already operate within an assessed session context); post-merge review (use post-pr-review); research or non-tree subagents.

人力资源Skill与智能体开发
★ 3
Grimblaz
Grimblaz/agent-orchestra

ui-testing

Resilient React component testing strategies focusing on user behavior. Use when writing or reviewing component-level React tests, fixing flaky component tests, or establishing React testing patterns. DO NOT USE FOR: Playwright E2E tests (use webapp-testing), canvas game interaction (use browser-canvas-testing), TDD workflow (use test-driven-development), debugging failures (use systematic-debugging), UI component design (use frontend-design), or randomized property tests (use property-based-testing).

设计师测试与质量前端开发
★ 3
Grimblaz
Grimblaz/agent-orchestra

ui-iteration

Reusable screenshot-driven UI polish workflow for iterative visual refinement. Use when improving layout, hierarchy, spacing, feedback, or Tailwind-based presentation through repeated review-and-adjust passes. DO NOT USE FOR: functional bug fixing, accessibility-only audits, or major redesign strategy work (use Code-Smith or frontend-design).

设计师前端开发
★ 3
Grimblaz
Grimblaz/agent-orchestra

tracking-format

Tracking-file frontmatter and coordination format guidance. Use when creating or reviewing local tracking files and related handoff conventions. DO NOT USE FOR: session-memory plan authoring rules outside the documented references here.

★ 3
Grimblaz
Grimblaz/agent-orchestra

test-driven-development

Test-Driven Development workflow guidance, quality standards, and practical patterns. Use when writing tests first, implementing to pass tests, validating quality gates, or refactoring safely; also when placing a hazardous or non-returning test file, when changing CI suite selection or a dot-sourced runner library, when a suite passes locally and fails only on CI, when claiming a rule is covered by the surrounding tests, when writing a test docstring that names a cross-surface invariant, and when writing a test that fabricates hostile input. DO NOT USE FOR: debugging existing failures (use systematic-debugging), React component test patterns (use ui-testing), E2E browser tests (use webapp-testing), randomized property verification (use property-based-testing), or architecture evaluation and design decisions (use software-architecture)

测试与质量
★ 3
Grimblaz
Grimblaz/agent-orchestra

terminal-hygiene

Terminal and test execution guardrails plus session-cost discipline for Agent Orchestra workflows. Use when choosing sync/async terminal mode, scoping Pester runs, retrying background commands, recovering from multiline-prompt stalls, wrapping subagent diagnostics, avoiding terminal/subagent batching mistakes, or applying session-cost discipline; also when a PowerShell expression returns an unexpected type, an array collapses to a scalar or a single element, a parameter binding or splat behaves unlike the call you wrote, or an ordered literal, pipeline, or here-string parses differently than written. DO NOT USE FOR: application-level debugging (use systematic-debugging), post-merge archival (use post-pr-review), or cost telemetry/measurement setup (use copilot-cost-collection).

Skill与智能体开发
★ 3
Grimblaz
Grimblaz/agent-orchestra

systematic-debugging

4-phase debugging process (Observe, Hypothesize, Test, Fix) for complex issues. Use when debugging fails, investigating flaky tests, tracking root causes, or facing mysterious bugs. DO NOT USE FOR: writing new tests (use test-driven-development), React component test patterns (use ui-testing), or E2E test setup (use webapp-testing).

测试与质量
★ 3
Grimblaz
Grimblaz/agent-orchestra

subagent-env-handshake

Subagent environment-handshake contract for Claude Code Agent-tool dispatch. Use when a parent session dispatches a subagent that may make tree-grounded claims such as file existence, branch identity, or landed changes - the handshake lets the subagent verify its live working-tree view matches the parent's before it prosecutes tree-grounded findings. DO NOT USE FOR: research subagents that never touch git/tree state; Copilot subagent dispatch (execution model differs).

律师与法务
★ 3
Grimblaz
Grimblaz/agent-orchestra

step-commit

Discrete validated-step commit workflow for Code-Conductor. Use when capturing per-step validated work as structured commits. DO NOT USE FOR: deciding whether auto-commit is enabled or replacing the PR-time formatting gate.

★ 3
Grimblaz
Grimblaz/agent-orchestra

specification-authoring

Structured authoring guidance for formal specification documents. Use when drafting machine-readable requirements, filling the repository specification template, or refining interfaces and acceptance criteria into a self-contained spec. DO NOT USE FOR: implementation planning (use plan-authoring) or broad design exploration (use brainstorming)

★ 3
Grimblaz
Grimblaz/agent-orchestra

solution-authoring

Reusable engagement-gate methodology for content-authoring decisions in upstream phases. Use when classifying a decision as load-bearing or routine, authoring a decision brief, handling an override or decline, capturing articulation, or evaluating skip rules. DO NOT USE FOR: GitHub setup, completion-marker ownership, or adversarial review pipeline orchestration.

★ 3
Grimblaz
Grimblaz/agent-orchestra

software-architecture

Clean Architecture, SOLID principles, and architectural decision guidance. Use when evaluating layer boundaries, dependency flow, design contract violations, or ADR-level decisions. DO NOT USE FOR: open-ended idea exploration (use brainstorming), UI component design (use frontend-design), writing tests (use test-driven-development), or coordinating parallel implementation lanes (use parallel-execution).

前端开发
★ 3