Search the complete global patent database using natural language queries powered by Valyu's semantic search API.
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
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
Submit your Claude Code skill and start earning
epx add yorkeccak/scientific-skills --skill patents-searchCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpatents-searchExecute the skills CLI command in your project's root directory to begin installation:
epx add yorkeccak/scientific-skills --skill patents-searchFetches patents-search from yorkeccak/scientific-skills 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:
.cursor/skills/patents-search
Restart Cursor to activate patents-search. Access via /patents-searchin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
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.
google-search-console
kostja94/marketing-skills · Backend · tag: search
powerpoint
igorwarzocha/opencode-workflows · Productivity · same category
pwa-expert
erichowens/some_claude_skills · Productivity · same category
sports-betting-analyzer
onewave-ai/claude-skills · Productivity · same category
cmux-browser
manaflow-ai/cmux · Productivity · same category
modly-image-to-3d
aradotso/trending-skills · Productivity · same category
Useful defaults in patents-search — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for patents-search matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in patents-search — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: patents-search is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added patents-search from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: patents-search is focused, and the summary matches what you get after install.
patents-search is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
patents-search is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
patents-search reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend patents-search for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 48