Search the complete global patent database using natural language queries powered by Valyu's semantic search API.
Works with
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:
Fetches 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:
Restart Cursor to activate patents-search. Access via /patents-search 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
30
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
30
stars
Search the complete global patent database using natural language queries powered by Valyu's semantic search API.
The scripts/search commands in this documentation are relative to this skill's installation directory.
Before running any command, locate the script using:
PATENTS_SCRIPT=$(find ~/.claude/plugins/cache -name "search" -path "*/patents-search/*/scripts/*" -type f 2>/dev/null | head -1)
Then use the full path for all commands:
$PATENTS_SCRIPT "CRISPR gene editing methods" 15
When you run a search and receive "setup_required": true, follow this flow:
Ask the user for their API key: "To search patents, I need your Valyu API key. Get one free ($10 credits) at https://platform.valyu.ai"
Once the user provides the key, run:
scripts/search setup <api-key>
Retry the original search.
{
"success": true,
"type": "patents_search",
"query": "CRISPR gene editing methods",
"result_count": 10,
"results": [
{
"title": "Patent Title",
"url": "https://patents.google.com/...",
"content": "Patent claims, description, technical details...",
"source": "patents",
"relevance_score": 0.95,
"images": ["https://example.com/diagram.png"]
}
],
"cost": 0.025
}
# Get patent titles
scripts/search "query" 10 | jq -r '.results[].title'
# Get URLs
scripts/search "query" 10 | jq -r '.results[].url'
# Extract full content
scripts/search "query" 10 | jq -r '.results[].content'
# Find prior art
scripts/search "lithium ion battery electrode materials" 50
# Search competitor patents
scripts/search "CAR-T cell therapy manufacturing methods" 20
# Find technology trends
scripts/search "quantum computing error correction patents" 15
# Search for blocking patents
scripts/search "mRNA vaccine delivery systems" 25
All commands return JSON with success field:
{
"success": false,
"error": "Error message"
}
Exit codes:
0 - Success1 - Error (check JSON for details)https://api.valyu.ai/v1/searchscripts/
├── search # Bash wrapper
└── search.mjs # Node.js CLI
Direct API calls using Node.js built-in fetch(), zero external dependencies.
If you're building an AI project and want to integrate Patents Search directly into your application, use the Valyu SDK:
from valyu import Valyu
client = Valyu(api_key="your-api-key")
response = client.search(
query="your search query here",
included_sources=["valyu/valyu-patents"],
max_results=20
)
for result in response["results"]:
print(f"Title: {result['title']}")
print(f"URL: {result['url']}")
print(f"Content: {result['content'][:500]}...")
import { Valyu } from "valyu-js";
const client = new Valyu("your-api-key");
const response = await client.search({
query: "your search query here",
includedSources: ["valyu/valyu-patents"],
maxResults: 20
});
response.results.forEach((result) => {
console.log(`Title: ${result.title}`);
console.log(`URL: ${result.url}`);
console.log(`Content: ${result.content.substring(0, 500)}...`);
});
See the Valyu docs for full integration examples and SDK reference.
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.
kostja94/marketing-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
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