64-team-brief-global

64-team-brief-global is a skill for Claude Code from minhnv0807/ai-business-skills. It costs 160 tokens per session (2,127 once invoked), scanned A, original, MIT.

A task-brief and meeting-template guide for assigning marketing work and running cross-functional meetings. It defines the deliverable, deadline, completion criteria, constraints, check-ins, agenda, and action items.

In plain words
What is it for?
Use it to assign a concrete marketing task, prepare an async-first meeting, or record owners and next steps.
Why use it?
It prevents vague assignments, missed deadlines, and repeated work by making expectations explicit. It also gives distributed teams a written record of decisions and follow-up tasks.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ai-business-skills plugin — 144 skills, 6 agents, 10 MCP servers shipped together

Good fit Use it to assign a concrete marketing task, prepare an async-first meeting, or record owners and next steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/minhnv0807/ai-business-skills/64-team-brief-global
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add minhnv0807/ai-business-skills --skill 64-team-brief-global
Clone the repo
git clone --depth 1 https://github.com/minhnv0807/ai-business-skills

Made for: Claude Code.

Or install ai-business-skills, the plugin that ships this one along with the rest of its 144 skills, 6 agents, 10 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for 64-team-brief-global

README.md
[![agentmods](https://agentmods.dev/badge/skills/minhnv0807/ai-business-skills/64-team-brief-global/github.svg)](https://agentmods.dev/skills/minhnv0807/ai-business-skills/64-team-brief-global)
Your own site
<a href="https://agentmods.dev/skills/minhnv0807/ai-business-skills/64-team-brief-global"><img src="https://agentmods.dev/badge/skills/minhnv0807/ai-business-skills/64-team-brief-global/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for 64-team-brief-global

Your own site · 80×15
<a href="https://agentmods.dev/skills/minhnv0807/ai-business-skills/64-team-brief-global"><img src="https://agentmods.dev/badge/skills/minhnv0807/ai-business-skills/64-team-brief-global.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 160 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,127 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00160 $0.02127
Opus 5.5 $0.00064 $0.00851
Sonnet 5.5 $0.00032 $0.00425
Haiku 4.5 $0.00016 $0.00213

Measured 1mo ago against content hash 476e953d09d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

64-team-brief-global scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/en/64-team-brief-global/SKILL.md · 177 lines

How it starts

The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Team Brief and Meeting Template (Global)

A good brief means the recipient knows exactly what to make, by when, and what "done" looks like. "Make some good content" is not a brief. "Write 3 Facebook captions on the pain angle, 200 words each, submitted Wednesday before 9:00 CET" is. Thirty minutes writing a proper brief saves three hours of rework.

Information gathering

Read .agents/product-marketing-context-global.md and the current campaign brief if available. If missing, ask up to 4 questions:

  1. What is the task, and which campaign or objective does it serve? Describe the deliverable concretely.
  2. Who is it assigned to, and do they have capacity? What role (writer, designer, media buyer, sales)?
  3. What is the real deadline? A date and a time with a timezone — "end of week" and "ASAP" are not deadlines.
  4. What does "done" mean? Measurable acceptance criteria, and where the work gets submitted.

Principles

  1. Deadlines carry a time and a timezone. On a distributed team, "Friday" means five different moments. Write "Friday 17:00 UTC" and let people convert.
  2. Important tasks get a written brief. Do not brief verbally and then blame the maker for getting it wrong.
  3. State what is NOT needed. This blocks over-delivery and scope drift.
  4. Briefing is not micromanaging. Lock the output and the standard, respect how the person works.
  5. Repeated misses mean the brief is broken. If the same person keeps missing, fix the brief before fixing the person.
  6. Two-way confirmation. The task is not assigned until the recipient confirms they understand it and accept the deadline.

Workflow

1. Scope the task and check the recipient

Check capacity before assigning: how many tasks do they hold, and which deadline comes first? If they are overloaded, choose between moving the deadline, cutting the scope, or reassigning — do not stack work and hope they absorb it.

2. Write the brief using the role template

Pick the role template below. Every brief needs: context (why), deliverable (what), done criteria (when it is finished), references (a good example and an anti-example), and constraints (hard limits).

Read the full file on GitHub · 177 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 177 lines · 160 tokens per session scan A 476e953d09d5

Subscribe to this mod's changes

64-team-brief-global is a skill published in the GitHub repository minhnv0807/ai-business-skills (631 stars, last pushed yesterday), licensed MIT. It adds 160 tokens to every session and 2,127 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.