菜单
Prepare runtime integrations such as Orgo.io, Composio, AgentMail, Granola, and Genome's Notion with setup tasks, health checks, approval gates, and tracking fields.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | integration-setup |
| description | Prepare runtime integrations such as Orgo.io, Composio, AgentMail, Granola, and Genome's Notion with setup tasks, health checks, approval gates, and tracking fields. |
Use this skill when a runtime integration must be discovered, prepared, dry-run, or diagnosed before automation uses it.
~/agentic_os.agentic-os runtime init --root <root> if integration-registry.yml is missing.agentic-os integration list --root <root> and identify the integration id.agentic-os integration setup <integration_id> --root <root> --dry-run.agentic-os integration doctor <integration_id> --root <root>.agentic-os notion track-runtime --root <root> --dry-run; apply only with --verified-workspace "Genome's Notion".Each integration record must include:
setup_taskshealth_checksapproval_gatescredentials.env_varsnotion_trackingGroom rough software ideas into source-backed implementation specs with original intent, capability discovery, tracker hierarchy, QA, Gherkin, and Notion documentation projection.
Append environment variables to ~/.zshenv on bigmac, genomesbox, and the Mac laptop in one step. Use when the user pastes `KEY=value` pairs and asks to add them to zshenv, or when setting secrets that need to be available on all three hosts. ssh aliases `bigmac`, `genomesbox`, and `mac` are already configured where needed.
Commit all local changes in logical groups until the repository is clean. Use when the user asks to commit everything, make all needed commits, or cleanly commit the full worktree without pushing.
Help users operate the published Composio CLI to find the right tool, connect accounts, inspect schemas, execute tools, subscribe to trigger events with `composio listen`, script workflows with `composio run`, and call authenticated app APIs with `composio proxy`. Use when the user asks how to do something with `composio`, wants to run a known tool slug, needs to discover a slug with `composio search`, fix a missing connection with `composio link`, inspect tool inputs with `--get-schema` or `--dry-run`, troubleshoot top-level CLI flows, or explicitly needs `composio dev` guidance.
Use when the user wants to work a LOS Jira ticket or non-trivial LOS task in a dedicated fast worktree, especially when they mention /workon, /orchestrate, fast worktree, use a worktree, or parallel agents.
Use when working or resuming LOS Jira implementation in a fast worktree with minimal chat output, especially after noisy /workon loops, repeated stack setup, test polling, or context/token burn.