$ loading_
Screen potential blocking patents and draft a non-opinion FTO triage memo.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "fto-triage" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/ip-legal/skills/fto-triage/SKILL.md 2. Save it as ~/.claude/skills/fto-triage/SKILL.md 3. Reload skills and tell me it's ready
Please run an FTO triage for 'an on-device speech recognition feature for consumer wearables, launching in the US first.' Start by stating this is not a formal FTO opinion, then list missing intake details, identify 2-5 plausible patents, and build a first-pass element-by-element comparison for the most relevant independent claims.
A patent-blocking triage memo with a disclaimer, missing information, candidate patents, first-pass claim charts, open questions, and next-step recommendations.
We already have three potentially relevant patents. Run an FTO triage for a new process using only these patents, and do not conclude it is clear to launch. Compare the process against each independent claim element by element, and separately flag doctrine-of-equivalents, indirect infringement, or divided infringement risks.
A structured triage analysis centered on the known patents, highlighting which claims most warrant further counsel review.
Please turn this FTO triage into a handoff memo for patent counsel, clearly stating it is not an FTO opinion, and list the issues a formal study still needs to resolve, such as enforceability, prosecution history, IPR outcomes, licensing availability, and the assignee's enforcement history.
A counsel-ready handoff memo that supports a subsequent formal FTO study.
Product managers or engineering teams can use it for a structured first look when evaluating a new product, feature, or process. It helps identify the most plausible patents and claims, but it does not replace a formal FTO opinion.
When a team already knows a few suspicious patents, it can use this skill to perform an element-by-element first pass on independent claims. This helps organize high-risk areas and evidence gaps before patent counsel steps in.
When a team is asking whether anything may block a launch, this skill can surface the issues a formal study still needs to answer. Examples include enforceability, prosecution history, IPR outcomes, licensing availability, and the assignee's enforcement history.
The documentation emphasizes that /fto-triage is only a structured first-pass review of potentially blocking patents, not a formal FTO opinion. It describes an intake process covering the product or process, technical details, jurisdictions, known patents, and timing; optional preliminary patent searching if a connector is available; and first-pass, element-by-element claim charts for the most plausible patents. It also calls for listing open issues for a real FTO study, recommended next steps, and a willfulness warning.
This is not a freedom-to-operate opinion. A formal FTO opinion requires a comprehensive search, full claim construction, and element-by-element infringement analysis by registered patent counsel. Patent infringement is strict liability; willful infringement triples damages. A "no obvious blocking patents" result from this skill means the triage didn't find one — it does not mean the product is clear.
~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md. If it
contains [PLACEHOLDER], stop and direct to /ip-legal:cold-start-interview.This skill never concludes that a product is clear to launch. If uncertain, flag — patent counsel decides.
/ip-legal:fto-triage "an on-device speech recognition model for consumer wearables, US launch first"
/ip-legal:fto-triage
The loudest guardrail in the plugin. Say this at the top of every output. Do not drop it. Do not soften it. Do not let the reader skim past it.
This is not a freedom-to-operate opinion. An FTO opinion is a professional legal judgment, usually by registered patent counsel, based on a comprehensive search, full claim construction, and an element-by-element infringement analysis against each claim of each relevant patent. This triage is a structured first look at what might be out there. A "no obvious blocking patents" result means the triage didn't find one — it does not mean the product is clear. Patent infringement is strict liability; willful infringement (which can follow from knowing about a patent and proceeding anyway) triples damages under 35 U.S.C. § 284. The decision to launch, make, use, sell, or import is a business decision informed by a formal FTO study and counsel's judgment — not by this triage. A registered patent attorney or agent evaluates before anyone relies on this for a product decision.
Under-flagging a blocking patent is a one-way door — a product launched, a deposition a year later, treble damages on the table. Over-flagging is a two-way door — the attorney narrows the list in a read-through. Stay on the two-way door side. Always.
Reading this triage is reading something about patents. Reading something about patents can, in some circumstances, factor into a willfulness analysis down the road. This is one reason the output is marked as privileged when a lawyer is using it, and why the non-lawyer output is framed as research to take to counsel. Do not discuss specific patents surfaced by this triage outside privileged channels.
…
No. The documentation repeatedly states that it is only a structured first look, not a freedom-to-operate opinion, and it cannot be used to conclude that a product is clear to launch.
The documentation says intake should cover the product or process, technical details, jurisdictions, known patents, and timing. This helps narrow plausible patents and support the first-pass comparison.
Yes. The docs say that if a patent research connector is available, it can run a preliminary search; otherwise, it should say so in the output and proceed using the patents supplied by the user.
Search watched skill registries, preview matches, and inspect SKILL.md before installing.
Draft DMCA notices, triage incoming claims, and prepare counter-notice drafts.
Standardize new matter intake and generate matter files plus a structured log.
Compare proposed handbook edits and identify cross-reference and state supplement impacts.
Review offer letters and restrictive covenants with jurisdiction-specific hiring checks.
Manage matter workspaces to separate, switch, and archive client contexts.
Assess code patentability, filing readiness, and prior-art risk signals.
Evaluate code patentability, filing readiness, and prior-art risk signals.
Quickly classify incoming NDAs by approval path and legal risk.
Triage support tickets by priority, ownership, and duplicate or known issue checks.
Triages fictional insurance claims and summarizes key intake details and priority.
Helps users triage workspace content items for next-step handling.