Skip to content
Agentmart
Submit a tool

team-combat

Coordinate multiple agents to work on the combat system

Skill by jonpol01

IndexedMIT
Write a review

Chalk Labs

Need help deploying team-combat?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/jonpol01-team-combat

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Coordinate multiple agents to work on the combat system

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/team-combat

What's inside

Skill name
team-combat
Description
Coordinate multiple agents to work on the combat system
License
MIT
Instructions
26 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# /team-combat — Combat Team Orchestration

## Trigger
Run when starting a combat feature that spans design, code, art, and audio.

## Team
- lead-designer → combat design doc, balance values
- gameplay-programmer → implementation in src/systems/
- lead-artist → combat VFX and animations
- audio-designer → combat sound effects
- qa-tester → combat test plan

## Workflow
1. lead-designer writes the combat design doc
2. All team members review and flag concerns
3. gameplay-programmer implements core mechanics
4. lead-artist and audio-designer work on assets in parallel
5. qa-tester writes test plan during implementation
6. Integration: merge code + assets + audio
7. /playtest the combat system
8. Iterate based on feedback

## Handoff Protocol
Each agent writes a handoff.md in their work area when passing to the next stage.

From jonpol01/Halo-game-studio, MIT.

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Apr 1, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from jonpol01

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get team-combat running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying team-combat?

CallGet help
Cite this page

team-combat skill. Agent Mart. https://agentmart.dev/skills/jonpol01-team-combat (last updated 2026-10-24)