Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
A skill your agent uses when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process…
Install 63 Campaign Retrospective Global
$ npx skills add minhnv0807/ai-business-skills --skill 63-campaign-retrospective-global -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install minhnv0807/ai-business-skills 63-campaign-retrospective-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/63-campaign-retrospective-global .claude/skills/63-campaign-retrospective-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 "63-campaign-retrospective-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/63-campaign-retrospective-global into .claude/skills/63-campaign-retrospective-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "63-campaign-retrospective-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/63-campaign-retrospective-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 63-campaign-retrospective-global -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install minhnv0807/ai-business-skills 63-campaign-retrospective-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/63-campaign-retrospective-global .agents/skills/63-campaign-retrospective-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 "63-campaign-retrospective-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/63-campaign-retrospective-global into .agents/skills/63-campaign-retrospective-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "63-campaign-retrospective-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 63-campaign-retrospective-global -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install minhnv0807/ai-business-skills 63-campaign-retrospective-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/63-campaign-retrospective-global .cursor/skills/63-campaign-retrospective-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 "63-campaign-retrospective-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/63-campaign-retrospective-global into .cursor/skills/63-campaign-retrospective-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "63-campaign-retrospective-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/63-campaign-retrospective-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 63-campaign-retrospective-global -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install minhnv0807/ai-business-skills 63-campaign-retrospective-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/63-campaign-retrospective-global .gemini/skills/63-campaign-retrospective-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 "63-campaign-retrospective-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/63-campaign-retrospective-global into .gemini/skills/63-campaign-retrospective-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "63-campaign-retrospective-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 63-campaign-retrospective-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 63-campaign-retrospective-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/63-campaign-retrospective-global .github/skills/63-campaign-retrospective-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 "63-campaign-retrospective-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/63-campaign-retrospective-global into .github/skills/63-campaign-retrospective-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "63-campaign-retrospective-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 63-campaign-retrospective-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 63-campaign-retrospective-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/63-campaign-retrospective-global .opencode/skills/63-campaign-retrospective-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 "63-campaign-retrospective-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/63-campaign-retrospective-global into .opencode/skills/63-campaign-retrospective-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "63-campaign-retrospective-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
63-campaign-retrospective-global- GitHub stars
- 609
- Token cost
- ~2.1k tokens
- SKILL.md length
- 966 words
- Files
- 1
- Skills in repo
- 142
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process…
- Works in 9 steps: Prepare (before the session) → Campaign scorecard → What worked (repeat next time) → …
- A campaign has ENDED and the team needs a structured retrospective — a scorecard against target
- SKILL.md covers Information gathering, Principles, Workflow and Facilitation guide, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
63 Campaign Retrospective Global is an agent skill from minhnv0807/ai-business-skills. Use when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process review, lessons written back into the playbook and Brand Hub, and action items with owners. Trigger on 'campaign retrospective', 'campaign retro', 'post-mortem', 'campaign debrief', 'what worked and what did not', 'the campaign is over, what did we learn'. Also use when a campaign underdelivered and the team is arguing about why. Not for — a…
Its SKILL.md is about 2.1k 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 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 campaign has ENDED and the team needs a structured retrospective — a scorecard against target
- Why with evidence
- Lessons written back into the playbook and Brand Hub
- Action items with owners
Example prompts
- “campaign retrospective”
- “campaign retro”
- “post-mortem”
- “/63-campaign-retrospective-global”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
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.
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
63 Campaign Retrospective Global loads about 2.1k tokens when it runs. Until then it costs about 185 tokens; SKILL.md has 966 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). 966 words, ~2,133 tokens.
Download SKILL.mdSave it as
.claude/skills/63-campaign-retrospective-global/SKILL.md (or your agent's skills folder).- name
- 63-campaign-retrospective-global
- description
- Use when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process review, lessons written back into the playbook and Brand Hub, and action items with owners. Trigger on 'campaign retrospective', 'campaign retro', 'post-mortem', 'campaign debrief', 'what worked and what did not', 'the campaign is over, what did we learn'. Also use when a campaign underdelivered and the team is arguing about why. Not for — a periodic performance report, see `07-marketing-report-global`; diagnosing live numbers mid-flight, see `03-performance-eval-global`; the next period ads plan, see `57-next-ads-plan-global`.
- metadata.version
- 1.0.1
- metadata.category
- operations
- license
- MIT
- triggers
- campaign retrospective, campaign retro, post-mortem, campaign debrief, what worked what did not, lessons from the campaign, campaign wrap-up
- output
- File .md — full retrospective: scorecard, what worked / did not / surprises, process review, playbook and Brand Hub updates, input for the next campaign…
- related
- 07-marketing-report-global, 60-launch-playbook-global, 02-campaign-brief-global, 34-ai-marketing-os-global, 65-team-performance-review-global
Campaign Retrospective (Global)
A retrospective is not for assigning blame — it is how the team and the system get better after every campaign. The best insight comes from failure, but only if it is safe to speak honestly. A retro with no action is wasted time: every lesson must become one concrete change in the playbook, the Brand Hub, or the process.
Information gathering
Ask up to 4 questions:
- Which campaign, and over what dates? Name, start and end dates, original objective.
- Final data: revenue, leads, CPA, ROAS, spend — final numbers versus target. (If a report already exists from
07-marketing-report-global, use it as the input.) - Who attends the retro? Content, performance, design, sales, leader?
- How long ago did the campaign end? Run the retro within 5 days of the end, while memory is fresh.
Principles
- Mandatory after every major campaign. No skipping because the team is busy. No retro means paying tuition without learning the lesson.
- Record only claims backed by data. "Creative A felt strong" is not an insight; "creative A hit $18 CPA against a $28 account average" is.
- No individual blame. Talk about systems and process. Everyone has the floor.
- Every lesson becomes one concrete change — to the playbook, a template, the Brand Hub, or a process — with an owner and a deadline.
- Document so it still makes sense in 6 months — and link the retro into the next campaign's brief.
Workflow
1. Prepare (before the session)
- Pull final data: revenue, leads, CPA, ROAS, spend, timeline adherence, budget variance.
- Send the data to the team before the meeting — the meeting is for discussion, not for reading numbers.
- Book 60 minutes with a named facilitator (usually the leader). For distributed teams, pick a time that works across the relevant timezones and require written pre-reads from anyone who cannot attend live.
2. Campaign scorecard
| KPI | Target | Actual | % achieved | vs previous campaign |
|---|---|---|---|---|
| Revenue | ||||
| Leads | ||||
| CPA | ||||
| ROAS | ||||
| Spend | ||||
| Timeline (on schedule?) | ||||
| Budget (within plan?) |
Overall verdict: Success (>90% of KPIs) / Mixed (60-90%) / Miss (<60%).
When comparing against category benchmarks, use the right region and industry row in references/benchmarks-global.md — and adjust for seasonality before declaring a CPA increase a failure, since Q4 media costs run materially above Q1.
3. What worked (repeat next time)
| # | What worked | Evidence (numbers) | Why it worked | How to apply next time |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 |
Name the winning patterns explicitly:
- Content angle: which angle converted best
- Creative format: video / image / carousel — which performed
- Audience: which segment responded
- Timing: which day or hour performed best
- Channel: best CPA and ROAS
4. What did not work (avoid next time)
| # | What failed | Evidence | Root cause | Decision: stop / fix / retest |
|---|---|---|---|---|
| 1 | ||||
| 2 |
Root cause must go past the symptom. "The ads were bad" is not a root cause; "audience overlapped with the previous campaign > frequency rose above 4 > CTR fell below 1%" is.
5. Surprises
- Positive surprises: what beat expectations, by how much, why — what do you take from it?
- Negative surprises: what came in worse, by how much, why — how do you prevent it?
6. Process and execution review
| Item | Assessment | Problems hit | Improvement |
|---|---|---|---|
| Brief quality | |||
| Timeline adherence | |||
| Team communication | |||
| Review and approval process | |||
| Launch-day execution | |||
| Data and tracking setup |
Biggest process bottleneck: the single thing most worth fixing next time.
7. Team callouts
Record specific contributions: [Name] — [the specific contribution and its positive impact on the result]. Recognize publicly, correct privately.
Show full SKILL.md (396 more words)Show less
8. Playbook and Brand Hub updates plus action items
| Document to update | What changes | Owner | Deadline |
|---|---|---|---|
Launch playbook (60-launch-playbook-global) | Add or amend step: [X] | Leader | |
| Campaign brief template | Adjust section: [Y] | Leader | |
| Brand Hub — customer insight | Add new insight from this campaign: [Z] | ||
| Brand Hub — KPI framework / internal benchmarks | Update the benchmarks you actually achieved (CPA, CVR) | ||
| Winning creative library | Store the winners plus the reason they won |
Every action item needs an owner and a deadline — never "the whole team will handle it."
9. Input for the next campaign
- 3 things to definitely repeat: 1... 2... 3...
- 3 things to definitely do differently: 1... 2... 3...
- Hypothesis to test next campaign: [hypothesis + how it will be measured]
Facilitation guide
- Timing: within 5 days of campaign end.
- Format: 60 minutes, full team, facilitator (leader): 10 min scorecard > 15 min what worked > 15 min what did not > 10 min process > 10 min action items and owners.
- Ground rules: no individual blame, systems and process only; everyone speaks; constructive, not a venting session.
- After: the leader publishes the document within 24 hours, shares it with the team and leadership, and links it into the next campaign brief.
Output structure
File name: campaign-retro-[campaign-name]-[YYYYMMDD].md — the 9 sections above: scorecard > what worked > what did not > surprises > process review > team callouts > playbook and Brand Hub updates > input for the next campaign > action items with owners.
Related skills
07-marketing-report-global: the final report supplies the scorecard data.60-launch-playbook-global: execution lessons are written directly back into the playbook.02-campaign-brief-global: the "lessons from the previous campaign" section of a new brief comes from this retro.34-ai-marketing-os-global: new insights and real benchmarks are written into the Brand Hub.65-team-performance-review-global: team callouts and observations feed individual reviews at period end — keep the two documents separate.
Quality checklist
- Retro run within 5 days of campaign end
- Scorecard covers all KPIs against target with a Success/Mixed/Miss verdict
- Every "what worked" and "what did not" entry has numeric evidence — no impressions
- Failures trace to a real root cause, not a symptom
- Benchmark comparisons adjusted for region, industry, and season
- At least one playbook update and one Brand Hub update
- Every action item has an owner and a deadline
- 3 things to repeat, 3 things to change, and a hypothesis for next time
- No individual blame anywhere in the document
- Document shared within 24 hours and linked into the next campaign brief
© 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/63-campaign-retrospective-global of minhnv0807/ai-business-skills.
Open the folder on GitHubat commit 0360adc
Compare with similar skills
63 Campaign Retrospective 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 |
|---|---|---|---|---|---|---|
| 63 Campaign Retrospective Global this skillminhnv0807/ai-business-skills | 609 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Weekly Engineering Retrogarrytan/gstack | 136k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Dough Execute Planterryyin/lizard | 2.5k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Oral Paper SkillAdkid-Zephyr/oral-paper-skill | 357 | — | ~1.9k | Automated safety check: Pass | None | |
| Deck Retroasheshgoplani/agent-deck | 1.1k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Dough Execution Retrospectiveterryyin/lizard | 2.5k | — | ~4k | Automated safety check: Pass | Custom licence |
Similar skills
Dough Execute Plan
terryyin/lizard
Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…
Oral Paper Skill
Adkid-Zephyr/oral-paper-skill
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.
Deck Retro
asheshgoplani/agent-deck
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs.
Dough Execution Retrospective
terryyin/lizard
Reviews planned, completed planless quick, or quick-to-planned execution against original intent, aggregate commits, current whole-product architecture, and tests, including after cleanup.
Criticism Self Criticism
HughYau/qiushi-skill
批评与自我批评：在工作完成、阶段验收、收到批评或同类错误反复出现时，对成果和过程做诚实、具体、基于事实的审视，输出可执行的改进项，并处理外来批评而不辩解。触发信号包括 review、复盘、审查、"帮我看看有没有问题"、"你确定吗"；任务刚开始或只是单步查询时不触发。
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
Categories
Questions about 63 Campaign Retrospective Global
What does 63 Campaign Retrospective Global do?
A skill your agent uses when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process…. 63 Campaign Retrospective Global is an agent skill from minhnv0807/ai-business-skills. Use when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process review, lessons written back into the playbook and Brand Hub, and action items with owners.
When should I use 63 Campaign Retrospective Global?
63 Campaign Retrospective Global fits situations like: A campaign has ENDED and the team needs a structured retrospective — a scorecard against target; why with evidence; lessons written back into the playbook and Brand Hub; action items with owners.
How do I install 63 Campaign Retrospective Global in Claude Code?
Run `npx skills add minhnv0807/ai-business-skills --skill 63-campaign-retrospective-global -a claude-code`. Or copy the skill folder (skills/en/63-campaign-retrospective-global in minhnv0807/ai-business-skills) into .claude/skills/63-campaign-retrospective-global in your project. Claude Code loads it when a task matches its description.
How do I install 63 Campaign Retrospective Global in Codex?
Run `npx skills add minhnv0807/ai-business-skills --skill 63-campaign-retrospective-global -a codex`. Or copy the skill folder (skills/en/63-campaign-retrospective-global in minhnv0807/ai-business-skills) into .agents/skills/63-campaign-retrospective-global in your project. Codex loads it when a task matches its description.
Can I use 63 Campaign Retrospective 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 63-campaign-retrospective-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/63-campaign-retrospective-global, .gemini/skills/63-campaign-retrospective-global, .github/skills/63-campaign-retrospective-global and .opencode/skills/63-campaign-retrospective-global in your project.
What does 63 Campaign Retrospective Global need to run?
SKILL.md names no scripts, command-line tools or credentials: 63 Campaign Retrospective Global is instructions for the agent only.
Does 63 Campaign Retrospective 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 63 Campaign Retrospective 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 63 Campaign Retrospective Global use?
63 Campaign Retrospective 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 63 Campaign Retrospective Global use?
About 2.1k tokens (SKILL.md is roughly 8.5k 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 63 Campaign Retrospective Global?
Skills that share tags, products or a category with 63 Campaign Retrospective Global: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.5k stars), Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 357 stars) and Deck Retro (asheshgoplani/agent-deck, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 63 Campaign Retrospective 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.