SkillAgentSearch skills...

envelope-team

Design and generate .envelope.json AI agent team definitions — the open standard for multi-agent teams with hierarchy, access policies, human-in-the-loop gates, and cron schedules.

Install / Use

npx skills add davepoon/buildwithclaude --skill envelope-team

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

94/100

Category

Automation

Supported Platforms

Universal

Our assessment of envelope-team

envelope-team scores 94/100 on our quality scale, 375th of 2,780 Automation skills we index (top 14%).

Its SKILL.md is 6.3 KB long, well organised into 15 sections with 6 code examples: a thorough specification that gives an agent plenty to work with.

With 3,752 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so envelope-team is actively maintained.
  • Our last check on 2026-11-16 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

envelope-team compared with similar skills

All 4 of these similar skills score higher than envelope-team; compare them before choosing.

SkillScoreStarsUpdatedFormat
envelope-team (this skill)by davepoon943.8ktodaySKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k9d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install envelope-team?
Run npx skills add davepoon/buildwithclaude --skill envelope-team. The install tabs above show the steps for each supported agent.
Which AI agents does envelope-team work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is envelope-team safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is envelope-team still maintained?
The repository was last updated today, so envelope-team is actively maintained.

name: envelope-team category: ai-ml description: Design and generate .envelope.json AI agent team definitions — the open standard for multi-agent teams with hierarchy, access policies, human-in-the-loop gates, and cron schedules.

Envelope Team

Design and generate .envelope.json AI agent team definition files — the open standard for building and deploying multi-agent teams on Envelope.

When to Use This Skill

  • User asks to build, design, or generate an Envelope team
  • User describes a workflow that could be automated by a team of AI agents
  • User wants to create a .envelope.json file for deployment
  • User needs help with agent hierarchy, access policies, or gates

What This Skill Does

  1. Takes a natural-language description of the team's purpose
  2. Designs the agent hierarchy (supervisor → managers → workers)
  3. Generates a schema-valid .envelope.json file
  4. Includes access policies, variables, secrets, and gates as appropriate
  5. Explains any schema concepts the user asks about

How to Use

Basic Usage

Build me an Envelope team for customer support triage — one supervisor,
two agents that read Zendesk tickets, and a Slack notifier for escalations.
Create an Envelope team definition for outbound sales — an SDR manager
overseeing two SDRs who work HubSpot leads and a RevOps analyst.

With human-in-the-loop gates

Build an Envelope team that drafts marketing emails and pauses for
human approval before sending.

Example

User: "Build me an Envelope team for content moderation — a supervisor and two reviewer agents that check posts against community guidelines."

Output:

{
  "$schema": "https://schema.openenvelope.org/team/v1.json",
  "name": "Content Moderation Team",
  "slug": "content-moderation",
  "version": "1.0.0",
  "description": "A supervisor and two reviewer agents that check posts against community guidelines.",
  "visibility": "team",
  "category": "ops",
  "requiredVariables": ["companyName"],
  "requiredSecrets": ["MODERATION_API_KEY"],
  "metadata": { "generatedBy": "Claude Code · openenvelope.org" },
  "agents": [
    {
      "key": "supervisor",
      "name": "Moderation Supervisor",
      "role": "supervisor",
      "capabilities": ["Route content to reviewer agents", "Aggregate decisions", "Escalate edge cases"],
      "model": "anthropic:claude-sonnet-4-5",
      "systemPrompt": "You supervise the content moderation team at {{companyName}}. Delegate each item to a reviewer and consolidate their verdicts."
    },
    {
      "key": "policy-reviewer",
      "name": "Policy Reviewer",
      "role": "reviewer",
      "capabilities": ["Check content against community guidelines", "Flag policy violations"],
      "model": "anthropic:claude-haiku-3-5",
      "systemPrompt": "You review content for policy violations at {{companyName}}. Return a verdict of approve, flag, or remove with a reason.",
      "reportsToKey": "supervisor",
      "accessPolicy": {
        "accessPolicyVersion": "1",
        "rules": [
          { "host": "api.moderation-service.com", "action": "allow" },
          { "host": "*", "action": "deny" }
        ]
      }
    },
    {
      "key": "spam-reviewer",
      "name": "Spam Reviewer",
      "role": "reviewer",
      "capabilities": ["Detect spam, bot activity, and duplicate content"],
      "model": "anthropic:claude-haiku-3-5",
      "systemPrompt": "You detect spam and bot activity at {{companyName}}. Return a verdict of approve, flag, or remove with a confidence score.",
      "reportsToKey": "supervisor"
    }
  ]
}

Schema Reference

Top-level fields

| Field | Required | Description | |---|---|---| | $schema | yes | Always https://schema.openenvelope.org/team/v1.json | | name | yes | Human-readable team name | | slug | yes | URL-safe, lowercase, hyphens only | | version | yes | Semver e.g. "1.0.0" | | description | yes | What this team does | | visibility | yes | "public" · "team" · "private" | | requiredVariables | no | Non-sensitive config, interpolated via {{varName}} | | requiredSecrets | no | API keys, stored encrypted, injected as ${SECRET_NAME} | | schedule | no | Cron schedule { cron, timezone, task } | | agents | yes | Agent definitions | | gates | no | Human-in-the-loop checkpoints |

Agent fields

| Field | Required | Description | |---|---|---| | key | yes | Unique identifier within this file | | name | yes | Display name | | role | yes | Free-form e.g. "supervisor", "analyst", "sdr" | | capabilities | yes | What this agent can do — used for delegation routing | | model | yes | e.g. anthropic:claude-sonnet-4-5, anthropic:claude-haiku-3-5 | | systemPrompt | yes | Agent instructions. Use {{varName}} and ${SECRET_NAME} | | reportsToKey | no | key of manager agent. Omit for the top-level supervisor | | accessPolicy | no | Outbound HTTP allowlist |

Hierarchy rule

Exactly one agent should have no reportsToKey — this is the supervisor that receives the initial task. All others reference their manager's key.

Access policy

"accessPolicy": {
  "accessPolicyVersion": "1",
  "rules": [
    { "host": "api.example.com", "action": "allow" },
    { "host": "*", "action": "deny" }
  ]
}

Human-in-the-loop gates

"gates": [
  {
    "name": "approval-check",
    "type": "approval",
    "trigger": { "afterAgent": "drafter" },
    "onApprove": "continue",
    "onReject": "halt"
  }
]

Tips

  • Use anthropic:claude-sonnet-4-5 for supervisors and managers; anthropic:claude-haiku-3-5 for leaf agents doing repetitive work
  • Put anything org-specific (company name, support email, Slack channel) in requiredVariables
  • End access policy rules with { "host": "*", "action": "deny" } for a strict allowlist
  • Add gates before any agent that sends emails, posts publicly, or makes purchases
  • Validate before deploying: npx @openenvelope/schema validate ./team.envelope.json

Links

Related Skills

View on GitHub
GitHub Stars3.8k
CategoryAutomation
Updated22h ago
Forks742

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions