setup-benny-pack
Direct instructions for validating a copied Benny pack. This file is dormant and is not a registered plugin skill.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 109
- Forks
- 19
01 前言 Front Matter
- name
- setup-benny-pack
- description
- Direct instructions for validating a copied Benny pack. This file is dormant and is not a registered plugin skill.
03 SKILL.md 正文
Validate the copied Benny pack
Use the registered $setup-benny skill as the authority. Confirm this file is at .codex/automations/benny/skills/setup-benny/SKILL.md, configuration is outside the copied pack under .codex/benny/, and mutable state is in one absolute, shared, owner-only canonical directory outside all worktrees.
Validate every field in ../../templates/configuration.example.yaml. Credential entries are external references only. Record least-privilege scopes, config and operational-file hashes, source-managed file hashes, atomic-state proof, allowed network hosts, retention, canaries, stable automation IDs, and activation blockers in .codex/benny/setup-receipt.json without secret values.
Reconcile exactly two stable automation names only after explicit user authorization. Update stored IDs rather than duplicating them and force both descriptors to PAUSED. Do not activate either job from this file.
04 同仓库更多 Skills
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing. Must always apply.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for $technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.