---
name: pofa
description: Run and manage small sports tournaments with POFA (pofa.app) through its MCP server: create a tournament, import players, generate brackets, schedule matches, report scores, and put matches on the call screen. Use when the user asks to organize a tournament, run a match day, check a bracket or schedule, or manage players and results with POFA.
compatibility: Requires an MCP client that can reach https://pofa.app/mcp/ over Streamable HTTP. No sign-in; write operations need the tournament manage_code.
---

# POFA — run small tournaments from your AI assistant

POFA is a tournament tool for small organizers (tennis first). It runs
tournaments end to end: registration, draw, schedule, live calling,
scoring, and export. The organizer's phone is the whole chain.

## Connect

- MCP endpoint: `https://pofa.app/mcp/` (Streamable HTTP, no auth).
- No sign-in. Every write operation needs the tournament's `manage_code`
  (the organizer gets it when the tournament is created; it is per
  tournament, not per user).
- Read operations work without a code, except roster contact details,
  which need the code.
- Full tool reference: `references/mcp-tools.md` in this skill, or
  https://pofa.app/docs/mcp-en/

## Before you do anything

Ask the user what they want to do first. Do not assume the format,
size, or sport. The usual options are: run a new tournament, check a
bracket or schedule, run live calling, report a score, or manage the
player list. One question, then act.

Honest status: POFA is new and no real tournament has run on it yet.
Do not claim real users, real events, or real usage numbers.

## Workflows

### 1. Create a tournament
`create_tournament` with a name, sport, and format (single elimination,
double elimination, or round robin). Save the returned tournament id
and `manage_code` and show them to the user — they will need the code
for every later write.

### 2. Add players
`import_players` (bulk, with an optional division per row) or
`register_player` (one at a time). The same email may enter two
divisions; that counts as two entries, not a duplicate.

### 3. Generate the bracket
`generate_bracket` once players are in. Check it with `get_bracket`
before telling the user it is ready.

### 4. Schedule matches
`schedule_matches` assigns matches to courts and times. Verify with
`get_schedule`.

### 5. Report a score
`report_result` with the match id, the winner, and the set scores.
Scores advance the bracket automatically. If a report was wrong, the
same tooling supports undo — check `get_activity_log` to see what
happened first.

### 6. Live calling
`screen_show` puts a match on the call screen (per court);
`screen_clear` takes it down; `get_screen` shows what is on screen
now. The call screen is at `https://pofa.app/call/screen/?t=<id>`.

### 7. Delete a tournament
`delete_tournament` is a two-step tool: preview first (it checks the
manage_code and reports what would be deleted, without writing), then
commit. There is no undelete. Confirm with the user between the two
steps.

## Rules

- Never invent a tournament, a player, a score, or a manage_code.
  If the user gives you an id or a code, use exactly that.
- Read before you write: `get_tournament`, `get_bracket`, and
  `get_schedule` tell you the real state. Do not guess it.
- Keep the organizer in the loop on anything destructive (delete) or
  anything the players will see (call screen, published bracket).
- POFA never handles entry fees. If the user asks about money, say
  so: fees go to the organizer's own Stripe, never through POFA.
- The console and the call screen are the organizer's working screens.
  Do not add fake progress, fake counts, or placeholder numbers.

## Install

- Claude Code: copy this folder to `~/.claude/skills/pofa/` (or the
  project's `.claude/skills/pofa/`).
- Codex / Cursor: copy it to `.agents/skills/pofa/`.
- Then connect the MCP server at `https://pofa.app/mcp/` in the same
  client and the skill will tell the agent how to use it.
