Fetch external documentation, references, and context for a query. Decomposes into 2-5 facets and spawns parallel document-specialist Claude agents.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionexternal-contextExecute the skills CLI command in your project's root directory to begin installation:
Fetches external-context from yeachan-heo/oh-my-claudecode and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate external-context. Access via /external-context in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
24.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.9K
stars
Fetch external documentation, references, and context for a query. Decomposes into 2-5 facets and spawns parallel document-specialist Claude agents.
/oh-my-claudecode:external-context <topic or question>
/oh-my-claudecode:external-context What are the best practices for JWT token rotation in Node.js?
/oh-my-claudecode:external-context Compare Prisma vs Drizzle ORM for PostgreSQL
/oh-my-claudecode:external-context Latest React Server Components patterns and conventions
Given a query, decompose into 2-5 independent search facets:
## Search Decomposition
**Query:** <original query>
### Facet 1: <facet-name>
- **Search focus:** What to search for
- **Sources:** Official docs, GitHub, blogs, etc.
### Facet 2: <facet-name>
...
Fire independent facets in parallel via Task tool:
Task(subagent_type="oh-my-claudecode:document-specialist", model="sonnet", prompt="Search for: <facet 1 description>. Use WebSearch and WebFetch to find official documentation and examples. Cite all sources with URLs.")
Task(subagent_type="oh-my-claudecode:document-specialist", model="sonnet", prompt="Search for: <facet 2 description>. Use WebSearch and WebFetch to find official documentation and examples. Cite all sources with URLs.")
Maximum 5 parallel document-specialist agents.
Present synthesized results in this format:
## External Context: <query>
### Key Findings
1. **<finding>** - Source: [title](url)
2. **<finding>** - Source: [title](url)
### Detailed Results
#### Facet 1: <name>
<aggregated findings with citations>
#### Facet 2: <name>
<aggregated findings with citations>
### Sources
- [Source 1](url)
- [Source 2](url)
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend external-context for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
external-context fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: external-context is the kind of skill you can hand to a new teammate without a long onboarding doc.
external-context fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
external-context is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in external-context — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
external-context is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: external-context is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: external-context is focused, and the summary matches what you get after install.
external-context is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 63