After Action Report
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
A skill your agent uses when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an…
Install 66 Crisis Playbook Global
$ npx skills add minhnv0807/ai-business-skills --skill 66-crisis-playbook-global -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install minhnv0807/ai-business-skills 66-crisis-playbook-global --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/en/66-crisis-playbook-global .claude/skills/66-crisis-playbook-global && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "66-crisis-playbook-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/66-crisis-playbook-global into .claude/skills/66-crisis-playbook-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "66-crisis-playbook-global", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/66-crisis-playbook-globalType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add minhnv0807/ai-business-skills --skill 66-crisis-playbook-global -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install minhnv0807/ai-business-skills 66-crisis-playbook-global --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/en/66-crisis-playbook-global .agents/skills/66-crisis-playbook-global && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "66-crisis-playbook-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/66-crisis-playbook-global into .agents/skills/66-crisis-playbook-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "66-crisis-playbook-global", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add minhnv0807/ai-business-skills --skill 66-crisis-playbook-global -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install minhnv0807/ai-business-skills 66-crisis-playbook-global --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/en/66-crisis-playbook-global .cursor/skills/66-crisis-playbook-global && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "66-crisis-playbook-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/66-crisis-playbook-global into .cursor/skills/66-crisis-playbook-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "66-crisis-playbook-global", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/minhnv0807/ai-business-skills.git --path skills/en/66-crisis-playbook-global--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add minhnv0807/ai-business-skills --skill 66-crisis-playbook-global -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install minhnv0807/ai-business-skills 66-crisis-playbook-global --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/en/66-crisis-playbook-global .gemini/skills/66-crisis-playbook-global && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "66-crisis-playbook-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/66-crisis-playbook-global into .gemini/skills/66-crisis-playbook-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "66-crisis-playbook-global", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install minhnv0807/ai-business-skills 66-crisis-playbook-globalInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add minhnv0807/ai-business-skills --skill 66-crisis-playbook-global -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/en/66-crisis-playbook-global .github/skills/66-crisis-playbook-global && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "66-crisis-playbook-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/66-crisis-playbook-global into .github/skills/66-crisis-playbook-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "66-crisis-playbook-global", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add minhnv0807/ai-business-skills --skill 66-crisis-playbook-global -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install minhnv0807/ai-business-skills 66-crisis-playbook-global --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/en/66-crisis-playbook-global .opencode/skills/66-crisis-playbook-global && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "66-crisis-playbook-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/66-crisis-playbook-global into .opencode/skills/66-crisis-playbook-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "66-crisis-playbook-global", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
66-crisis-playbook-global- GitHub stars
- 609
- Token cost
- ~2.8k tokens
- SKILL.md length
- 1,264 words
- Files
- 1
- Skills in repo
- 142
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an…
- Works in 4 steps: What type of crisis is this? Match it… → How fast is it spreading? Ten people or… → Where did it start? An unhappy customer,… → …
- A brand faces a communications CRISIS
- SKILL.md covers Information gathering, Principles, Crisis classification and Process by level, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
66 Crisis Playbook Global is an agent skill from minhnv0807/ai-business-skills. Use when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an escalation matrix, a do-not-do list, holding statements, and a post-mortem. Trigger on 'PR crisis', 'crisis playbook', 'a complaint is going viral', 'bad reviews are spreading', 'our content caused backlash', 'we are getting attacked online'. Also use when the user forwards an angry thread and asks what to do right now. Not for —…
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Social media marketing, Runbooks and postmortems and Retrospectives. The repository describes itself as: 138 bilingual AI marketing skills (69 VN + 69 Global) for Claude Code, OpenCode, Codex, VS Code. Four role SOP packs — content, design, performance, leader ops — plus strategy… The licence is MIT.
When your agent uses it
- A brand faces a communications CRISIS
- A campaign is failing in public — L1 to L5 severity classification
- A first-four-hours process
- Response templates by type
Example prompts
- “PR crisis”
- “crisis playbook”
- “a complaint is going viral”
- “/66-crisis-playbook-global”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- What type of crisis is this? Match it against the L1-L5 table below.
- How fast is it spreading? Ten people or ten thousand? One channel, or has it jumped channels?
- Where did it start? An unhappy customer, a creator or influencer, a competitor, a regulator, or the press?
- What is actually true? Which fact is disputed, do you have evidence, and do you have enough to respond at all?
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
66 Crisis Playbook Global loads about 2.8k tokens when it runs. Until then it costs about 188 tokens; SKILL.md has 1,264 words of instructions outside code blocks.
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
Auto-check passed
The automated check found no risky patterns in SKILL.md.
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). 1,264 words, ~2,770 tokens.
Download SKILL.mdSave it as
.claude/skills/66-crisis-playbook-global/SKILL.md (or your agent's skills folder).- name
- 66-crisis-playbook-global
- description
- Use when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an escalation matrix, a do-not-do list, holding statements, and a post-mortem. Trigger on 'PR crisis', 'crisis playbook', 'a complaint is going viral', 'bad reviews are spreading', 'our content caused backlash', 'we are getting attacked online'. Also use when the user forwards an angry thread and asks what to do right now. Not for — monitoring before anything blows up, see `15-social-listening-global`; diagnosing weak performance numbers, see `03-performance-eval-global`; the routine post-campaign review, see `63-campaign-retrospective-global`.
- metadata.version
- 1.0.1
- metadata.category
- operations
- license
- MIT
- triggers
- crisis, crisis playbook, PR crisis, campaign is failing, content caused backlash, bad reviews spreading, complaint going viral, brand under attack online
- output
- File .md — crisis classification, hour-by-hour response plan, who does what, what to say and not say, escalation matrix, post-mortem
- related
- 15-social-listening-global, 03-performance-eval-global, 63-campaign-retrospective-global, 07-marketing-report-global, 62-marketing-review-global
Crisis Playbook (Global)
A crisis arrives without warning, so the playbook must exist before it is needed. Three ground rules: (1) do not react before you have facts — most crises look worse than they are in the first 30 minutes; (2) do not stay silent past 4 hours on a spreading crisis, because silence reads as admission; (3) handled well, a crisis builds trust; handled badly, it destroys it permanently.
Information gathering
Read the 15-social-listening-global report if available (early detection). Before doing anything, answer 4 questions:
- What type of crisis is this? Match it against the L1-L5 table below.
- How fast is it spreading? Ten people or ten thousand? One channel, or has it jumped channels?
- Where did it start? An unhappy customer, a creator or influencer, a competitor, a regulator, or the press?
- What is actually true? Which fact is disputed, do you have evidence, and do you have enough to respond at all?
If you do not have enough information: publish one short line confirming you are investigating and commit to a specific update time. Do not go silent, and do not respond to unverified claims.
Principles
- Assess first, react second. Thirty to sixty minutes of investigation beats a wrong answer in five minutes.
- Never silent past 4 hours on a spreading crisis.
- Do not delete legitimate negative comments (clear spam and hate speech excepted) — deleting escalates.
- Do not argue in public. Move the complainant to a private channel.
- Do not respond while emotional. Draft it, wait 30 minutes, reread, then send.
- Do not promise what you cannot deliver, and do not minimize the facts.
- L3 and above must go to the leader. Never self-handled.
- Regulated categories escalate straight to legal. In health, finance, insurance, credit, and crypto, any challenge to a claim goes directly to legal review — do not draft a public response first.
Crisis classification
| Level | Type | Example | Priority | Response window |
|---|---|---|---|---|
| L1 | Operational — campaign or system failure, severe KPI miss | Ads not delivering, landing page down, tracking broken | High | 2-4 hours |
| L2 | Content — inaccurate or misleading content published | Misleading caption, wrong figure, inappropriate image | High | 2-4 hours |
| L3 | Reputation — customer complaint spreading | Viral one-star review, exposé thread | Critical | 1-2 hours |
| L4 | Brand attack — coordinated | Mass fake reviews, competitor smear, brigading | Critical | Same day |
| L5 | Legal / compliance / data | Deceptive-advertising or undisclosed-endorsement complaint, personal data breach, IP infringement, platform enforcement action | Critical + counsel | Immediate |
Process by level
L1 — Operational
In the first 2 hours: pull the full data set to find where the real number sits; diagnose the root cause (run 03-performance-eval-global); notify leadership with a hypothesis and actions; deploy the emergency fix.
Report template: "Campaign [X] is at [actual] against a target of [target]. Preliminary cause: [hypothesis]. In progress: [3 actions]. Next update at [time]."
L2 — Content
Immediately: screenshot and archive the evidence BEFORE removing anything; take down the affected post (faster than apologizing on the broken post); notify the leader, do not self-handle.
Within 2-4 hours: establish what was wrong, who was affected, and the reach; draft the response and have the leader approve it before posting (run 62-marketing-review-global).
Response template: "We found that [content X] in our [date] post contained [an error / inaccurate information]. We have [removed / corrected] it and apologize for the confusion. The correct information is: [...]. Thanks to [the person who flagged it] for raising it."
L3 — Reputation
Immediately: do NOT delete comments, do NOT argue in public, archive all evidence with timestamps.
Within 1-2 hours: verify whether the complaint is legitimate.
- If legitimate: acknowledge, apologize, fix, compensate. Template: "[Name], we're sorry about this experience. That is not the standard we intend. Could you send us a direct message so we can resolve it with you directly?"
- If not legitimate: state the facts calmly with evidence, and do not escalate the tone.
Note: in US and EU markets, review platforms are part of the crisis surface. Respond on the platform where the complaint lives, and never incentivize or suppress reviews to offset it — that is itself an FTC issue.
L4 — Brand attack
Archive evidence with timestamps; notify leadership immediately; weigh staying silent (a small-scale attack is amplified by responding) against speaking up (if it is spreading); never respond emotionally; report coordinated inauthentic behavior through the platform's own reporting flow; consult counsel if there are signs of defamation.
Show full SKILL.md (538 more words)Show less
L5 — Legal, compliance, and data
Stop every related campaign IMMEDIATELY. Notify leadership. Consult counsel before doing anything else, and make no public statement before legal input. Route by trigger:
| Trigger | First move |
|---|---|
| Claim challenged as deceptive, or an endorsement ran without disclosure | Pause the asset, pull the substantiation file and the creator contract, route to counsel. FTC exposure attaches to the advertiser, not only the creator |
| Personal data exposed or accessed without authorization | Notify your data protection lead or counsel the moment you become aware. Under GDPR a controller has a 72-hour duty to report a qualifying breach to the supervisory authority, and affected individuals must be told without undue delay where the risk is high. Do not wait for full facts to start the clock |
| California or other US state privacy complaint (CCPA/CPRA and equivalents) | Route to counsel; preserve the request and response record, do not respond ad hoc |
| Platform policy enforcement (account restricted, ads disapproved at scale, page unpublished) | Do not spin up backup accounts. File the platform appeal, document the disputed asset, and fix the underlying policy issue |
| Regulated category (health, finance, insurance, credit, crypto) | Any claim issue escalates straight to legal review before any response is drafted |
This playbook coordinates the response. It does not give legal advice, and it does not replace counsel on any of the triggers above.
Escalation matrix
| Level | Handled by | Who must know | Timeline |
|---|---|---|---|
| L1 | Media buyer + leader | Leadership same day | 2-4 hours |
| L2 | Content + leader | Leadership if reach > 10K | 2-4 hours |
| L3 | Leader | Leadership immediately | 1-2 hours |
| L4 | Leadership + leader | Board or executive team if needed | Same day |
| L5 | Leadership + counsel | Board or executive team, plus the data protection lead for any data incident | Immediate |
Do-not-do list
- Delete legitimate negative comments.
- Argue or trade emotional replies with an angry person.
- Respond before verifying the facts.
- Promise compensation or a fix you may not be able to deliver.
- Lie, or downplay the severity.
- Stay silent past 4 hours while a crisis spreads.
- Let a junior decide the response at L2 or above.
- Buy, incentivize, or suppress reviews to offset negative sentiment.
- Open replacement ad accounts to work around a platform enforcement action.
- Make a public statement on a legal or data matter before counsel has seen it.
Output structure
# Crisis Response — [Incident name] — [Date/time]
## 1. Initial assessment
| Item | Content |
|------|---------|
| Classification | L[1-5] — [type] |
| Origin | |
| Current scale | [estimated reach, number of channels] |
| Verified facts | |
| Unverified claims | |
## 2. Hour-by-hour response plan
| Time window | Action | Owner | Status |
|-------------|--------|-------|--------|
| 0-1h | | | |
| 1-4h | | | |
| 4-24h | | | |
| Day 2-7 | | | |
## 3. Messaging
Approved to say: [...]
Not to say: [...]
Single spokesperson: [...]
Channels used: [...]
## 4. Internal actions
| Task | Owner | Deadline |
|------|-------|----------|
## 5. Monitoring
| Metric | Before | After 24h | After 7 days |
|--------|--------|-----------|--------------|
| Sentiment | | | |
| Mention volume | | | |
| Inbox / complaints | | | |After the crisis
After one week: write the post-mortem (what happened, how it was handled, the outcome), update this playbook with the new lessons, and run a team session so it does not repeat. If the crisis was campaign-related, fold it into 63-campaign-retrospective-global.
Related skills
15-social-listening-global: early detection before it becomes a crisis, and sentiment tracking during and after.03-performance-eval-global: root-cause diagnosis for L1 operational crises.62-marketing-review-global: approve the response content before publishing.63-campaign-retrospective-global: extract systemic lessons once it is resolved.07-marketing-report-global: report the impact on monthly KPIs.
Quality checklist
- Classified to the correct level before responding
- Evidence archived with timestamps before anything was removed
- Facts in the response verified
- Response approved by the leader (mandatory at L2 and above)
- Single spokesperson — not several people answering differently
- Nothing on the do-not-do list was done
- Legal, data, and platform-enforcement triggers routed to counsel before any public statement
- Sentiment monitoring scheduled at 24 hours and 7 days
- Post-mortem scheduled within one week
© 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/66-crisis-playbook-global of minhnv0807/ai-business-skills.
Open the folder on GitHubat commit 0360adc
Compare with similar skills
66 Crisis Playbook Global next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| 66 Crisis Playbook Global this skillminhnv0807/ai-business-skills | 609 | — | ~2.8k | Automated safety check: Pass | MIT | |
| After Action Reportrampstackco/claude-skills | 945 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Launch Retro Analyzeraaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Incident RetrospectiveOpenHands/extensions | 163 | — | ~922 | Automated safety check: Pass | MIT | |
| Self ImproverAffitor/affiliate-skills | 701 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Release Retrospectivemurphytrueman/design-system-ops | 206 | — | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
Launch Retro Analyzer
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "run a launch retro / post-mortem", "compare launch results vs targets by channel", or "decide what to keep or kill for the next launch"; produces a…
Incident Retrospective
OpenHands/extensions
Create an automation that drafts incident retrospectives. An agent skill from OpenHands/extensions.
Self Improver
Affitor/affiliate-skills
Review affiliate campaign results and improve strategy. An agent skill from Affitor/affiliate-skills.
Release Retrospective
murphytrueman/design-system-ops
Review how a shipped release, migration or deprecation went against its plan: blast radius, comms, migration, timeline, support load, each gap classed.
Launch Retrospective
Ootto-AI/claude-content-skills
Use after a social launch, campaign, creator collaboration, or distribution test has enough evidence to decide what should be repeated, changed, or stopped.
More from minhnv0807/ai-business-skills
All 142 skills in this repoDesign Master
minhnv0807/ai-business-skills
Handles eight kinds of marketing visual requests, from logos and campaign key visuals to infographics and quote graphics, by generating images or writing paste-ready prompts.
Offer Design
minhnv0807/ai-business-skills
Designs or repairs what a business sells, covering the promise, value stack, bonuses, guarantee, honest scarcity and a tiered ladder, rather than price or copy.
Global SEO Growth
minhnv0807/ai-business-skills
Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.
B2B Lead Generation
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
Community Seeding Plan
minhnv0807/ai-business-skills
Plans honest participation in outside communities such as Reddit, Discord and Facebook Groups, with a rules-based community list, roster, posts, replies and calendar.
Ad Conversion Tracking Setup
minhnv0807/ai-business-skills
Sets up and verifies conversion tracking before ad spend: Meta Pixel and CAPI, Google Ads, GA4, TikTok, server-side GTM, consent mode, UTMs and a pre-launch checklist.
Related
Questions about 66 Crisis Playbook Global
What does 66 Crisis Playbook Global do?
A skill your agent uses when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an…. 66 Crisis Playbook Global is an agent skill from minhnv0807/ai-business-skills. Use when a brand faces a communications CRISIS or a campaign is failing in public — L1 to L5 severity classification, a first-four-hours process, response templates by type, an escalation matrix, a do-not-do list, holding statements, and a post-mortem.
When should I use 66 Crisis Playbook Global?
66 Crisis Playbook Global fits situations like: A brand faces a communications CRISIS; A campaign is failing in public — L1 to L5 severity classification; A first-four-hours process; response templates by type.
How do I install 66 Crisis Playbook Global in Claude Code?
Run `npx skills add minhnv0807/ai-business-skills --skill 66-crisis-playbook-global -a claude-code`. Or copy the skill folder (skills/en/66-crisis-playbook-global in minhnv0807/ai-business-skills) into .claude/skills/66-crisis-playbook-global in your project. Claude Code loads it when a task matches its description.
How do I install 66 Crisis Playbook Global in Codex?
Run `npx skills add minhnv0807/ai-business-skills --skill 66-crisis-playbook-global -a codex`. Or copy the skill folder (skills/en/66-crisis-playbook-global in minhnv0807/ai-business-skills) into .agents/skills/66-crisis-playbook-global in your project. Codex loads it when a task matches its description.
Can I use 66 Crisis Playbook Global in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add minhnv0807/ai-business-skills --skill 66-crisis-playbook-global -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/66-crisis-playbook-global, .gemini/skills/66-crisis-playbook-global, .github/skills/66-crisis-playbook-global and .opencode/skills/66-crisis-playbook-global in your project.
What does 66 Crisis Playbook Global need to run?
SKILL.md names no scripts, command-line tools or credentials: 66 Crisis Playbook Global is instructions for the agent only.
Does 66 Crisis Playbook Global access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is 66 Crisis Playbook Global safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does 66 Crisis Playbook Global use?
66 Crisis Playbook Global is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does 66 Crisis Playbook Global use?
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to 66 Crisis Playbook Global?
Skills that share tags, products or a category with 66 Crisis Playbook Global: After Action Report (rampstackco/claude-skills, 945 stars), Launch Retro Analyzer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Incident Retrospective (OpenHands/extensions, 163 stars) and Self Improver (Affitor/affiliate-skills, 701 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 66 Crisis Playbook Global?
minhnv0807 (a GitHub user) maintains it in minhnv0807/ai-business-skills, which has 609 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on September 12, 2026.
Source: minhnv0807/ai-business-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.