Create agent company packages conforming to the Agent Companies specification (agentcompanies/v1). Use when a user wants to create a new agent company from scratch, build a company around an existing git repo or skills collection, or scaffold a team/department of agents. Triggers on: "create a company", "make me a company", "build a company from this repo", "set up an agent company", "create a team of agents", "hire some agents", or when given a repo URL and asked to turn it into a company. Do NOT use for importing an existing company package (use the CLI import command instead) or for modifying a company that is already running in Paperclip. --- # Company Creator Create agent company packages that conform to the Agent Companies specification.
- 📁 references/
- 📁 scripts/
- 📄 SKILL.md
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or autonomous AI (3) need help with capabilities, subagents, planning, or skill mechanisms (4) ask about Claude Code, Cursor, or similar agent internals (5) want to build agents for business, research, creative, or operational tasks
Delegate coding tasks to Blackbox AI CLI agent. Multi-model agent with built-in judge that runs tasks through multiple LLMs and picks the best result. Requires the blackbox CLI and a Blackbox AI API key.
Create new agents for the code-forge application. Agents are stored as .md files in the <cwd>/.forge/agents directory with YAML frontmatter (id, title, description, reasoning, tools, user_prompt) and markdown body containing agent instructions. Use when users need to add new agents, modify existing agents, or understand the agent file structure.
Create new agents for the code-forge application. Agents are stored as .md files in the <cwd>/.forge/agents directory with YAML frontmatter (id, title, description, reasoning, tools, user_prompt) and markdown body containing agent instructions. Use when users need to add new agents, modify existing agents, or understand the agent file structure.
- 📁 .github/
- 📁 docs/
- 📁 messages/
- 📄 .dockerignore
- 📄 .env.example
- 📄 .env.test
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
Generate checklist-first CodexBridge `/agent` drafts from natural-language intake using bounded action routing, task-type templates, scope clarification, and immutable prompt scaffolds. Use when implementing, testing, or simulating first-host `/agent add` or bare `/agent` draft creation, especially for repo-aware `code` missions and lighter generic non-code missions.
Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: "PersistentAgentsClient", "persistent agents", "agent threads", "agent runs", "streaming agents", "function calling agents .NET".
Create and configure Neuron AI agents with providers, tools, instructions, and memory. Use this skill whenever the user mentions building agents, creating AI assistants, setting up LLM-powered chat bots, configuring chat agents, or wants to create an agent that can talk, use tools, or handle conversations. Also trigger for any task involving agent configuration, provider setup, tool integration, or chat history management in Neuron AI.
Delegate work to builtin or custom subagents with single-agent, chain, parallel, async, forked-context, and intercom-coordinated workflows. Use for advisory review, implementation handoffs, and multi-step tasks where a single agent should stay in control while other agents contribute context, planning, or execution. --- # Pi Subagents This skill is for the main parent orchestrator only. Do not inject or follow it inside spawned child subagents. The parent session owns delegation, orchestration, review fanout, and final fix-worker launches; child subagents should receive concrete role-specific tasks and should not run their own subagent workflows. Use this skill when the parent orchestrator needs to launch a specialized subagent, compose multiple agents into a workflow, or create/edit agents and chains on demand. ## When to Use - **Advisory review**: use fresh-context `reviewer` agents for adversarial code review, or fork to `oracle` when inherited decisions and drift matter - **Implementation handoff**: have `oracle` advise, then `worker` implement only after an approved direction - **Recon and planning**: use `scout` or `context-builder`, then `planner` - **Parallel exploration**: run multiple non-conflicting tasks concurrently - **Long-running work**: launch async/background runs and inspect them later - **Subagent control**: watch needs-attention signals and soft-interrupt only when a delegated run is genuinely blocked - **Agent authoring**: create, update, or override agents and chains for a project ## Tool vs Slash Commands Agents can use the `subagent(...)` tool directly for execution, management, status, and control.
- 📄 agent-job-background.js
- 📄 SKILL.md
Use to spawn or check on long-running background agent jobs (each launches a new Docker agent container that opens a PR when done). Trigger when the user says "create a background job", "spawn an agent", "kick off a job", "run this in the background", "check job status", or asks "what's the status of job <id>".
- 📄 ai-agent-dev.md
- 📄 SKILL.md
- 📄 skill.meta.yml
用于 AI Agent 开发岗位面试出题；覆盖 Agent 架构、LLM 调用、工具集成、MCP 协议、RAG、上下文工程与多 Agent 协作，强调工程落地与故障处理能力。
