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 technical-spec-templategit 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/technical-spec-template)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/technical-spec-template"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/technical-spec-template/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/technical-spec-template"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/technical-spec-template.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.00090 | $0.01761 |
| Opus 5.5 | $0.00036 | $0.00704 |
| Sonnet 5.5 | $0.00018 | $0.00352 |
| Haiku 4.5 | $0.00009 | $0.00176 |
Grade A, and why
technical-spec-template 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill de Plantilla de Especificación Técnica
Escribe especificaciones técnicas que los ingenieros realmente lean — framing claro del problema, requisitos inequívocos, decisiones explícitas y compensaciones documentadas.
Entradas Requeridas
Pregunta al usuario por estos datos si no se proporcionan:
- Descripción de funcionalidad o sistema (qué necesita especificarse)
- PRD o brief de producto relacionado (si está disponible)
- Revisores de ingeniería (cuya aprobación es necesaria)
- Restricciones conocidas (limitaciones técnicas, requisitos de seguridad, objetivos de rendimiento)
Cuándo Escribir una Especificación Técnica
Escribe una especificación técnica cuando:
- La funcionalidad requiere cambios en 2+ sistemas
- Hay decisiones arquitectónicas significativas que tomar
- Más de un ingeniero trabajará en la implementación
- La funcionalidad tiene implicaciones de seguridad, privacidad o cumplimiento
- El esfuerzo estimado es >5 story points
Sáltate la especificación para correcciones de bugs triviales o cambios de 1-2 horas.
Formato de Salida de Especificación Técnica
Especificación Técnica — [Nombre de Funcionalidad]
Autor: [Nombre] Estado: Borrador | En Revisión | Aprobado | Implementado Creado: [Fecha] | Última Actualización: [Fecha] Revisores: [Líder de Ing., Arquitecto, PM, Seguridad si es necesario] PRD Relacionado: [Enlace] | Epic de Jira: [Enlace]
1. Declaración del Problema
[2–3 oraciones. ¿Qué problema estamos resolviendo y por qué ahora? Sin lenguaje de solución aquí.]
2. Objetivos y No-Objetivos
Objetivos (en alcance):
- [Resultado específico y medible]
- [Resultado específico y medible]
No-Objetivos (explícitamente fuera de alcance):
- [Qué esta especificación NO cubre]
- [Suposición común a descartar tempranamente]
3. Antecedentes y Contexto
[Cualquier trabajo previo, sistemas relacionados, o contexto que los ingenieros necesitan para entender el espacio de decisión. Enlaza a especificaciones previas, ADRs, o investigación.]
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 · 159 lines · 90 tokens per session scan A c4bfd6f23eac
technical-spec-template is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 1,761 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…