How do I install the Team skill?

Run npx skillmds@latest add jiayaoqijia/team in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Team?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

jiayaoqijia (@jiayaoqijia) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Team by jiayaoqijia — Agent Skill

Name: Team
Author: jiayaoqijia

File contents

Agent Team Skill

Overview

Launch a coordinated team of 4 background agents to add implementation depth across the eth2028 codebase. Each agent works on non-overlapping packages to avoid conflicts.

Inputs

Target: package names or "auto" to pick packages needing depth
Count: number of files per agent (default: 4 = 2 source + 2 test)
Focus: "gap" (fix PARTIAL gaps), "depth" (add new implementations), or "both"

Workflow

Analyze - Check git status, identify packages needing depth, review gap analysis
Plan - Assign non-overlapping packages to 4 agents (2 packages per agent)
Launch - Start 4 background agents in parallel via Task tool with run_in_background: true
Monitor - Wait for all agents to complete, check for build/test failures
Verify - Run go build ./... and go test ./... on all affected packages
Commit - Stage new files, commit with descriptive message, update README stats
Push - Push to remote

Agent Assignment Rules

Each agent gets exactly 2 packages (non-overlapping with other agents)
Each agent creates 2 source files + 2 test files (4 files total)
Agents ONLY create NEW files, NEVER modify existing files
All files must be under 500 lines
All files must build and pass tests before the agent reports completion
Each test file must have 15+ test functions
Use subagent_type: "general-purpose" and mode: "bypassPermissions"

Package Priority (2026-2028 roadmap)

High priority (Glamsterdam/Hogota 2026-2027):

consensus/ - SSF, quick slots, attestations, finality
core/types/ - Transaction types, SSZ encoding
core/vm/ - EVM opcodes, precompiles, gas tables
core/state/ - StateDB, access events, prefetcher
das/ - PeerDAS, blob sampling, custody
engine/ - Engine API, payload building, forkchoice
p2p/ - Gossip, discovery, sync protocols

Medium priority (I+/J+ 2027-2028):

zkvm/ - RISC-V CPU, STF executor, proof backend
proofs/ - Proof aggregation, mandatory proofs
rollup/ - Native rollups, anchor contracts
trie/ - Binary trie, MPT migration
verkle/ - Verkle tree, state migration

Lower priority (K+/L+ 2028+):

crypto/ - BLS, KZG, PQC, threshold
txpool/ - Validation, sharding, encrypted
light/ - Header sync, proof cache
witness/ - Execution witness, collector

Commit Format

depth: add N files across M packages for <package-list>

New implementations:
- <package>: <description> (<key features>)
- <package>: <description> (<key features>)
...

Example Invocation

User: /team Agent: Launches 4 agents creating 16 files across 8 packages, waits, verifies, commits, pushes.

User: /team consensus das engine Agent: Focuses agents on specified packages.

Guardrails

Never modify existing files (agents create only)
Never switch branches or create stashes
Always verify build + tests pass before committing
Scope commits to new files only
Check for name collisions with existing types/functions before creating files
Maximum 500 LOC per file

---name: teamdescription: Launch a team of 4 parallel agents to add depth across multiple packages. Each agent creates 2 source files + 2 test files in non-overlapping packages. All files build and pass tests before committing.---# Agent Team Skill## OverviewLaunch a coordinated team of 4 background agents to add implementation depth across the eth2028 codebase. Each agent works on non-overlapping packages to avoid conflicts.## Inputs- Target: package names or "auto" to pick packages needing depth- Count: number of files per agent (default: 4 = 2 source + 2 test)- Focus: "gap" (fix PARTIAL gaps), "depth" (add new implementations), or "both"## Workflow1. **Analyze** - Check git status, identify packages needing depth, review gap analysis2. **Plan** - Assign non-overlapping packages to 4 agents (2 packages per agent)3. **Launch** - Start 4 background agents in parallel via Task tool with `run_in_background: true`4. **Monitor** - Wait for all agents to complete, check for build/test failures5. **Verify** - Run `go build ./...` and `go test ./...` on all affected packages6. **Commit** - Stage new files, commit with descriptive message, update README stats7. **Push** - Push to remote## Agent Assignment Rules- Each agent gets exactly 2 packages (non-overlapping with other agents)- Each agent creates 2 source files + 2 test files (4 files total)- Agents ONLY create NEW files, NEVER modify existing files- All files must be under 500 lines- All files must build and pass tests before the agent reports completion- Each test file must have 15+ test functions- Use `subagent_type: "general-purpose"` and `mode: "bypassPermissions"`## Package Priority (2026-2028 roadmap)High priority (Glamsterdam/Hogota 2026-2027):- `consensus/` - SSF, quick slots, attestations, finality- `core/types/` - Transaction types, SSZ encoding- `core/vm/` - EVM opcodes, precompiles, gas tables- `core/state/` - StateDB, access events, prefetcher- `das/` - PeerDAS, blob sampling, custody- `engine/` - Engine API, payload building, forkchoice- `p2p/` - Gossip, discovery, sync protocolsMedium priority (I+/J+ 2027-2028):- `zkvm/` - RISC-V CPU, STF executor, proof backend- `proofs/` - Proof aggregation, mandatory proofs- `rollup/` - Native rollups, anchor contracts- `trie/` - Binary trie, MPT migration- `verkle/` - Verkle tree, state migrationLower priority (K+/L+ 2028+):- `crypto/` - BLS, KZG, PQC, threshold- `txpool/` - Validation, sharding, encrypted- `light/` - Header sync, proof cache- `witness/` - Execution witness, collector## Commit Format```depth: add N files across M packages for <package-list>New implementations:- <package>: <description> (<key features>)- <package>: <description> (<key features>)...```## Example InvocationUser: `/team`Agent: Launches 4 agents creating 16 files across 8 packages, waits, verifies, commits, pushes.User: `/team consensus das engine`Agent: Focuses agents on specified packages.## Guardrails- Never modify existing files (agents create only)- Never switch branches or create stashes- Always verify build + tests pass before committing- Scope commits to new files only- Check for name collisions with existing types/functions before creating files- Maximum 500 LOC per file

Frequently asked questions

Team