64 Team Brief Global

What it does

When your agent uses it

• A leader assigns work to a marketing team member
• Runs a cross-functional meeting — a task brief with concrete deliverables
• A deadline with time and timezone
• A definition of done

Example prompts

• “assign a task”
• “brief for my team”
• “team brief”
• “/64-team-brief-global”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

1. 1Scope the task and check the recipient
2. 2Write the brief using the role template
3. 3Set check-in points for complex tasks
4. 4Assign and confirm
5. 5Accept against the done criteria

What it can do on your machine

Read from SKILL.md and the folder at commit 0360adc. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

64 Team Brief Global loads about 2.3k tokens when it runs. Until then it costs about 189 tokens; SKILL.md has 827 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~189

When it runs · the whole SKILL.md, loaded when a task matches

~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from minhnv0807/ai-business-skills at commit 0360adc, republished under its MIT licence (© minhnv0807). 827 words, ~2,274 tokens.

name

64-team-brief-global

description

Use when a leader assigns work to a marketing team member or runs a cross-functional meeting — a task brief with concrete deliverables, a deadline with time and timezone, a definition of done, constraints, and check-in points, plus an async-first meeting agenda and action-item template. Trigger on 'assign a task', 'brief for my team', 'team brief', 'definition of done', 'meeting agenda template', 'my team keeps delivering the wrong thing'. Also use when the user says nobody knows who owns what. Not for — the campaign brief the whole team executes from, see `02-campaign-brief-global`; briefing an external agency or freelancer, see `67-agency-vendor-brief-global`; evaluating performance, see `65-team-performance-review-global`.

metadata.version

1.0.1

metadata.category

operations

license

MIT

triggers

assign a task, brief for my team, team brief, 1:1 brief, definition of done, meeting agenda template, marketing standup agenda, delegate work to the team

output

File .md — a task brief by role (writer / designer / media buyer / channel owner) or meeting notes with an agenda and action items carrying owners and deadlines

related

product-marketing-context-global, 02-campaign-brief-global, 62-marketing-review-global, 65-team-performance-review-global, 41-campaign-asset-list-global…

# Task Brief — [Task name]

Assigned to: [name] · Assigned by: [leader] · Date: [date]
Deadline: [day, date, time + timezone]
Priority: Urgent / High / Normal

## Why this task matters
[2-3 sentences: which campaign or objective it serves, why the deadline matters]

## What to produce
| # | Deliverable | Detailed spec | Format | Quantity |
|---|-------------|---------------|--------|----------|
| 1 | | | | |
| 2 | | | | |

**Not in scope:** [list explicitly what is out of scope]

## Definition of done
- [ ] [Criterion 1 — measurable, not vague]
- [ ] [Criterion 2]
- [ ] Submitted to: [folder / channel / method]

## Reference material
- Brand voice / brand guideline: [link]
- Campaign brief: [link]
- Good reference: [link + why it is good]
- Anti-reference, do NOT copy: [link + why]

## Constraints
- [Hard limits: banned words, claims that cannot be made, mandatory format]

## Check-in points
- [Date]: submit first draft for review
- [Date]: final after feedback
- If blocked or unsure: raise it immediately, do not guess

# Meeting notes — [Topic] — [Date]

Attendees: [name + function] · Chair: [name] · Notetaker: [name]
Duration: [30-45 minutes] · Timezone: [reference timezone + local equivalents]

## Pre-read (circulated [X] hours before)
- Results vs target: [link to dashboard or report]
- Written updates from anyone who cannot attend live: [link to thread]

## Agenda (live time = decisions only)
| # | Topic | Presenter | Time |
|---|-------|-----------|------|
| 1 | Questions on the pre-read | | 5 min |
| 2 | Blockers | | 15 min |
| 3 | Decisions to make | | 20 min |
| 4 | Assignments for next period | | 5 min |

## Decisions made
| Decision | Basis (data/insight) | Accountable | Revisit when |
|----------|----------------------|-------------|--------------|

## Action items
| Task | Owner | Deadline (with timezone) | Done when |
|------|-------|--------------------------|-----------|

## Open questions
| Question | What is needed to decide | Owner | Due |

© minhnv0807, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/en/64-team-brief-global of minhnv0807/ai-business-skills.

Open the folder on GitHubat commit 0360adc