- 📁 examples/
- 📁 references/
- 📄 SKILL.md
This skill should be used when the user asks to "create a hedera plugin", "build a hedera agent kit plugin", "extend hedera agent kit", "create custom hedera tools", "add hedera functionality", "write a hedera tool", "implement hedera tool", or needs guidance on Hedera Agent Kit plugin architecture, tool definitions, mutation tools, query tools, or parameter schemas using Zod.
百度地图Map Agent Plan，官方为 Agent专属AI地图技能，直连 place、direction、geocoding、reverse_geocoding、weather 五大核心能力，大模型一键调用地图服务。
Use this skill when an agent is managing its own micro.blog identity with mb. It covers autonomous posting, voice consistency, disclosure, and how an agent should participate as itself rather than impersonating a human user.
Use Telegram as a chat interface to Agent Zero's LLM. Set up a persistent bot that listens in designated chats and routes messages through the agent.
- 📁 .github/
- 📁 acp-research/
- 📁 adrs/
- 📄 .dockerignore
- 📄 .gitignore
- 📄 acp_diag.sh
**任意两个 Agent 建立直接通信。零注册、零配置、框架无关。**
- 📄 metadata.json
- 📄 SKILL.md
Migration guide from @openrouter/sdk to @openrouter/agent for callModel, tool(), stop conditions, and agent features. This skill should be used when code imports callModel, tool(), or stop conditions from @openrouter/sdk and needs to migrate to @openrouter/agent.
Use this skill when the user wants to manage AI agent knowledge, organize agent configurations, or set up post-session learning systems. Triggers include: organizing agent skills or knowledge into a structured shelf, extracting insights from conversation transcripts, splitting monolithic agent config files into modular pieces, managing memory files, searching indexed knowledge, or diagnosing shelf health. Use ShelfAI whenever a user mentions managing agent context, chunking configs, learning from sessions, compacting memory, or organizing reusable agent knowledge pieces.
- 📁 agents/
- 📁 references/
- 📄 SKILL.md
Use when working in a repo that uses Codaph and you need shared agent history, a fresh context block before starting Claude or Codex, a checkpoint before risky edits, diagnostics for agent loops, or explicit handoffs between agents.
Governance framework for deciding whether a new capability should be an agent, a skill, or handled by the main agent directly. Use this skill BEFORE creating any new agent or skill. Triggers on: "I need the system to do X", "should this be an agent?", "add capability for X", "create an agent for X", "we need a new agent", "should I make a skill for this?". Also activates when the skill-creator skill is about to be used — architect runs first as a gatekeeper to prevent agent/skill sprawl. Use proactively whenever you're about to create something new in .claude/agents/ or .claude/skills/. --- # Architect — Capability Design Framework You're about to add a new capability to AOS. Before writing any code or creating any files, run through this framework to determine the right form factor: **agent**, **skill**, **main agent**, or **extend existing**. ## The Company Model
Use when the user says "add a facade", "new tool", "extend vault", "add brain feature", "new skill", or "extend agent". For extending the agent's own internals with vault-first knowledge gathering. --- # Agent Dev — Vault-First Internal Development Develop the agent's own internals with the vault as the primary source of truth. The vault knows more about the agent than any code scan or model training data. Always search the vault first, extract maximum context, and only then touch code. ## When to Use Any time the work target is the agent's own codebase: adding tools, extending facades, modifying vault operations, brain features, skills, or transport. Not for projects that merely _use_ the agent. ## Core Principle **Vault first. Before code. Before training data. Always.** The vault is the authoritative source for how the agent works. Do not rely on general knowledge from training data — it is outdated and lacks project-specific decisions. Do not scan the codebase to understand architecture — the vault already has it. ## Orchestration Sequence ### Step 1: Search the Vault (MANDATORY — before anything else) Before reading any source file, before making any plan, before offering any advice: ```
bmad-master agent
