菜单
Prepare a safe, versioned Skizzles release from canonical source. Use when an approved release version must be aligned across package metadata, rebuilt into the plugin, validated, and handed off for a separate tag, publication, or live cutover decision.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Coordinate work through a bounded native Codex MultiAgentV2 task graph. Read before the first subagent spawn or orchestration action in a task. Use for complexity-aware model dispatch, behavioral roles, task messaging, worker-to-worker ownership delegation, dependency fan-out, review loops, goal checkpoints, warm handoffs, synchronization, and recovery. Do not use for routine single-agent work or communication across unrelated top-level Desktop tasks.
Choose, install, diagnose, update, or uninstall Skizzles from its canonical repository. Use when a user wants plain Codex skills, the complete Skizzles plugin harness, source-linked hot reload, an isolated copied install, optional Container Lab compatibility checks, or help making a new task pick up an installed version.
Use Skizzles' bundled Container Lab launcher to create, run attached commands in, inspect, synchronize, and destroy disposable Docker Compose labs with isolated Git workspaces. Use when Docker/Compose isolation, reproducible experiments, or guarded file synchronization would help.
Stage, inspect, and validate the Skizzles versioned plugin from its canonical source tree. Use when changing plugin inputs, checking generated-plugin drift, preparing a reviewable package checkpoint, or diagnosing packaging validation failures.
Preserve authentication, authorization, session, permission, access-control, and availability semantics. Use when changing login/session flows, permission checks, API auth errors, gated UI, role-based access, token refresh, logout behavior, unavailable states, or security-sensitive user access paths.
Profile and reduce Rust/Cargo build times through measured, behavior-preserving optimization campaigns. Use when a Rust workspace has slow cold builds, slow warm rebuilds, giant crates, duplicate dependencies, expensive macros/codegen, poor Cargo parallelism, or when asked to apply the fasterthanli.me Rust build profiling methodology, split crates for build speed, inspect cargo timings, or run a long-running /goal-driven build optimization effort.
| name | release-skizzles |
| description | Prepare a safe, versioned Skizzles release from canonical source. Use when an approved release version must be aligned across package metadata, rebuilt into the plugin, validated, and handed off for a separate tag, publication, or live cutover decision. |
Release only from a clean, validated source state. Keep versioning, generated output, and live deployment as distinct decisions.
.DS_Store.PATH, or launchd state is in scope.package.json and packages/core/plugin-template/.codex-plugin/plugin.json together.bun run plugin:check to record expected pre-regeneration drift, then regenerate with bun run plugin:build; do not edit plugins/skizzles/ directly.bun install --frozen-lockfile, bun run typecheck, bun test, and bun run plugin:check.Hand the validated version, evidence, and exact remaining publication/tag/cutover steps to the release owner. Do not create tags, publish artifacts, install the plugin, or change live settings without explicit authorization.