Test Team Coordination
Execute a test scenario against a team, observing coordination pattern behaviors, evaluating acceptance criteria, and generating a structured RESULT.md. Use when validating that a team's coordination pattern produces the expected behaviors during a realistic task, comparing coordination patterns on equivalent workloads, or establishing baseline performance for a team composition.
Install
npx skills add pjt222/agent-almanac --skill test-team-coordinationgit clone --depth 1 https://github.com/pjt222/agent-almanac.git /tmp/agent-almanac
mkdir -p ~/.claude/skills
cp -r /tmp/agent-almanac/i18n/caveman-lite/skills/test-team-coordination ~/.claude/skills/test-team-coordinationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test Team Coordination Execute a test scenario from `tests/scenarios/teams/` against the target team. Observe coordination pattern behaviors, evaluate acceptance criteria, score the rubric, and produce a `RESULT.md` in `tests/results/`. ## When to Use - Validating that a team's coordination pattern produces expected behaviors - Running a structured test after modifying a team definition or agent - Comparing coordination patterns by running the same scenario with different teams - Establishing baseline performance metrics for a team composition - Regression testing after adding new agents or changing team membership ## Inputs - **Required**: Path to the test scenario file (e.g., `tests/scenarios/teams/test-opaque-team-cartographers-audit.md`) - **Optional**: Run ID override (default: `YYYY-MM-DD-<target>-NNN` auto-generated) - **Optional**: Team size override (default: from scenario frontmatter) - **Optional**: Skip scope change (default: false — inject scope change if defined) ## Procedure ### Step 1: Load and Validate Test Scenario 1.1. Read the test scenario file specified in the input. 1.2. Parse YAML frontmatter and extract: - `target` — the team to test - `coordination-pattern` — the expected pattern - `team-size` — number of members to spawn - Acceptance criteria table - Scoring rubric (if present) - Ground truth data (if present) 1.3. Verify the scenario file has all required sections: - Objective - Pre-conditions
Details
- Skill name
test-team-coordination- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/test-team-coordination/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Test Team Coordination skill do?
Execute a test scenario against a team, observing coordination pattern behaviors, evaluating acceptance criteria, and generating a structured RESULT.md. Use when validating that a team's coordination pattern produces the expected behaviors during a realistic task, comparing coordination patterns on equivalent workloads, or establishing baseline performance for a team composition.
How do I install the Test Team Coordination skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add pjt222/agent-almanac --skill test-team-coordination. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test Team Coordination popular?
It lives in pjt222/agent-almanac, which has 45 GitHub stars and 4 forks, and is included in 1 curated skill list.
Related skills
Adapt Architecture
45pjt222/agent-almanac
Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.
Adaptic
45pjt222/agent-almanac
Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.
Add Puzzle Type
45pjt222/agent-almanac
Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.
Validate Piles Notation
45pjt222/agent-almanac
Parse and validate PILES (Puzzle Input Line Entry System) notation for specifying piece fusion groups in jigsawR. Covers syntax validation, parsing into group lists, plain-language explanation, adjacency verification against puzzle results, and round-trip serialization. Use when validating user-supplied PILES strings before passing to generate_puzzle(), debugging fusion group issues, explaining the notation to users, or testing round-trip parse/serialize fidelity.
Test Shiny App
45pjt222/agent-almanac
Test Shiny applications using shinytest2 for end-to-end browser tests and testServer() for unit-testing module server logic. Covers snapshot testing, CI integration, and mocking external services. Use when adding tests to an existing Shiny application, setting up a testing strategy for a new Shiny project, writing regression tests before refactoring Shiny code, or integrating Shiny app tests into CI/CD pipelines.
Vibe to Prod
41wolverin0/claude-skills
Guided 13-layer production-readiness self-check for a vibe-coded app. Use when the user asks "is this production ready", "what am I missing before launch", "ship check", "did I forget anything", or wants to harden an AI-generated MVP. Walks the 13 layers, runs cheap detections + manual tests, emits a per-layer PASS/GAP scorecard. Lighter than /audit (which is full due-diligence).
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.