← Clerq Patent ResearchCONTENT HISTORY
WHAT CHANGED
Update to Clerq Patent Research
Snapshot Oct 24, 2026 · 13:46 UTC · version 0.1.4
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Clerq Patent Research and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use Clerq when the user wants patent prior-art research, similar-patent discovery, patent-document lookup, or patentability triage.",
"included_files": [],
"name": "patent-research",
"skill_md_contents": "---\nname: patent-research\ndescription: Use Clerq when the user wants patent prior-art research, similar-patent discovery, patent-document lookup, or patentability triage.\n---\n\n# Clerq patent research\n\nUse the Clerq MCP server for patent research tasks.\n\n## Workflows\n\n- For an invention, technical concept, or problem description, use semantic patent search. Describe the subject matter naturally rather than constructing Boolean or keyword syntax.\n- For a known patent, use similar-patent discovery with its publication, application, or grant number.\n- For document analysis, retrieve only the patent fields needed for the current task. Request claims or descriptions only when the user actually needs full-text analysis.\n- For patentability triage, explain that the workflow is asynchronous. Starting triage consumes the account's configured Clerq triage credit. After starting it, return the workflow ID and do not immediately poll in the same turn. In a later turn, follow Clerq's returned polling instructions and retrieve only the requested result sections.\n\n## Guardrails\n\n- Do not present research results as legal advice or guarantee patentability, validity, infringement outcomes, or grant of a patent.\n- Do not invent patent records, tool results, or completed triage results.\n- Do not use patent-research tools for unrelated tasks.\n- For side-effecting or billable operations, make the user-visible consequence clear before initiating them when required by the host.\n"
}SHA-256 of public snapshot: e39dd01aaf7cdc14ed52f1ffd16faa8d4a469225a2b8bd70a853c649ec3ef021