assess-ip-landscape
关于
This skill analyzes the intellectual property landscape for a given technology, identifying patent clusters, competitor portfolios, and potential freedom-to-operate risks. It provides strategic recommendations for IP positioning and white space opportunities. Developers should use it before starting new R&D, evaluating market entry, or preparing for investment due diligence.
快速安装
Claude Code
推荐npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/assess-ip-landscape在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
Assess IP Landscape
Map intellectual property landscape for technology area — identify patent clusters, white spaces, key players, freedom-to-operate risks. Produces strategic assessment that informs R&D direction, licensing decisions, IP filing strategy.
When Use
- Before starting R&D in new technology area (what's already claimed?)
- Evaluating market entry where incumbents have strong patent portfolios
- Preparing for investment due diligence (IP asset assessment)
- Informing patent filing strategy (where to file, what to claim)
- Assessing freedom-to-operate risk for new product or feature
- Monitoring competitor IP activity for strategic positioning
Inputs
- Required: Technology domain or product area to assess
- Required: Geographic scope (US, EU, global)
- Optional: Specific competitors to focus on
- Optional: Own patent portfolio (for gap analysis and FTO)
- Optional: Time horizon (last 5 years, last 10 years, all time)
- Optional: Classification codes (IPC, CPC) if known
Steps
Step 1: Define Search Scope
Establish boundaries of landscape analysis.
- Define technology domain precisely:
- Core technology area (e.g., "transformer-based language models" not "AI")
- Adjacent areas to include (e.g., "attention mechanisms, tokenization, inference optimization")
- Areas to explicitly exclude (e.g., "computer vision transformers" if focusing on NLP)
- Identify relevant classification codes:
- IPC (International Patent Classification) — broad, used worldwide
- CPC (Cooperative Patent Classification) — more specific, US/EU standard
- Search WIPO's IPC publication or USPTO's CPC browser
- Define geographic scope:
- US (USPTO), EU (EPO), WIPO (PCT), specific national offices
- Most analyses start with US + EU + PCT for broad coverage
- Set time window:
- Recent activity: last 3-5 years (current competitive landscape)
- Full history: 10-20 years (mature technology areas)
- Watch for expired patents that open up design space
- Document scope as Landscape Charter
Got: Clear, bounded scope that is specific enough to produce actionable results but broad enough to capture relevant competitive landscape. Classification codes identified for systematic search.
If fail: Technology domain too broad (thousands of results)? Narrow by adding technical specificity or focusing on specific application area. Too narrow (few results)? Broaden to adjacent technologies. Right scope typically yields 100-1000 patent families.
Step 2: Harvest Patent Data
Collect patent data within defined scope.
- Query patent databases using Landscape Charter:
- Free databases: Google Patents, USPTO PatFT/AppFT, Espacenet, WIPO Patentscope
- Commercial databases: Orbit, PatSnap, Derwent, Lens.org (freemium)
- Combine keyword search + classification codes for best coverage
- Build search queries systematically:
Query Construction:
+-------------------+------------------------------------------+
| Component | Example |
+-------------------+------------------------------------------+
| Core keywords | "language model" OR "LLM" OR "GPT" |
| Technical terms | "attention mechanism" OR "transformer" |
| Classification | CPC: G06F40/*, G06N3/08 |
| Date range | filed:2019-2024 |
| Assignee filter | (optional) specific companies |
+-------------------+------------------------------------------+
- Download results in structured format (CSV, JSON) including:
- Patent/application number, title, abstract, filing date
- Assignee/applicant, inventor(s)
- Classification codes, citation data
- Legal status (granted, pending, expired, abandoned)
- Deduplicate by patent family (group national filings of same invention)
- Record total patent family count and source databases
Got: Structured dataset of patent families within scope, deduplicated and timestamped. Dataset is foundation for all subsequent analysis.
If fail: Database access limited? Google Patents + Lens.org (free) provide good coverage. Query returns too many results (>5000)? Add technical specificity. Too few (<50)? Broaden keywords or add classification codes.
Step 3: Analyze Landscape
Map patent clusters, key players, trends.
- Cluster analysis: Group patents by sub-technology:
- Use classification codes or keyword clustering to identify 5-10 sub-areas
- Count patent families per cluster
- Identify which clusters growing (recent filing surges) vs. mature (flat or declining)
- Key player analysis: Identify top 10 assignees by:
- Total patent family count (portfolio breadth)
- Recent filing rate (last 3 years — current activity)
- Average citation count (patent quality proxy)
- Geographic filing breadth (US-only vs. global filings)
- Trend analysis: Chart filing trends over time window:
- Overall filing volume by year
- Filing volume by cluster by year
- New entrants (assignees filing for first time in domain)
- Citation network: Identify most-cited patents (foundational IP):
- High forward citations = heavily relied upon by subsequent filings
- These are likely blocking patents or essential prior art
- Produce Landscape Map: clusters, players, trends, key patents
Got: Clear picture of who owns what, where activity concentrated, how landscape evolving. Key blocking patents identified. White spaces (areas with few filings) visible.
If fail: Dataset too small for meaningful clustering? Combine clusters into broader groups. One assignee dominates (>50% of filings)? Analyze their portfolio as separate sub-landscape.
Step 4: Identify White Spaces and Risks
Extract strategic insights from landscape.
- White space analysis (opportunities):
- Technology areas within scope with few or no patent filings
- Expired patent families where design space has reopened
- Active areas where only one player has filed (first-mover but no competition)
- White spaces adjacent to growing clusters (next frontier)
- FTO risk screening (threats) — adapted from
healtriage matrix:- Critical: Granted patents directly covering your planned product/feature
- High: Pending applications likely to grant with relevant claims
- Medium: Granted patents in adjacent areas that could be broadly interpreted
- Low: Expired patents, narrow claims, or geographically irrelevant filings
- Competitive positioning:
- Where does your portfolio (if any) sit relative to competitors?
- Which competitors have blocking positions in your target areas?
- Which competitors might be interested in cross-licensing?
- Produce Strategic Assessment: white spaces, FTO risks, positioning, recommendations
Got: Actionable strategic recommendations: where to file, what to avoid, who to watch, what risks need detailed FTO analysis.
If fail: FTO risks identified? This screening is preliminary — does NOT replace formal FTO opinion from patent attorney. Flag critical risks for legal review. White spaces seem too good (valuable area with no filings)? Verify search scope didn't accidentally exclude relevant filings.
Step 5: Document and Recommend
Package landscape assessment for decision-makers.
- Write Landscape Report with sections:
- Executive summary (1 page: key findings, top risks, main recommendations)
- Scope and methodology (search terms, databases, date range)
- Landscape overview (clusters, trends, key players with visualizations)
- White space analysis (opportunities ranked by strategic value)
- Risk assessment (FTO concerns ranked by severity)
- Recommendations (filing strategy, licensing targets, monitoring alerts)
- Include supporting data:
- Patent family list (structured, sortable)
- Cluster map (visual)
- Filing trend charts
- Key patent summaries (top 10-20 most relevant patents)
- Set up ongoing monitoring:
- Define alert queries for new filings in critical areas
- Set review cadence (quarterly for active areas, annually for stable ones)
Got: Complete landscape report that enables strategic IP decisions. Report evidence-based, clearly scoped, actionable.
If fail: Report too large? Produce executive summary first and offer detailed sections on request. Executive summary should always stand alone as decision document.
Validation Checklist
- Landscape Charter defines scope, classification, geography, time window
- Patent dataset harvested from multiple databases and deduplicated
- Clusters identified with filing counts and trend direction
- Top 10 key players profiled with portfolio metrics
- White spaces identified and ranked by strategic value
- FTO risks screened and classified by severity
- Key blocking patents identified with citation analysis
- Recommendations specific and actionable
- Limitations acknowledged (screening vs. formal FTO opinion)
- Monitoring alerts defined for ongoing landscape tracking
Pitfalls
- Too broad a scope: "AI patents" is not landscape — it's ocean. Be specific about technology and application
- Single-database reliance: No single patent database has complete coverage. Use at least two sources
- Ignoring patent families: Counting individual filings instead of families inflates numbers. One invention filed in 10 countries is one patent family, not ten
- Confusing applications with grants: Pending application is not enforceable right. Distinguish between granted patents and published applications
- White space misinterpretation: Empty area might mean "nobody tried" or "everybody tried and failed." Investigate before assuming opportunity
- Landscape as legal opinion: This skill produces strategic intelligence, not legal advice. FTO risks flagged here need formal analysis by patent counsel
See Also
search-prior-art— Detailed prior art search for specific inventions or patent validity challengesscreen-trademark— Trademark conflict screening and distinctiveness analysis for trademark side of IP landscapesfile-trademark— Trademark filing procedures for EUIPO, USPTO, Madrid Protocolsecurity-audit-codebase— Risk assessment methodology parallels IP risk screeningreview-research— Literature review skills apply to prior art analysis
GitHub 仓库
相关推荐技能
executing-plans
设计该Skill用于当开发者提供完整实施计划时,以受控批次方式执行代码实现。它会先审阅计划并提出疑问,然后分批次执行任务(默认每批3个任务),并在批次间暂停等待审查。关键特性包括分批次执行、内置检查点和架构师审查机制,确保复杂系统实现的可控性。
requesting-code-review
设计该Skill可在完成任务、实现主要功能或合并代码前自动调度代码审查子代理,确保实现符合需求和计划。它支持通过指定git SHA范围进行精准的代码变更审查,帮助开发者在关键节点及时发现潜在问题。核心原则是"早审查、勤审查",适用于开发流程的各个关键阶段。
connect-mcp-server
设计这个Skill指导开发者如何将MCP服务器连接到Claude Code,支持HTTP、stdio和SSE三种传输协议。它涵盖了从安装配置到认证安全的完整流程,适用于集成GitHub、Notion、数据库等外部服务。当开发者需要添加集成、配置外部工具或提及MCP相关功能时,这个Skill能提供实用的操作指南。
web-cli-teleport
设计该Skill帮助开发者根据任务特性选择Claude Code的Web或CLI界面,并指导如何在两种环境间无缝迁移会话。它能分析任务复杂度、迭代需求等要素,推荐最优工作界面和工作流。关键特性包括会话状态管理、环境切换指导和上下文优化建议。
