Gitea Workflow
jwynia/agent-skills
Orchestrate agile development workflows for Gitea repositories using the tea CLI.
PM behavioral retrospective. An agent skill from gnurio/nurijanian-skills.
Install Situation Retrospective
$ npx skills add gnurio/nurijanian-skills --skill situation-retrospective -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gnurio/nurijanian-skills situation-retrospective --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/gnurio/nurijanian-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/situation-retrospective .claude/skills/situation-retrospective && 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 "situation-retrospective" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/situation-retrospective into .claude/skills/situation-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "situation-retrospective", 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/gnurio/nurijanian-skills/tree/main/skills/situation-retrospectiveType 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 gnurio/nurijanian-skills --skill situation-retrospective -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gnurio/nurijanian-skills situation-retrospective --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnurio/nurijanian-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/situation-retrospective .agents/skills/situation-retrospective && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "situation-retrospective" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/situation-retrospective into .agents/skills/situation-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "situation-retrospective", 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 gnurio/nurijanian-skills --skill situation-retrospective -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gnurio/nurijanian-skills situation-retrospective --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnurio/nurijanian-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/situation-retrospective .cursor/skills/situation-retrospective && 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 "situation-retrospective" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/situation-retrospective into .cursor/skills/situation-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "situation-retrospective", 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/gnurio/nurijanian-skills.git --path skills/situation-retrospective--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 gnurio/nurijanian-skills --skill situation-retrospective -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gnurio/nurijanian-skills situation-retrospective --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnurio/nurijanian-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/situation-retrospective .gemini/skills/situation-retrospective && 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 "situation-retrospective" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/situation-retrospective into .gemini/skills/situation-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "situation-retrospective", 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 gnurio/nurijanian-skills situation-retrospectiveInstalls 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 gnurio/nurijanian-skills --skill situation-retrospective -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gnurio/nurijanian-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/situation-retrospective .github/skills/situation-retrospective && 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 "situation-retrospective" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/situation-retrospective into .github/skills/situation-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "situation-retrospective", 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 gnurio/nurijanian-skills --skill situation-retrospective -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gnurio/nurijanian-skills situation-retrospective --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnurio/nurijanian-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/situation-retrospective .opencode/skills/situation-retrospective && 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 "situation-retrospective" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/situation-retrospective into .opencode/skills/situation-retrospective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "situation-retrospective", 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
situation-retrospective- GitHub stars
- 124
- Token cost
- ~1.4k tokens
- SKILL.md length
- 730 words
- Files
- 2 (incl. references)
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- MIT
At a glance
PM behavioral retrospective. An agent skill from gnurio/nurijanian-skills.
- Works in 3 steps: Get the Situation → Map the Behavior → Deliver the Feedback
- A PM wants to debrief a specific situation they recently handled — a meeting
- SKILL.md covers What This Mode Does, Process, Calibration Notes and Input/Output Contract
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Situation Retrospective is an agent skill from gnurio/nurijanian-skills. PM behavioral retrospective. Use this skill whenever a PM wants to debrief a specific situation they recently handled — a meeting, a conflict, a decision, a conversation with an engineer or designer, a feature that shipped badly, a standup that went sideways. The PM describes what happened and you map their actual behavior against the PM excellence framework to surface what they did well and where they fell short. Trigger on: "I just had a situation where...", "I want to think through how I handled..."…
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/pm-excellence-behaviors.md`).
It sits in Product & Project Management, covering Retrospectives and Meeting notes and agendas. The repository describes itself as: Claude Code and Cursor skills for product managers — PM coaching, verbalized sampling, tech sensemaking, and more. The licence is MIT.
When your agent uses it
- A PM wants to debrief a specific situation they recently handled — a meeting
- A conversation with an engineer
- A feature that shipped badly
- A standup that went sideways
Example prompts
- “I just had a situation where...”
- “I want to think through how I handled...”
- “something happened this week that I want to debrief”
- “/situation-retrospective”
Workflow steps
3 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 43a0566. 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
Situation Retrospective loads about 1.4k tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 185 tokens; SKILL.md has 730 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 gnurio/nurijanian-skills at commit 43a0566, republished under its MIT licence (© gnurio). 730 words, ~1,402 tokens.
Download SKILL.mdSave it as
.claude/skills/situation-retrospective/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- situation-retrospective
- description
- PM behavioral retrospective. Use this skill whenever a PM wants to debrief a specific situation they recently handled — a meeting, a conflict, a decision, a conversation with an engineer or designer, a feature that shipped badly, a standup that went sideways. The PM describes what happened and you map their actual behavior against the PM excellence framework to surface what they did well and where they fell short. Trigger on: "I just had a situation where...", "I want to think through how I handled...", "something happened this week that I want to debrief", "was this the right call?", "I'm not sure I handled this well", or any time a PM describes a specific recent event and wants feedback on their behavior.
Situation Retrospective
Read references/pm-excellence-behaviors.md before beginning. You will map the PM's described
behavior against the 7 clusters in that file.
What This Mode Does
The PM describes a real situation. You ask enough questions to understand what actually happened (not just their interpretation), then you map their behavior against the excellence framework, surface what they got right, name what they missed, and give them 2-3 specific things to do differently next time.
The output should feel like getting feedback from a rigorous, honest colleague who was in the room — not like a generic coaching session.
Process
Step 1: Get the Situation
Ask the PM to describe the situation. If they've already described it, work with what they've given. You need to understand:
- What was the context? (team meeting, 1:1, cross-functional review, incident, etc.)
- Who was involved? (engineers, designers, leadership, stakeholders, etc.)
- What did the PM actually say or do? (get specifics — avoid abstract summaries)
- What happened as a result?
- What did the PM want to happen? Did it?
If the description is vague ("I had a hard conversation with my lead engineer"), ask one targeted follow-up: "Walk me through what you actually said, and what they said back."
Don't ask more than two follow-up questions before beginning your analysis. You don't need the complete picture to start seeing patterns.
Step 2: Map the Behavior
Silently (don't narrate this to the PM) map what they described against the 7 clusters:
Cluster 1: Communication — Did they champion the "why"? Did they translate leadership pressure into calm direction? Were they consistent in tone? Did they communicate openly or withhold?
Cluster 2: Decision Quality — Was the decision data-grounded? Customer-centric? Was the reasoning transparent to the team? Were they ruthless in prioritization?
Cluster 3: Team Empowerment — Did they delegate to the right experts? Did they protect team autonomy? Did they shorten feedback loops or create talkathons?
Cluster 4: Presence & Execution — Did they show up? Did they do the unglamorous work? Were they organized and clear?
Cluster 5: Research & Domain Grounding — Were their instincts backed by data and domain knowledge? Did they consider edge cases?
Cluster 6: Listening & Openness — Did they listen and act on what they heard, or just appear to? Were they attached to a particular outcome?
Cluster 7: People & Care — Did they treat people as partners? Did they focus on the team and the user, or on their own position?
Show full SKILL.md (333 more words)Show less
Step 3: Deliver the Feedback
Structure your output as:
What you got right: Name 1-2 specific things they did well. Be concrete — "you kept the team focused on the user problem rather than the technical dispute" not "you communicated well."
What you missed: Name the 1-3 most significant gaps. For each one:
- State the gap clearly: "What you did was X. The framework suggests Y instead."
- Explain why it matters: connect it to team trust, decision quality, or downstream consequences
- Reference the specific cluster it falls under (optional — use only if it adds clarity)
The one thing to do differently next time: Synthesize the feedback into a single concrete behavioral change they can try the very next time they're in a similar situation. This should be specific enough that they could describe it to someone else and have that person recognize it when they see it.
Calibration Notes
Avoid the compliment sandwich. If there's a serious gap, name it directly. Starting with positives is fine; burying the real feedback under reassurance is not.
Stay in the behavioral layer. Don't say "you seem like you struggle with authority" — say "in this situation, you overrode the designer's direction without explaining the business constraint, which is exactly the pattern that erodes trust over time."
The PM's intent doesn't excuse the impact. They may have had good reasons for what they did. Acknowledge that. Then explain what the impact would have been anyway.
If the situation reveals a genuine strength, say so without hedging. Some PMs have real areas of excellence buried under general anxiety about their performance. Naming strengths clearly is as important as naming gaps.
Input/Output Contract
Accepts: A description of a specific PM situation (a meeting, decision, conversation, event)
Produces: Behavioral analysis mapped to the excellence framework — strengths named, gaps named with explanation and impact, one concrete behavior change
Passes to: blind-spot-scan if a recurring pattern emerges; adversarial-roleplay if a
specific relationship dynamic needs practice; or terminal if the PM has what they need
© gnurio, MIT. 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 (references) in skills/situation-retrospective of gnurio/nurijanian-skills.
- SKILL.md
- references/pm-excellence-behaviors.md
Open the folder on GitHubat commit 43a0566
Compare with similar skills
Situation Retrospective 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 |
|---|---|---|---|---|---|---|
| Situation Retrospective this skillgnurio/nurijanian-skills | 124 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Gitea Workflowjwynia/agent-skills | 170 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Scrum Masteralirezarezvani/claude-skills | 28k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Scrum Master Agentalirezarezvani/claude-code-skill-factory | 882 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Agile Workflowjwynia/agent-skills | 170 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Omh Operating Rhythmrlaope/oh-my-hermes | 3.2k | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Scrum Master
alirezarezvani/claude-skills
Advanced Scrum Master skill for data-driven agile team analysis and coaching.
Scrum Master Agent
alirezarezvani/claude-code-skill-factory
Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting
Agile Workflow
jwynia/agent-skills
Orchestrate agile development workflows by invoking commands in sequence with checkpoint-based flow control.
Omh Operating Rhythm
rlaope/oh-my-hermes
[omh] Team minutes, retros, and decision history to keep: meeting minutes, scrum/sprint records, retros, decisions, and follow-up history.
Agile Ceremonies
aiskillstore/marketplace
Agile ceremonies and sprint management specialist. An agent skill from aiskillstore/marketplace.
More from gnurio/nurijanian-skills
All 15 skills in this repoVibe Code Leaf Finder
gnurio/nurijanian-skills
This skill should be used when a user wants to identify which parts of a codebase are safe to modify with AI ("vibe code") and which require careful human engineering.
Corporate Misalignment Finder
gnurio/nurijanian-skills
Find, diagnose, and fix misalignment in corporate settings. An agent skill from gnurio/nurijanian-skills.
Verbalized Sampling
gnurio/nurijanian-skills
Generate diverse outputs by prompting for a probability distribution instead of a single response.
Focal Point Finder
gnurio/nurijanian-skills
This skill should be used when someone needs to find, propose, or evaluate a focal point in a coordination, negotiation, or alignment problem.
Orchestrate Pm Alignment
gnurio/nurijanian-skills
PM alignment coach and router. An agent skill from gnurio/nurijanian-skills.
Tech Sensemaking
gnurio/nurijanian-skills
Analyze technology announcements to surface non-obvious strategic implications using Verbalized Sampling.
Related
Categories
Questions about Situation Retrospective
What does Situation Retrospective do?
PM behavioral retrospective. An agent skill from gnurio/nurijanian-skills. Situation Retrospective is an agent skill from gnurio/nurijanian-skills. PM behavioral retrospective.
When should I use Situation Retrospective?
Situation Retrospective fits situations like: A PM wants to debrief a specific situation they recently handled — a meeting; A conversation with an engineer; A feature that shipped badly; A standup that went sideways.
How do I install Situation Retrospective in Claude Code?
Run `npx skills add gnurio/nurijanian-skills --skill situation-retrospective -a claude-code`. Or copy the skill folder (skills/situation-retrospective in gnurio/nurijanian-skills) into .claude/skills/situation-retrospective in your project. Claude Code loads it when a task matches its description.
How do I install Situation Retrospective in Codex?
Run `npx skills add gnurio/nurijanian-skills --skill situation-retrospective -a codex`. Or copy the skill folder (skills/situation-retrospective in gnurio/nurijanian-skills) into .agents/skills/situation-retrospective in your project. Codex loads it when a task matches its description.
Can I use Situation Retrospective 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 gnurio/nurijanian-skills --skill situation-retrospective -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/situation-retrospective, .gemini/skills/situation-retrospective, .github/skills/situation-retrospective and .opencode/skills/situation-retrospective in your project.
What does Situation Retrospective need to run?
SKILL.md names no scripts, command-line tools or credentials: Situation Retrospective is instructions for the agent only.
Does Situation Retrospective 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 Situation Retrospective 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 Situation Retrospective use?
Situation Retrospective is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Situation Retrospective use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.
What are the alternatives to Situation Retrospective?
Skills that share tags, products or a category with Situation Retrospective: Gitea Workflow (jwynia/agent-skills, 170 stars), Scrum Master (alirezarezvani/claude-skills, 28k stars), Scrum Master Agent (alirezarezvani/claude-code-skill-factory, 882 stars) and Agile Workflow (jwynia/agent-skills, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Situation Retrospective?
gnurio (a GitHub user) maintains it in gnurio/nurijanian-skills, which has 124 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on August 13, 2026.
Source: gnurio/nurijanian-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.