git:20261003.6414a7e to git:20261003.eedca51

2 added, 1 removed. Audit A to A.

---

name: daily-team

description: Show today's creative team and task, have the team plan it, or build it as an HTML tool. The team and task are drawn from the date, so they change every day. Use when the user asks for today's team, today's task, a creative team, or new angles on a brief.

- argument-hint: "[publish | build [1-4]] [brief]"

+ argument-hint: "[publish | recruit | build [1-4]] [brief]"

allowed-tools: Bash(sh *), Bash(cat *)

---

# Daily team

!`sh "${CLAUDE_SKILL_DIR}/team.sh"`

Request: $ARGUMENTS

- Empty request: print the team and task above as written and stop.

- `publish`: run `sh daily.sh` from this skill's folder. It records today's team and asset with the user's Claude subscription, then commits and pushes to the repository. Tell the user before running it, then report the script's output.

+ - `recruit`: run `sh recruit.sh` from this skill's folder. It drafts next week's season with the user's Claude subscription, runs the tests, pushes a branch, and opens a pull request. Tell the user before running it, then give them the pull request link.

- A brief: follow "Work the brief" with that brief instead of the task.

- `build`, an optional count from 1 to 4, then an optional brief: follow "Work the brief" for the brief, or for today's task if there is none. Then follow "Build an artifact" once per artifact, with member 1 leading the first, member 2 the second, and so on. Write each file to `team-builds/<date>/artifact-<n>.html` in the current directory instead of printing it, and give the user the path.

If the team above is missing or shows an error, run `sh team.sh` from this skill's folder and use its output.

!`cat "${CLAUDE_SKILL_DIR}/prompt.md"`