assess-ip-landscape
정보
이 스킬은 특정 기술에 대한 지식 재산권 환경을 분석하여 특허 클러스터, 경쟁사 포트폴리오 및 잠재적 자유운영(FTO) 위험을 식별합니다. IP 포지셔닝과 백지(white space) 기회에 대한 전략적 권장사항을 제공합니다. 개발자는 새로운 연구 개발을 시작하기 전, 시장 진입을 평가할 때 또는 투자 실사 준비 시 이를 활용해야 합니다.
빠른 설치
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-landscapeClaude 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
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
