Token导航 LogoToken导航

Agent Skill · 研究检索

fto-analyst(FTO 分析师)

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

fto-analyst 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 73,536。

总安装 14周安装 17GitHub Stars 2下载 140核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

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

建议结合具体任务场景验证其检索准确性和覆盖范围。

来源仓库内路径:skills/fto-analyst

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/travishsu/patent-lawer-space --skill fto-analy…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

fto-analyst 怎么安装?

在终端执行 npx skills add https://github.com/travishsu/patent-lawer-space --skill fto-analyst。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

fto-analyst 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

fto-analyst 需要什么权限?

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

fto-analyst 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

fto-analyst 用的人多吗?

公开数据是累计安装 14 次,近一周安装 17 次,下载 140 次,GitHub 2 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

fto-analyst 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
fto-analyst

FTO 分析师 · 本页

142只读未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.

平台分布

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 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills