PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mohitagw15856/pm-claude-skills --skill retro-analysisgit clone --depth 1 https://github.com/mohitagw15856/pm-claude-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/retro-analysis)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/retro-analysis"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/retro-analysis/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/retro-analysis"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/retro-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00094 | $0.00882 |
| Opus 5.5 | $0.00038 | $0.00353 |
| Sonnet 5.5 | $0.00019 | $0.00176 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
retro-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill de Análisis de Retrospectiva
Genera un resumen de retrospectiva fundamentado en datos que separa hechos de percepciones, para que el equipo dedique el tiempo de retro a soluciones en lugar de debatir qué pasó.
Inputs Requeridos
Pide al usuario estos datos si no se proporcionan:
- Tickets del sprint: planificados vs. completados
- Tickets llevados al siguiente sprint y razones (si se conocen)
- Tickets reabiertos después de cerrar (señal de calidad)
- Cualquier incidente o trabajo no planificado (señal de scope creep)
- Velocidad del sprint vs. promedio histórico (contexto de tendencia)
Proceso
- Calcula: tasa de finalización, tasa de carry-over, porcentaje de trabajo no planificado
- Identifica patrones: ¿qué tipos de tickets tenían más probabilidad de ser llevados? ¿Cuáles causaron bloqueos?
- Anota cualquier ruptura de procesos o comunicación visible en los datos
- Prepara 3 preguntas "Iniciar / Detener / Continuar" basadas en los datos — no genéricas, específicas de este sprint
- Sugiere 1 experimento concreto para el próximo sprint basado en el mayor punto de fricción
- Valida — Confirma que cada pregunta es específica de este sprint (no una pregunta genérica reciclada), y que el experimento recomendado es concreto y medible
Estructura del Output
Resumen de Retrospectiva Sprint [Número]
Por los Números:
- Planificado: [n] tickets | Completado: [n] | Carry-over: [n] | Tasa de finalización: [%]
- Trabajo no planificado: [n] tickets ([%] de capacidad)
- Velocidad: [puntos] vs. [promedio] promedio
Lo que Sugieren los Datos: [2-3 observaciones fundamentadas en los números anteriores]
Preguntas para la Discusión:
- Iniciar: [pregunta específica basada en datos de este sprint]
- Detener: [pregunta específica basada en datos de este sprint]
- Continuar: [pregunta específica basada en datos de este sprint]
Experimento Sugerido para el Próximo Sprint: [Un cambio de proceso concreto y comprobable — con una métrica específica de éxito]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 63 lines · 94 tokens per session scan A 4f5a205cd2fc
retro-analysis is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 882 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-12.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…