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.
Conduct a retrospective on a coding session. An agent skill from brim-borium/spotify_sdk.
Install Retro
$ npx skills add brim-borium/spotify_sdk --skill retro -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brim-borium/spotify_sdk retro --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/brim-borium/spotify_sdk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/retro .claude/skills/retro && 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 "retro" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/retro into .claude/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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/brim-borium/spotify_sdk/tree/main/.agents/skills/retroType 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 brim-borium/spotify_sdk --skill retro -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brim-borium/spotify_sdk retro --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brim-borium/spotify_sdk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/retro .agents/skills/retro && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "retro" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/retro into .agents/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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 brim-borium/spotify_sdk --skill retro -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brim-borium/spotify_sdk retro --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brim-borium/spotify_sdk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/retro .cursor/skills/retro && 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 "retro" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/retro into .cursor/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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/brim-borium/spotify_sdk.git --path .agents/skills/retro--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 brim-borium/spotify_sdk --skill retro -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brim-borium/spotify_sdk retro --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brim-borium/spotify_sdk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/retro .gemini/skills/retro && 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 "retro" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/retro into .gemini/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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 brim-borium/spotify_sdk retroInstalls 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 brim-borium/spotify_sdk --skill retro -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brim-borium/spotify_sdk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/retro .github/skills/retro && 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 "retro" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/retro into .github/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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 brim-borium/spotify_sdk --skill retro -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brim-borium/spotify_sdk retro --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brim-borium/spotify_sdk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/retro .opencode/skills/retro && 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 "retro" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/retro into .opencode/skills/retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "retro", 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
retro- GitHub stars
- 166
- Used in
- 7 other repos
- Token cost
- ~1.1k tokens
- SKILL.md length
- 648 words
- Files
- 2
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Conduct a retrospective on a coding session. An agent skill from brim-borium/spotify_sdk.
- Works in 3 steps: Call the Skill tool with… → Read the primary sources for the session… → Look for candidates for improvement in…
- Tasks that involve Retrospectives
- SKILL.md covers Steps and Reference
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Retro is an agent skill from brim-borium/spotify_sdk. Conduct a retrospective on a coding session.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Product & Project Management, covering Retrospectives. The repository describes itself as: Flutter Package to connect the spotify sdk. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Retrospectives
Example prompts
- “/retro”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Call the Skill tool with writing-for-agents for the writing style guide.
- Read the primary sources for the session the user specifies. This may mean searching through session logs on this machine. If the user…
- Look for candidates for improvement in these categories.
What it can do on your machine
Read from SKILL.md and the folder at commit 2622fc0. 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
Retro loads about 1.1k tokens when it runs. Until then it costs about 13 tokens; SKILL.md has 648 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 brim-borium/spotify_sdk at commit 2622fc0, republished under its Apache-2.0 licence (© brim-borium). 648 words, ~1,093 tokens.
Download SKILL.mdSave it as
.claude/skills/retro/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- retro
- description
- Conduct a retrospective on a coding session.
- disable-model-invocation
- true
The user has asked for a retrospective. You are suggesting improvements to the coding agent's environment to improve future runs.
Steps
Call the Skill tool with
writing-for-agentsfor the writing style guide.Read the primary sources for the session the user specifies. This may mean searching through session logs on this machine. If the user doesn't specify a session, default to the current one.
Look for candidates for improvement in these categories.
- Navigation: how easy was it for the agent to find the right files? Are there hidden dependencies between files? Would a navigation pointer make it easier? Use when the session took a long time to find a piece of information.
- Automated checks: are there automated checks that could catch errors the agent made? Linting, typing, tests, filesystem linters? Read the repo's own check command first (its
package.json/build-toollint/checkscripts, its CI workflow), so a check that already exists but sits unwired or silently broken is the finding, not a reinvention. A repo with no guardrail (no pre-commit hook and no CI job running its lint/typecheck/test command) is itself a finding: an un-linted repo is a standing missed opportunity, not a neutral default. Use when the agent made a mistake an automated check could have caught, or the repo has no guardrail at all. - Coding standards: should the reviewer agent be given a new rule to enforce? Should an existing rule be removed or clarified? Classify the violation first: a mechanical one (a fixed syntactic pattern, a banned API, an import shape, a file-location rule) gets a deterministic check, full stop: a custom rule in the repo's own linter, a new pre-commit hook, or a new CI job, whichever the repo's language and existing guardrail make cheapest. Default to building the check over writing the rule. Reserve
CODING_STANDARDS.mdfor genuine judgement calls (cross-file consistency, "matches the surrounding style," anything no guardrail could ever substitute for). Use when the reviewer agent failed to catch a mistake. - Global AGENTS.md: are there any steering instructions that should be moved to coding standards (or automated checks) instead? Use when the AGENTS.md file is particularly large - in the repo OR the user's global scope.
- Tool economy: did the agent make expensive tool calls that could be streamlined? Is there any custom tooling (CLI's, MCP's) that is particularly token-inefficient? Use when the agent made an expensive tool call.
- No-ops: look for instructions in steering files that don't modify the agent's behavior. Use when the steering files are large and unwieldy.
- Information access: look for opportunities to increase the agent's access to information. Teeing dev server logs, readonly access to third-party services. Use when a crucial piece of information was not available to the agent.
- Present these candidates to the user, in order of severity.
Show full SKILL.md (185 more words)Show less
Reference
Implementation vs Review
Remember that all work goes through two stages: implementation and review. The implementation agent has the most context pressure. They are responsible for exploration, writing code, and debugging failures.
The review agent has the least context pressure - it receives a diff, so no exploration needed. It often does not need to write code or debug.
This means that the review agent should be responsible for imposing coding standards, not the implementation agent.
Files
You have access to several files in the repo:
CLAUDE.md/AGENTS.md: these files are pushed to the context window of any agent working in this repo. They should be used incredibly sparingly, usually only for navigation pointers to other files.CODING_STANDARDS.md: this file is read during review, not implementation. Add navigation pointers to docs folders if the standards file gets more than 1,000 lines long.- Docs: use docs as references files, pointed to by other files. Look for existing docs before writing new ones.
- Skills: use skills for docs (since their description goes into the agent's context window), or for user-invoked commands. Follow the advice in the
writing-for-agentsskill.
© brim-borium, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/retro of brim-borium/spotify_sdk.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 2622fc0
Used in 7 other repositories
We found 8 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 7 other GitHub owners. This page covers the copy in brim-borium/spotify_sdk, which our catalogue first saw on October 7, 2026.
- growupanand/ConvoForm.agents/skills/retro
- willdady/platypus.agents/skills/retro
- ArcReel/ArcReel.agents/skills/retro
- Xircth/VibeX.agents/skills/retro.claude/skills/retro
- dzhng/skillsskills/engineering/retro
- tt-a1i/matt-skills-with-to-goalskills/in-progress/retro
- FeatherHunter/dsh-mattpocock-skills-deckpackage/bundled-skills/retro
Compare with similar skills
Retro 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 |
|---|---|---|---|---|---|---|
| Retro this skillbrim-borium/spotify_sdk | 166 | 7 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Weekly Engineering Retrogarrytan/gstack | 136k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Dough Execute Planterryyin/lizard | 2.6k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Oral Paper SkillAdkid-Zephyr/oral-paper-skill | 350 | — | ~1.9k | Automated safety check: Pass | None | |
| Deck Retroasheshgoplani/agent-deck | 1k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Dough Execution Retrospectiveterryyin/lizard | 2.6k | — | ~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 brim-borium/spotify_sdk
All 9 skills in this repoDomain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Implement Spec
brim-borium/spotify_sdk
Implement the result of /to-spec and /to-tickets in code. An agent skill from brim-borium/spotify_sdk.
Android Setup
brim-borium/spotify_sdk
Configure or clean Spotify App Remote SDK AAR resolution on Android.
Build Runner
brim-borium/spotify_sdk
Generate Dart JSON models and .g.dart files using buildrunner.
PR
brim-borium/spotify_sdk
Use when writing a PR body.
Platform Sync
brim-borium/spotify_sdk
Synchronize method channels and event streams across Dart, Android (Kotlin), iOS (Swift), and Web.
Related
Categories
Questions about Retro
What does Retro do?
Conduct a retrospective on a coding session. An agent skill from brim-borium/spotify_sdk. Retro is an agent skill from brim-borium/spotify_sdk. Conduct a retrospective on a coding session.
When should I use Retro?
Retro fits situations like: tasks that involve Retrospectives.
How do I install Retro in Claude Code?
Run `npx skills add brim-borium/spotify_sdk --skill retro -a claude-code`. Or copy the skill folder (.agents/skills/retro in brim-borium/spotify_sdk) into .claude/skills/retro in your project. Claude Code loads it when a task matches its description.
How do I install Retro in Codex?
Run `npx skills add brim-borium/spotify_sdk --skill retro -a codex`. Or copy the skill folder (.agents/skills/retro in brim-borium/spotify_sdk) into .agents/skills/retro in your project. Codex loads it when a task matches its description.
Can I use Retro 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 brim-borium/spotify_sdk --skill retro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/retro, .gemini/skills/retro, .github/skills/retro and .opencode/skills/retro in your project.
What does Retro need to run?
SKILL.md names no scripts, command-line tools or credentials: Retro is instructions for the agent only.
Does Retro 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 Retro 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 Retro use?
Retro is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Retro use?
About 1.1k tokens (SKILL.md is roughly 4.4k 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 Retro?
Skills that share tags, products or a category with Retro: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.6k stars), Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 350 stars) and Deck Retro (asheshgoplani/agent-deck, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Retro?
brim-borium (a GitHub user) maintains it in brim-borium/spotify_sdk, which has 166 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.
Source: brim-borium/spotify_sdk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.