Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
Assess whether an idea, feature request, or opportunity is worth pursuing before anyone writes a PRD.
Install Opportunity Assessment
$ npx skills add andreaskelm/pm-brain --skill opportunity-assessment -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install andreaskelm/pm-brain opportunity-assessment --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/andreaskelm/pm-brain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/opportunity-assessment .claude/skills/opportunity-assessment && 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 "opportunity-assessment" agent skill from https://github.com/andreaskelm/pm-brain/tree/main/.claude/skills/opportunity-assessment into .claude/skills/opportunity-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opportunity-assessment", 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/andreaskelm/pm-brain/tree/main/.claude/skills/opportunity-assessmentType 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 andreaskelm/pm-brain --skill opportunity-assessment -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install andreaskelm/pm-brain opportunity-assessment --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andreaskelm/pm-brain.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/opportunity-assessment .agents/skills/opportunity-assessment && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "opportunity-assessment" agent skill from https://github.com/andreaskelm/pm-brain/tree/main/.claude/skills/opportunity-assessment into .agents/skills/opportunity-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opportunity-assessment", 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 andreaskelm/pm-brain --skill opportunity-assessment -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install andreaskelm/pm-brain opportunity-assessment --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andreaskelm/pm-brain.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/opportunity-assessment .cursor/skills/opportunity-assessment && 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 "opportunity-assessment" agent skill from https://github.com/andreaskelm/pm-brain/tree/main/.claude/skills/opportunity-assessment into .cursor/skills/opportunity-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opportunity-assessment", 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/andreaskelm/pm-brain.git --path .claude/skills/opportunity-assessment--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 andreaskelm/pm-brain --skill opportunity-assessment -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install andreaskelm/pm-brain opportunity-assessment --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andreaskelm/pm-brain.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/opportunity-assessment .gemini/skills/opportunity-assessment && 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 "opportunity-assessment" agent skill from https://github.com/andreaskelm/pm-brain/tree/main/.claude/skills/opportunity-assessment into .gemini/skills/opportunity-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opportunity-assessment", 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 andreaskelm/pm-brain opportunity-assessmentInstalls 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 andreaskelm/pm-brain --skill opportunity-assessment -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/andreaskelm/pm-brain.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/opportunity-assessment .github/skills/opportunity-assessment && 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 "opportunity-assessment" agent skill from https://github.com/andreaskelm/pm-brain/tree/main/.claude/skills/opportunity-assessment into .github/skills/opportunity-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opportunity-assessment", 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 andreaskelm/pm-brain --skill opportunity-assessment -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install andreaskelm/pm-brain opportunity-assessment --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/andreaskelm/pm-brain.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/opportunity-assessment .opencode/skills/opportunity-assessment && 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 "opportunity-assessment" agent skill from https://github.com/andreaskelm/pm-brain/tree/main/.claude/skills/opportunity-assessment into .opencode/skills/opportunity-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "opportunity-assessment", 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
opportunity-assessment- GitHub stars
- 234
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,498 words
- Files
- 3 (incl. references)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Assess whether an idea, feature request, or opportunity is worth pursuing before anyone writes a PRD.
- Works in 7 steps: Preflight (before any template) → Write the problem hypothesis, not the… → Who, how many, how painful (with the… → …
- The user asks is this worth pursuing
- SKILL.md covers Is this the right thing?, Step 1 — Preflight (before any…, Step 2 — Write the problem… and Step 3 — Who, how many, how…, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Opportunity Assessment is an agent skill from andreaskelm/pm-brain. Assess whether an idea, feature request, or opportunity is worth pursuing before anyone writes a PRD. Covers the problem hypothesis, who has the problem and how badly, the four risks (value, usability, feasibility, viability), the riskiest assumption and its cheapest test, kill criteria, and a go / no-go / learn-more call. Use when the user asks "is this worth pursuing", "should we build this", "assess this opportunity", "opportunity assessment", "business case for an idea", "evaluate this idea before a PRD", "is…
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/criteria.md` and `references/template.md`).
It sits in Product & Project Management, covering PRD writing, Feature launches and release readiness and UX design. The repository describes itself as: AI-powered product management thinking & operating system. Playbooks, guides, templates, and frameworks that bridge PM theory to daily execution.
When your agent uses it
- The user asks is this worth pursuing
- Should we build this
- Assess this opportunity
- Opportunity assessment
Example prompts
- “is this worth pursuing”
- “should we build this”
- “assess this opportunity”
- “/opportunity-assessment”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
- Preflight (before any template)
- Write the problem hypothesis, not the solution
- Who, how many, how painful (with the evidence tier)
- Run the four risks
- Find the riskiest assumption and the cheapest test
- Write kill criteria before the evidence comes in
- Make the call: go, no-go, or learn more
What it can do on your machine
Read from SKILL.md and the folder at commit 38696ac. 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
Opportunity Assessment loads about 2.5k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 165 tokens; SKILL.md has 1,498 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,498 words (~2,520 tokens).
“An opportunity assessment is the step before the PRD. It answers four questions: is the problem real, is it worth solving, is it worth solving for us, and is now the time? The failure I see most often isn't a…”
- name
- opportunity-assessment
Files
SKILL.md and 2 other files (references) in .claude/skills/opportunity-assessment of andreaskelm/pm-brain.
- SKILL.md
- references/criteria.md
- references/template.md
Open the folder on GitHubat commit 38696ac
Compare with similar skills
Opportunity Assessment 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 |
|---|---|---|---|---|---|---|
| Opportunity Assessment this skillandreaskelm/pm-brain | 234 | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Schematicblader/schematic | 241 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Vscuse Scenario AuthoringOfficeDev/microsoft-365-agents-toolkit | 780 | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| App Spec Packagerinstructa/agent-skills | 139 | — | ~1.5k | Automated safety check: Pass | None | |
| Reviewgolbin/agent-skills | 214 | — | ~706 | Automated safety check: Pass | None | |
| Write Product Specbholmesdev/hubble.md | 1.5k | — | ~966 | Automated safety check: Pass | MIT |
Similar skills
Vscuse Scenario Authoring
OfficeDev/microsoft-365-agents-toolkit
A skill your agent uses when: reading a docs scenario, PRD, mockup, or user flow and using vscuse-ui/noVNC as the primary authoring surface to record, generate, replace, or update vscuse test plans…
App Spec Packager
instructa/agent-skills
A skill your agent uses when the user wants to turn an application, product, startup idea, SaaS, mobile app, web app, API, AI product, or internal tool into a production-ready Markdown specification…
Review
golbin/agent-skills
Review software designs and implementations for user experience, simplicity, and maintainability; apply fixes when requested.
Write Product Spec
bholmesdev/hubble.md
Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.
Prd UX Design
OfficeDev/microsoft-365-agents-toolkit
A skill your agent uses when adding or changing product requirements, scenarios, user flows, surface behavior, or design artifacts before specs or implementation.
More from andreaskelm/pm-brain
All 18 skills in this repoAI Product Management
andreaskelm/pm-brain
Ship and spec AI features, LLM products, agents, copilots, and generative UX — including when to use a model vs.
Discovery Synthesis
andreaskelm/pm-brain
Plan customer discovery, turn interview snapshots into synthesis and evidence-based opportunities, build or update an Opportunity Solution Tree, map jobs and segments, and design RAT tests for the…
Eng Design Collab
andreaskelm/pm-brain
Partner effectively with engineering and design — feasibility and scope negotiation, tech debt tradeoffs, design reviews, discovery with builders, and PRD handoffs that don't get thrown away.
Experimentation
andreaskelm/pm-brain
Design and run product experiments at a practical PM level — A/B tests, hypothesis tests, rollouts, feature flags, and reading results without pretending to be a statistician.
Launch Gtm
andreaskelm/pm-brain
Plan, tighten, or review a product launch and go-to-market motion: rollout phases, beta and GA readiness, sales enablement, marketing launch, and release comms (internal and external).
North Star
andreaskelm/pm-brain
Define, sharpen, or audit a North Star metric and its input metrics tree, and decide which product metrics actually matter (leading vs.
Related
Categories
Questions about Opportunity Assessment
What does Opportunity Assessment do?
Assess whether an idea, feature request, or opportunity is worth pursuing before anyone writes a PRD. Opportunity Assessment is an agent skill from andreaskelm/pm-brain. Assess whether an idea, feature request, or opportunity is worth pursuing before anyone writes a PRD.
When should I use Opportunity Assessment?
Opportunity Assessment fits situations like: the user asks is this worth pursuing; should we build this; assess this opportunity; opportunity assessment.
How do I install Opportunity Assessment in Claude Code?
Run `npx skills add andreaskelm/pm-brain --skill opportunity-assessment -a claude-code`. Or copy the skill folder (.claude/skills/opportunity-assessment in andreaskelm/pm-brain) into .claude/skills/opportunity-assessment in your project. Claude Code loads it when a task matches its description.
How do I install Opportunity Assessment in Codex?
Run `npx skills add andreaskelm/pm-brain --skill opportunity-assessment -a codex`. Or copy the skill folder (.claude/skills/opportunity-assessment in andreaskelm/pm-brain) into .agents/skills/opportunity-assessment in your project. Codex loads it when a task matches its description.
Can I use Opportunity Assessment 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 andreaskelm/pm-brain --skill opportunity-assessment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/opportunity-assessment, .gemini/skills/opportunity-assessment, .github/skills/opportunity-assessment and .opencode/skills/opportunity-assessment in your project.
What does Opportunity Assessment need to run?
SKILL.md names no scripts, command-line tools or credentials: Opportunity Assessment is instructions for the agent only.
Does Opportunity Assessment 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 Opportunity Assessment 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 Opportunity Assessment use?
Opportunity Assessment has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Opportunity Assessment use?
About 2.5k tokens (SKILL.md is roughly 10k 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 2k tokens, read only when the agent opens those files.
What are the alternatives to Opportunity Assessment?
Skills that share tags, products or a category with Opportunity Assessment: Schematic (blader/schematic, 241 stars), Vscuse Scenario Authoring (OfficeDev/microsoft-365-agents-toolkit, 780 stars), App Spec Packager (instructa/agent-skills, 139 stars) and Review (golbin/agent-skills, 214 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Opportunity Assessment?
andreaskelm (a GitHub user) maintains it in andreaskelm/pm-brain, which has 234 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 9, 2026.
Source: andreaskelm/pm-brain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.