菜单
Build Animus workflow packs - `pack.toml`, workflow exports, runtime overlays, MCP server descriptors, schedules, and marketplace operations. Use when creating or updating installable Animus packs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Authoring policy for producing Office documents (xlsx/pptx/docx) as `document` subjects. Used by the author-document workflow's generate phase — draft a spec, render+store via the animus-document-engine store_document tool, then record it with create_subject.
Operate Animus v0.7 execution environments — environment plugins and coder nodes, the cross-phase environment broker, workflow/phase `environment:` pinning, `environment_routing:` rules, `workspaces:` multi-repo checkout sets, lease records and the startup reaper, and animus-environment-railway. Use when pinning workflows to remote execution, debugging node acquisition or teardown, or authoring multi-repo runs.
Operate the Animus portal (animus-launchapp) — the flat-named portal MCP surface and admin-only tool visibility, Claude/Codex subscription Connections, the external MCP-server catalog with Connect handshake and ext.* subject projection, the durable script registry and phase_context_schema authoring loop, team_* workflow authoring over MCP, and trigger-event observability. Use when driving a portal deployment rather than a local CLI install.
Product lifecycle agents — product owner, architect, auditor, docs-writer, devops, researcher personas
Guide a project from idea to autonomous engineering setup — interview the user, write VISION.md, AGENT_PRINCIPLES.md, registry, agents/workflows/phases/schedules YAML, scripts, and a first runnable task. Use when standing up Animus in a new project beyond the minimal /animus-setup scaffold.
Set up .mcp.json, Claude Code permissions, and connect AI tools to Animus's MCP server
| name | animus-pack-authoring |
| description | Build Animus workflow packs - `pack.toml`, workflow exports, runtime overlays, MCP server descriptors, schedules, and marketplace operations. Use when creating or updating installable Animus packs. |
| user_invocable | true |
| auto_invoke | true |
| animus_version | 0.7.0-rc.18 |
Workflow packs bundle reusable Animus workflows, runtime overlays, and optional MCP integrations.
Do not read the full pack manual before starting. Open only the reference that matches the file you are editing:
pack.toml structure and field definitions.Start with the smallest viable pack:
my-pack/
├── pack.toml
├── workflows/
│ └── workflows.yaml
└── runtime/
└── agent-runtime.overlay.yaml
domain-pack, connector-pack, or capability-pack.pack.toml.[[dependencies]] (other packs) and [[requires_plugins]] (Animus plugins) so animus pack install resolves them automatically (v0.5.14+).animus pack info --path ./my-pack before installing or publishing (the pack inspect alias was retired in v0.5.14), and preview dependency/plugin resolution with animus pack install --path ./my-pack --dry-run.If the task shifts from manifest work to runtime overlays or registry operations, open the corresponding reference file instead of broad-reading every pack detail.