ワンクリックでManusで任意のスキルを実行

animus-pack-authoring

スター0

フォーク1

更新日2026年7月15日 21:57

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 ページを確認してインストールできます。

Manusで実行

ソース

launchapp-dev

launchapp-dev/animus-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Pack Authoring

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:

Read references/manifest.md for pack.toml structure and field definitions.
Read references/runtime-and-workflows.md for workflow exports, overlays, decision contracts, or MCP server descriptors.
Read references/operations.md only for install, uninstall, dependency resolution, pin, registry/publish, first-party pack, or schedule questions.

Minimal pack shape

Start with the smallest viable pack:

my-pack/
├── pack.toml
├── workflows/
│   └── workflows.yaml
└── runtime/
    └── agent-runtime.overlay.yaml

Authoring flow

Pick the pack kind: domain-pack, connector-pack, or capability-pack.
Write a minimal pack.toml.
Export one working workflow before adding more variants.
Add runtime overlays only for the agents and phases the pack actually needs.
Declare permissions and secrets early so activation failures are explicit.
Declare [[dependencies]] (other packs) and [[requires_plugins]] (Animus plugins) so animus pack install resolves them automatically (v0.5.14+).

Rules

Pack-qualify workflow IDs to avoid collisions.
Keep agents narrow and role-specific.
Use workflow references to compose with installed packs instead of duplicating logic.
Use decision contracts on review-style phases that should gate progress.
Test with 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.

このリポジトリの他の Skills

同じリポジトリ

document-author

launchapp-dev/animus-skills

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.

2026-07-160

animus-environment-operations

launchapp-dev/animus-skills

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.

2026-07-150

animus-portal-operations

launchapp-dev/animus-skills

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.

2026-07-150

animus-agent-personas

launchapp-dev/animus-skills

Product lifecycle agents — product owner, architect, auditor, docs-writer, devops, researcher personas

2026-07-150

animus-bootstrap

launchapp-dev/animus-skills

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.

2026-07-150

animus-mcp-setup

launchapp-dev/animus-skills

Set up .mcp.json, Claude Code permissions, and connect AI tools to Animus's MCP server

2026-07-150

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

Pack Authoring

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:

Read references/manifest.md for pack.toml structure and field definitions.
Read references/runtime-and-workflows.md for workflow exports, overlays, decision contracts, or MCP server descriptors.
Read references/operations.md only for install, uninstall, dependency resolution, pin, registry/publish, first-party pack, or schedule questions.

Minimal pack shape

Start with the smallest viable pack:

my-pack/
├── pack.toml
├── workflows/
│   └── workflows.yaml
└── runtime/
    └── agent-runtime.overlay.yaml

Authoring flow

Pick the pack kind: domain-pack, connector-pack, or capability-pack.
Write a minimal pack.toml.
Export one working workflow before adding more variants.
Add runtime overlays only for the agents and phases the pack actually needs.
Declare permissions and secrets early so activation failures are explicit.
Declare [[dependencies]] (other packs) and [[requires_plugins]] (Animus plugins) so animus pack install resolves them automatically (v0.5.14+).

Rules

Pack-qualify workflow IDs to avoid collisions.
Keep agents narrow and role-specific.
Use workflow references to compose with installed packs instead of duplicating logic.
Use decision contracts on review-style phases that should gate progress.
Test with 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.