conforming
A credentialed-CLI fixture skill that satisfies every lint check; lint should report zero findings.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 29
- Forks
- 7
01 前言 Front Matter
- name
- conforming
- metadata
- { "auth": "creds", "credentialed": true, "primitive-class": "credentialed-cli" }
- description
- A credentialed-CLI fixture skill that satisfies every lint check; lint should report zero findings.
02 资源文件 1
- 脚本scripts/cli.py337 B
03 SKILL.md 正文
A no-op fixture skill used by T10's conventions-check lint tests.
Security rules (non-negotiable)
- Secrets live only in
~/.agentbundle/credentials.env(mode 0600 on POSIX; DACL-restricted on Windows), the OS keyring, or process environment variables. Never read that file, print it, or echo the token. - Never put the token on the command line. The primitive
refuses flags like
--token/--api-token/--bearer/--pat/--passwordand exits — do not work around it. - If
checkexits with the "missing credentials" code, tell the user to runagentbundle creds setup <namespace>themselves. It's interactive — do not run it for them.
04 同仓库更多 Skills
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).
jira-story-triage
Review Jira work items for readiness and improve weak stories — it explains why each item is not ready (which question failed and the specific gap), identifies unresolved human questions, drafts proposed rewrites and acceptance criteria, and writes to Jira only after you approve the exact payload; read-only until then. Triggers on "which stories are not ready", "which stories need more detail", "improve these weak stories", "make these tickets actionable", "draft better acceptance criteria", "apply the story-readiness bar", "explain why these items are not ready", "prepare Jira story improvements without writing". Do NOT use for a read-only team status snapshot or what to pick up next / blocked / unassigned / in progress / stand-up (use jira-team-status), to create an issue (use jira), to apply approved updates to named issues (use jira), to turn an epic into specs (use jira-brief-intake), or to fix a defect end-to-end (use jira-defect-flow).
jira-align
Read and mutate Jira Align (Atlassian Cloud or self-hosted/on-prem) via the REST API 2.0. Supports fetching individual records (epics, features, stories, capabilities, themes, portfolios, programs, teams, users, etc.), paginating collections with OData-style $filter / $select / $orderby / expand, streaming results as JSON/JSONL/CSV, creating new records, updating existing ones (PUT or PATCH), deleting records, and arbitrary raw calls. Use when the user wants to read, search, export, create, or update Jira Align data.