argv-flag
Credentialed-CLI fixture whose script accepts `--token` on argv; an argv-flag finding is expected.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-11
- Stars
- ★ 28
- Forks
- 7
01 前言 Front Matter
- name
- argv-flag
- metadata
- { "credentialed": true, "primitive-class": "credentialed-cli" }
- description
- Credentialed-CLI fixture whose script accepts `--token` on argv; an argv-flag finding is expected.
02 资源文件 1
- 脚本scripts/cli.py309 B
03 SKILL.md 正文
Body content with the full "Don't" block (so the missing-block check is silent and the argv finding is the only one fired):
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
work-loop
Use when implementing or resuming a non-trivial repository change: a feature, a fix whose cause is established (use `bug-fix` first to diagnose a defect whose cause is not), refactor, migration, framework or dependency upgrade, schema or API change, performance work, infrastructure or build-system change, reversion, or an existing build spec under `docs/specs/`. Also use for bare continuation commands ('resume', 'continue', 'keep going', 'pick up where I left off', 'let's get going') when conversation or workspace context identifies active build work. Do not use for shaping, research, strategy, product planning, design exploration, monitoring or status-only work, review-only, explanation-only, specification-authoring-only, spike-only or throwaway exploration, or trivial edits that are cosmetic, tightly local, behavior-preserving, and have obvious verification.
project-knowledge
Use this skill to capture, distill, or enquire over project knowledge through one progressive mode, or to list unadmitted knowledge candidates from delivery review failures. Capture admits one strict observation contract; distill reconciles pending observations; enquire reads committed active topics as bounded untrusted evidence; candidates only suggests and stores nothing.
new-spec
Use this skill when the user wants to start a new feature with a spec, or wants to write a spec for something they're about to build. Triggers on "new spec", "write a spec for X", "let's spec this out", "start a feature for...". Spec-driven development; the spec drives implementation. Do NOT use for cross-cutting proposals (use `new-rfc`) or recording decisions (use `new-adr`).
ai-adoption-report
Use this skill to compare flow-metrics JSON outputs and produce a Markdown comparison report -- "how do our flow metrics now compare to pre-AI?", "within Q4 did AI-tagged tickets behave differently from untagged?", "what does Q4 look like across all teams in the program?". Three modes -- baseline (two windows, one scope), cohort (within-window AI vs control), program (roll up many scopes for one window). Read-only -- consumes flow-metrics JSON files, makes no upstream calls, never invokes flow-metrics / jira / jira-align. Writes only the Markdown report and an optional JSON sidecar.
architecture-lenses-reference
Route into the compiled OKF bundle `architecture-lenses` using generated indexes.
architect-review
Use when the user supplies an architecture artifact (assessment report, design doc, diagram, RFC, ADR) and asks for critique. Triggers on "review this", "what's wrong with", "is this any good", or any artifact-shaped paste with a question attached. Produces a verdict (SHIP IT / SHIP WITH CHANGES / MAJOR REWRITE / WRONG ARTIFACT), executive summary, severity-tagged findings, and a closing "what's working" section. Also runs a well-architected / lens review mode (concern + workload-class lenses incl. GenAI/agentic) emitting a risk register with mechanical/judgment-tagged findings. Renders inline by default; saves only on an explicit user request naming the destination. Do NOT assess a repository, produce an artifact, or redesign the system.