example
Example skill in the governance-extras pack.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 30
- Forks
- 7
01 前言 Front Matter
- description
- Example skill in the governance-extras pack.
03 SKILL.md 正文
example
Minimal fixture skill.
04 同仓库更多 Skills
release-loop
Use to drive the deployed end-to-end validation outer loop — deploy the integrated whole to an ephemeral environment, run e2e, observe telemetry, feed deployed findings back to work-loop's inner loop, redeploy, and iterate until the deployed whole converges, then stop at the human consent gate for the prod ship. Run by the release-lead agent (a peer of work-loop's supervisor, not a work-loop mode). Triggers on "run the release loop", "deploy the integrated whole and iterate", "ship it to an ephemeral env and run e2e", "iterate the deployed env until it converges", "take this to a prod-ship readiness record". Autonomy is carved by minimum-regret — reversible ⇒ autonomous on ephemeral envs; irreversible ⇒ human. No engine. Do NOT use for the inner local build loop (use work-loop), to author a fidelity-ladder / local-infra-equivalents skill (that is the inner-loop obligation), or to run the live product as a managed service (adopter ops).
generate-iac
Use this skill to author governed, best-practice Terraform/OpenTofu infrastructure from a plain-language intent. Triggers on "provision X", "create Terraform for", "generate IaC for", "set up cloud resources", "write Terraform for", "scaffold infrastructure". Stops at a digest-pinned `terraform plan` (G4 handoff); never runs `apply`. Governance-first — resolves the decision-record surface before any code.
content-design
Use when someone asks what a surface should communicate or how its copy should feel before final words are written, or when a team needs a cross-surface brand register. Runs in three modes: message and narrative structure for a content brief; per-surface acquisition copy goals for a copy-direction record; brand-level register for named, ranked voice goals and arbitration rules. Use `ux-writing` for final product UI strings and state microcopy, `creative-direction` for visual mood, and `information-architecture` for page hierarchy. Organization-level content strategy belongs to `define-content-strategy`; product positioning and growth strategy stay upstream; implementation belongs to `frontend-engineering`. Triggers on "shape the message hierarchy before we wireframe", "set ranked copy goals for this landing page", and "define how our brand should sound across product and marketing".
security-checklists-reference
Route into the compiled OKF bundle `security-checklists` using generated indexes.
jira
Read and mutate Jira (Atlassian Cloud or self-hosted Server / Data Center) via the REST API. Supports JQL search with auto-pagination, fetching issues / projects / users, creating and updating issues, applying workflow transitions, adding comments and attachments, deleting issues, listing projects, looking up users, and an arbitrary raw escape hatch. Streams results as JSON, JSONL, or CSV. Handles Cloud (REST v3, basic auth with email + API token, ADF, nextPageToken) vs Server/DC (REST v2, bearer Personal Access Token, plain text, startAt) differences automatically. Use when the user wants to read, search, export, create, update, or transition Jira data.
jira-team-status
Team backlog status for sprint, stand-up, and orientation — what the team can pick up, what is ready, blocked, in progress, unassigned, stale, or needs story work. Triggers on "show me the team backlog", "what can the team pick up", "what is ready", "what is blocked", "what is unassigned", "sprint status", "stand-up summary", "stale team work". Applies the five-question bar only when explicitly asked for agent-ready or one-PR work. Always start read-only; disclose scope and completeness. Do NOT use to improve weak stories (use jira-story-triage), create an issue (use jira), apply approved updates (use jira), turn an epic into specs (use jira-brief-intake), fix a defect end-to-end (use jira-defect-flow), or for local repository work that is ready, active, or blocked (use work-loop's dispatch.py).