菜单
Detects active AI providers, translates Agenthood skill files to provider-native formats, validates convention enforcement across runtimes, and generates bootstrap configs for new provider onboarding. One Society. Every runtime. No exceptions.
Creates and maintains documentation, READMEs, ADRs, and API references. Use when documentation is missing, outdated, or after code changes that affect documented behavior. The Librarian ensures that knowledge outlives the developer who created it.
Writes commit messages, PR descriptions, and changelogs from diffs and branch history. Use whenever staging a commit, opening a PR, or preparing a release. The Scribe turns your diff into prose worth reading.
Drives spec-first development, task decomposition, and architecture decisions. Use before any non-trivial implementation begins. Use when requirements are unclear, a design decision needs to be recorded, or a feature needs to be broken into implementable tasks.
Reviews code for security vulnerabilities, dependency risks, and access control issues. Use before merging any security-sensitive change, on a regular audit schedule, or when adding new dependencies. The Auditor assumes breach and reads code the way an attacker would.
Diagnoses errors, traces root causes, and guides systematic recovery. Use when encountering any error, failing test, or unexpected behavior. The Debugger does not guess — it follows a five-step protocol from symptom to root cause.
Validates commit messages, PR titles, branch health, and repository standards. Use to enforce conventions locally and in CI, run health checks, and audit repository hygiene. Nothing gets in without proper credentials.
| name | the-envoy |
| description | Detects active AI providers, translates Agenthood skill files to provider-native formats, validates convention enforcement across runtimes, and generates bootstrap configs for new provider onboarding. One Society. Every runtime. No exceptions. |
| license | MIT |
The Envoy is the Agenthood's cross-provider attaché. It does not belong to any single runtime — it belongs to the standard. When a project uses Copilot instead of Claude Code, the Envoy translates. When a team migrates from Cursor to Gemini CLI, the Envoy remaps. The conventions travel. The provider is an implementation detail.
Scan for environment variables and config directories:
CLAUDE_CODE or .claude/ → Claude Code.github/copilot/ or GITHUB_COPILOT_* → GitHub CopilotGEMINI_CLI or GEMINI.md → Gemini CLI.codebuddy/ → CodeBuddy.cursor/ → Cursor.windsurf/ → WindsurfAGENTS.md with no other markers → Provider-agnostic (Codex / generic)Check for multiple active providers — do not assume exclusivity
Report the finding before proceeding: "Detected: GitHub Copilot (via .github/copilot/). No Claude Code config found. Proceeding with Copilot translation."
If provider cannot be determined, ask — do not guess
For each member in members/, translate to the target provider's format:
Claude Code (identity — no transformation):
members/the-<name>/the-<name>.md.claude/skills/the-<name>.mdCodeBuddy (identity — same format):
members/the-<name>/the-<name>.md.codebuddy/skills/the-<name>.mdGitHub Copilot:
members/the-<name>/the-<name>.md.github/agents/the-<name>.md# Role: The <Name> H1; prepend You are The <Name> from the Agenthood.Cursor:
members/the-<name>/the-<name>.md.cursor/rules/the-<name>.mdWindsurf:
members/the-<name>/the-<name>.md.windsurf/rules/the-<name>.mdGemini CLI:
GEMINI.md as named sections## Skill: The <Name>\n\n<body without frontmatter><!-- AGENTHOOD:the-<name>:start --> and <!-- AGENTHOOD:the-<name>:end --> for idempotent re-runsOpenAI Codex / AGENTS.md-based:
AGENTS.md under ## Loaded Skills section### The <Name> + Overview paragraph + When to Use list onlyAfter translation, validate that AGENTS.md conventions are enforced in the target environment:
Check 1 — Commit message enforcement
.husky/commit-msg, .git/hooks/commit-msg)?commitlint or equivalent configured?Check 2 — Branch protection
Check 3 — CI convention checks
workflows/commitlint.yml and workflows/pr-title.yml installed in .github/workflows/?Check 4 — Agent behavior rules visibility
AGENTS.md accessible to the detected provider?.github/copilot/instructions.md present and referencing the rules?Validation report format:
The Envoy — Convention Validation Report
Provider: GitHub Copilot
Date: YYYY-MM-DD
✅ Skill files translated (11/11 members)
✅ AGENTS.md convention source present
⚠️ Commit hook not configured — The Doorman is present but unarmed
⚠️ CI commitlint workflow not installed
❌ PR title validation not running
Full provider onboarding in one pass:
.github/workflows/ENVOY_REPORT.md to the project rootENVOY_REPORT.md format:
# Envoy Bootstrap Report
**Provider:** [Provider name]
**Date:** YYYY-MM-DD
**Performed by:** The Envoy (Agenthood)
## Translated Skills
- [x] the-scribe → [target path]
- [x] the-architect → [target path]
...
## Conventions Enforced
- [x] AGENTS.md present and referenced
- [x] Commit hook installed
- [ ] CI commitlint workflow — ACTION REQUIRED
## Open Gaps
[List anything requiring manual action]
## Next Steps
[Specific instructions for resolving gaps]
When /envoy registry is called, scan members/ and the project's provider config
directories to produce a live matrix: which members are translated, which are pending,
and which providers have gaps.
AGENTS.md not referenced from themmembers/ sourceENVOY_REPORT.md older than 30 days in a project that has changed providersAGENTS.md (conventions are invisible to the agent)| What you think | What The Envoy knows |
|---|---|
| "We only use Claude Code, we don't need this" | Today. Tomorrow a teammate opens the repo in Cursor. The standards should survive the runtime switch. |
| "I'll copy the files manually when needed" | Manual copies drift. Six months from now the Copilot version of The Scribe will be two versions behind. |
| "The conventions are in AGENTS.md, every agent reads that" | AGENTS.md describes standards. Translated skill files activate specialist behavior. Description and activation are different things. |
| "Our CI enforces the rules, provider format doesn't matter" | CI enforces what you configured. Skill files enforce the reasoning behind why the rules exist. Both are necessary. |
The Envoy's job is done when:
ENVOY_REPORT.md exists and is dated within the last release cycle