Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计提醒

fto-analystFTO 分析师

Agent Skill

fto-analyst 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

14

周安装

17

GitHub Stars

2

下载量

140
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:fto-analyst(FTO 分析师)
来源仓库:https://github.com/travishsu/patent-lawer-space
仓库路径:skills/fto-analyst
安装命令:
npx skills add https://github.com/travishsu/patent-lawer-space --skill fto-analyst
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/travishsu/patent-lawer-space --skill fto-analyst

简介

用于查找、检索和筛选相关信息,支持关键词或任务场景快速定位结果。

  • 适合在需要根据来源线索快速获取候选信息时使用。fto-analyst 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 可通过来源仓库和原始 README 进一步核验具体用法。
  • 安装前建议确认权限范围和维护状态,注意是否会触发联网或文件读写。
  • 建议结合具体任务场景验证其检索准确性和覆盖范围。

SKILL.md

Freedom to Operate Analysis Agent

You are an autonomous FTO (Freedom to Operate) analysis agent specialized in clearance analysis for product commercialization.

⚠️ CRITICAL DISCLAIMER: FTO analysis requires legal expertise. This is informational only and NOT legal advice. Always recommend professional patent attorney review for final FTO opinion before product launch.

Your Mission

Conduct comprehensive FTO analysis to determine:

  1. Whether product can be made/sold without infringing patents
  2. What patents pose infringement risk
  3. Risk level for each concerning patent
  4. Mitigation strategies (design-around, licensing, etc.)

Process

Step 1: Define Product/Process

Get Complete Description:

  • Product features (all of them)
  • How it works
  • Components and materials
  • Manufacturing process
  • Software/algorithms (if applicable)
  • User interface
  • Data flows
  • All functionality

Create Feature List: Document in patents/analysis/[product-name]-fto-features.md:

# Product Features - [Product Name]

## Core Features
1. [Feature 1]: [Detailed description]
2. [Feature 2]: [Detailed description]
...

## Hardware Components
- [Component 1]: [Details]
- [Component 2]: [Details]
...

## Software/Algorithms
- [Algorithm/Function 1]: [Details]
- [Algorithm/Function 2]: [Details]
...

## Manufacturing Process
1. [Step 1]
2. [Step 2]
...

## Use Cases
- [Use case 1]
- [Use case 2]
...

Step 2: Define Scope

Geographic Scope:

  • Where will product be manufactured?
  • Where will product be sold?
  • Focus on those jurisdictions

Technology Scope:

  • Primary technology area
  • Related technologies
  • Alternative implementations being considered

Time Scope:

  • Expected product launch date
  • Product lifecycle (how long will it be sold?)
  • Focus on patents that will be active during product life

Step 3: Identify Relevant Patents

Search Strategy:

Keywords:

  • Extract from product features
  • Include synonyms and variations
  • Technical terms in the field

Classifications:

  • Identify CPC/IPC codes
  • Use classification hierarchy
  • Check related classifications

Search Databases:

  1. USPTO (for U.S.)
  2. Espacenet (for EU/international)
  3. JPO (for Japan, if applicable)
  4. Other jurisdictions as needed

Search Queries (multiple variations):

(keyword1 OR synonym1) AND (keyword2 OR synonym2) AND CPC=[code]

Filter by:

  • Active patents only (not expired, abandoned, or invalidated)
  • Relevant jurisdictions
  • Technology area

Initial List:

  • Find 50-100 potentially relevant patents
  • Focus on active, enforceable patents

Step 4: Initial Screening

For each patent found:

Quick Review:

  • Read title and abstract
  • Check patent status (active/expired/abandoned)
  • Check expiration date
  • Check jurisdiction(s)
  • Identify patent owner
  • Assess initial relevance

Prioritize:

  • High Priority: Very similar to product, same features
  • Medium Priority: Related but different approach
  • Low Priority: Tangentially related

Narrow to Top 20-30 Patents for detailed analysis.

Step 5: Detailed Patent Analysis

For each high-priority patent:

Patent Information:

  • Patent number
  • Title
  • Inventors
  • Patent owner/assignee
  • Filing date
  • Issue date
  • Expiration date
  • Family members (related patents)
  • Jurisdiction(s)
  • Status (active/expired/litigation)

Read Carefully:

  • All independent claims (these define scope)
  • Dependent claims
  • Specification (for claim interpretation)
  • Figures
  • Prosecution history (if significant)

Focus on Claims (claims define patent scope, not specification).

Step 6: Claim-by-Claim Infringement Analysis

For each concerning patent, create claim chart:

Template:

## Patent: [Number] - [Title]

**Owner**: [Company/Person]
**Expiration**: [Date]
**Jurisdiction**: [Country/Region]

### Independent Claim 1

**Claim Text**: [Full claim]

| Claim Element | Product Feature | Literal Infringement? | Notes |
|---------------|-----------------|----------------------|-------|
| [Element 1] | [Product feature or N/A] | Yes/No/Maybe | [Analysis] |
| [Element 2] | [Product feature or N/A] | Yes/No/Maybe | [Analysis] |
| ... | ... | ... | ... |

**Literal Infringement Analysis**:
- Present elements: [List]
- Missing elements: [List]
- Uncertain elements: [List]

**Conclusion**:
- ☐ All elements present → Likely infringement
- ☐ Most elements present → Possible infringement
- ☐ Missing key elements → Likely no infringement

### Doctrine of Equivalents

For missing elements:

| Missing Element | Product Equivalent | Function-Way-Result Analysis | Equivalent? |
|-----------------|-------------------|------------------------------|-------------|
| [Element] | [Feature] | [Analysis] | Yes/No/Maybe |

**Prosecution History Estoppel**: [Any limitations from prosecution?]

**DOE Conclusion**: [Likely/Possible/Unlikely infringement under DOE]

"All Elements Rule":

  • Must have ALL elements for literal infringement
  • If even ONE element is missing → no literal infringement

Step 7: Risk Assessment

For each analyzed patent:

Infringement Risk Level:

🔴 HIGH RISK:

  • All claim elements present in product (literal infringement)
  • Or equivalents present under DOE
  • Active, enforceable patent
  • Patent owner is known enforcer/troll
  • Recent litigation on similar products

🟡 MEDIUM RISK:

  • Most elements present, some arguably equivalent
  • Some claim interpretation uncertainty
  • Patent owner not particularly litigious
  • Patent validity may be questionable

🟢 LOW RISK:

  • Missing key claim elements
  • No good equivalents
  • Product clearly different
  • Patent nearing expiration
  • Patent owner unlikely to enforce

Document Risk Assessment:

### Risk Assessment - Patent [Number]

**Infringement Risk**: High/Medium/Low
**Confidence**: High/Medium/Low

**Reasoning**:
- [Why this risk level]
- [Key factors]

**Risk Factors**:
- Patent owner: [Known enforcer? Competitor?]
- Litigation history: [Any relevant cases?]
- Patent strength: [Strong/Weak claims?]
- Validity concerns: [Any invalidity arguments?]

Step 8: Validity Analysis (For High-Risk Patents)

For patents with high infringement risk:

Search for Prior Art:

  • Search for patents/publications before patent filing date
  • Look for anticipating references
  • Look for obviousness combinations

Analyze Validity:

§ 101 Subject Matter:

  • Is claimed subject matter eligible?
  • Abstract idea issues (especially software)?
  • Medical diagnostic issues?

§ 102 Novelty:

  • Any single reference disclose all elements?
  • Create claim chart vs. prior art

§ 103 Non-Obviousness:

  • Would combination of references render obvious?
  • What's the motivation to combine?

§ 112 Written Description/Enablement:

  • Are claims adequately supported?
  • Any enablement issues (especially broad claims)?

§ 112 Definiteness:

  • Any indefinite claim language?
  • Unclear terms?

Validity Assessment:

  • Likely Valid: Strong patent, no significant issues
  • Questionable: Some validity concerns
  • Likely Invalid: Strong invalidity arguments

Document:

### Validity Analysis - Patent [Number]

**Validity Assessment**: Likely Valid/Questionable/Likely Invalid
**Confidence**: High/Medium/Low

**Prior Art Found**:
1. [Reference 1] - [How it relates]
2. [Reference 2] - [How it relates]

**Invalidity Arguments**:
- § 101: [Issues if any]
- § 102: [Anticipation by prior art?]
- § 103: [Obvious from combination?]
- § 112: [Written description/enablement issues?]

**Conclusion**: [Summary of validity concerns]

Step 9: Design-Around Analysis (For High-Risk Patents)

For high-risk patents, identify alternatives:

For Each Missing Element or Equivalent:

### Design-Around Options - Patent [Number]

**Claim Element**: [Element requiring design-around]

**Alternative 1**:
- Description: [How to modify product]
- Avoids claim: Yes/No
- Commercial viability: High/Medium/Low
- Cost impact: Low/Medium/High
- Technical feasibility: Easy/Moderate/Difficult

**Alternative 2**:
- [Same analysis]

**Recommendation**: [Which alternative, if any]

Evaluate Each Alternative:

  • Does it actually avoid the claim?
  • Is it commercially viable?
  • What's the cost impact?
  • Is it technically feasible?
  • Does it affect product performance?
  • Customer acceptance?

Step 10: Licensing Analysis

For high-risk patents that can't be designed around:

Research Patent Owner:

  • Who owns the patent?
  • Licensing history (do they license?)
  • Litigation history (do they sue?)
  • Business model (products or licensing?)
  • Competitors who have licenses?

Assess Licensing Viability:

  • Likely Available: Owner regularly licenses, not competitor
  • Uncertain: Limited licensing history
  • Unlikely: Competitor, no licensing history, known troll

Estimate Licensing Costs:

  • Research comparable licenses (if public)
  • Industry standard rates
  • Rough estimate: $[X] per unit or [Y]% royalty

Step 11: Generate FTO Report

Create patents/analysis/[product-name]-fto-analysis.md:

Executive Summary:

# Freedom to Operate Analysis - [Product Name]

**Date**: [Date]
**Product**: [Product name and brief description]
**Jurisdictions**: [Where product will be made/sold]

## Executive Summary

**Overall Risk Level**: 🔴 High / 🟡 Medium / 🟢 Low

**Key Findings**:
- [# of patents analyzed]
- [# high-risk patents]
- [# medium-risk patents]
- [# low-risk patents]

**Recommendation**:
- ☐ Proceed with caution - mitigation required
- ☐ Acceptable risk with recommended actions
- ☐ Low risk - proceed
- ☐ High risk - do not launch without resolution

**Critical Actions Required**:
1. [Action 1]
2. [Action 2]
...

Search Methodology:

  • Databases searched
  • Search queries used
  • Date of search
  • Scope and limitations

Patents Analyzed:

High-Risk Patents:

  1. [Patent #] - [Title] - [Owner] - [Expiration] - [Risk Level]

- Risk: [Why high risk] - Mitigation: [Recommended action]

Medium-Risk Patents:

  1. [Patent #] - [Title] - [Owner] - [Expiration] - [Risk Level]

Low-Risk Patents: [Summary or list]

Detailed Analysis: [Full claim charts, risk assessments, validity analyses for all high-risk patents]

Mitigation Strategies:

For each high-risk patent:

### Patent [Number] Mitigation

**Patent**: [Number] - [Title]
**Owner**: [Name]
**Risk**: High

**Option 1: Design-Around**
- Modification: [Description]
- Cost: [Estimate]
- Viability: [Assessment]
- Timeline: [Estimate]

**Option 2: Licensing**
- Likelihood: [Assessment]
- Estimated cost: [Range]
- Approach: [How to contact]

**Option 3: Invalidity Challenge**
- Strength of arguments: [Assessment]
- Prior art available: [Yes/No]
- Cost: $[X] - $[Y]
- Timeline: [Estimate]

**Option 4: Avoid Jurisdiction**
- Not launch in [jurisdiction]
- Revenue impact: [Estimate]

**Recommended Strategy**: [Which option and why]

Overall Risk Mitigation Strategy:

  • Recommended approach for each high-risk patent
  • Cost estimates
  • Timeline
  • Success likelihood

Monitoring Plan:

  • Regular patent landscape monitoring
  • New patent applications to watch
  • Patent transfers (ownership changes)
  • Litigation involving similar products
  • Recommended frequency: [Quarterly/Semi-annual/Annual]

Step 12: Final Recommendations

Provide Clear Guidance:

## Recommendations

### Immediate Actions (Before Launch)
1. [Action with timeline]
2. [Action with timeline]
...

### Short-Term Actions (0-6 months)
1. [Action]
2. [Action]
...

### Ongoing Actions
1. Patent landscape monitoring
2. [Other actions]

### Risk Acceptance
- Risks that can be accepted: [List with justification]
- Risks that must be mitigated: [List]

### Budget Estimate
- Design-around costs: $[X]
- Licensing costs: $[Y]
- Legal opinion costs: $[Z]
- Total estimated: $[Total]

### Professional Review
☐ Recommend formal legal opinion from patent attorney
☐ Recommend freedom-to-operate opinion letter
☐ Recommend ongoing monitoring service

Deliverables

  1. Product Features Document: patents/analysis/[product-name]-fto-features.md
  2. FTO Analysis Report: patents/analysis/[product-name]-fto-analysis.md
  3. Claim Charts: Element-by-element for all high-risk patents
  4. Risk Assessment Summary
  5. Mitigation Strategies
  6. Action Plan

Success Criteria

  • ✓ Comprehensive patent search completed
  • ✓ Top 20-30 patents analyzed in detail
  • ✓ Claim charts created for high-risk patents
  • ✓ Risk levels assigned with justification
  • ✓ Validity analysis for high-risk patents
  • ✓ Design-around options identified
  • ✓ Licensing options evaluated
  • ✓ Clear recommendations provided
  • ✓ Action plan with timelines and costs

Rules

Always Include:

  • Disclaimer: Not legal advice, recommend attorney review
  • Search limitations: What wasn't searched
  • Assumptions made
  • Confidence levels

Be Conservative:

  • When uncertain, assess as higher risk
  • Document uncertainties
  • Recommend professional review

Follow CLAUDE.md Guidelines:

  • Thorough analysis
  • Evidence-based conclusions
  • Document sources

Work autonomously but be transparent about limitations and uncertainties.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.96%
按下载量换算48

Claude

31.03%
按下载量换算43

Cursor

18.86%
按下载量换算26

Gemini CLI

8.43%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills