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 mshadmanrahman/pm-pilot --skill tech-to-pm-translatorgit clone --depth 1 https://github.com/mshadmanrahman/pm-pilotWrote 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/mshadmanrahman/pm-pilot/tech-to-pm-translator)<a href="https://agentmods.dev/skills/mshadmanrahman/pm-pilot/tech-to-pm-translator"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/pm-pilot/tech-to-pm-translator/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/mshadmanrahman/pm-pilot/tech-to-pm-translator"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/pm-pilot/tech-to-pm-translator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00125 | $0.02965 |
| Opus 5 | $0.00063 | $0.01483 |
| Sonnet 5 | $0.00025 | $0.00593 |
| Haiku 4.5 | $0.00013 | $0.00297 |
Grade A, and why
tech-to-pm-translator 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 11d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech-to-PM Translator
Converts technical developer documentation into structured, code-free knowledge base documents that PMs, designers, and other non-engineers can use to understand systems without reading code.
Philosophy
This is a translation skill, not a summarization skill.
- Summarization loses detail. A PM reading a summary still can't answer questions.
- Translation reframes the same information for a different audience. A PM reading a translated doc can understand what breaks, why, and who to talk to.
The output preserves technical accuracy while stripping implementation detail and adding decision-support framing.
When to Activate
- User says "translate docs for PMs", "make this PM-friendly", "convert tech docs"
- User says "create PM context from these docs", "non-engineer version"
- User says "explain this system for PMs/designers", "create onboarding docs"
- User has technical markdown files and wants them accessible to non-coders
- After a team writes architecture docs and wants broader org understanding
Input
Required:
- Source path: Directory or glob pattern containing technical docs (e.g.,
.claude/ref/,docs/architecture/,**/*.md)
Optional:
- Output path: Where to write the translated docs (default: alongside source or user-specified)
- Audience: "pm" (default), "designer", "stakeholder", "new-hire" (adjusts framing depth)
- Project name: For context-specific terminology and ownership mapping
- Existing context: Path to existing PM docs to avoid duplication and maintain consistency
Output Documents
The skill produces up to four document types depending on source material:
| Document | When Generated | Purpose |
|---|---|---|
| Platform Guide | Always | How the system works end-to-end: user flows, data pipelines, integrations |
| Bug Anatomy | When source docs cover components, failure modes, or debugging | Bug families, filing guide, priority framework, engineer communication tips |
| Migration/Change Landscape | When source docs describe transitions, deprecations, or active migrations | What's changing, dependency map, decision framework for fix depth |
| Architecture Overview | When source docs cover infrastructure, deployment, or system design | Updated tech architecture in PM-friendly terms |
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.
- 11d ago First seen · 298 lines · 125 tokens per session scan A 3d784222c1dd
tech-to-pm-translator is a skill published in the GitHub repository mshadmanrahman/pm-pilot (20 stars, last pushed 5d ago), licensed MIT. It adds 125 tokens to every session and 2,965 once invoked, about $0.0006 per session on Opus 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-08-30.
Other skills, from other repositories
analyze-codebase
Run comprehensive PLG analysis on a codebase to detect tech stack, existing growth features, and revenue opportunities. Use when the user says "analyze", "scan", "audit codebase", or "find growth opportunities".
build-implementation
Generate context-aware implementation prompts for a selected growth loop. Use when the user says "build", "implement", "generate code", "create prompt", or "how do I build this".
deploy-telemetry
Set up analytics and tracking infrastructure for growth loops. Use when the user says "deploy telemetry", "set up analytics", "tracking", "events", "push to supabase", or "skene push".
plan-growth-loop
Generate prioritized growth loops with implementation roadmaps based on codebase analysis. Use when the user says "plan", "growth loops", "prioritize", "what should I build", or "roadmap".
validate-loop
Check if growth loop requirements are actually implemented in the codebase. Use when the user says "validate", "check status", "skene status", "is it done", or "verify implementation".
initialize-config
Set up Skene configuration for a project. Use when starting a new PLG analysis, when .skene.config is missing, or when the user says "skene init", "set up skene", or "configure skene".