agentleFS
flowleap-aiflowleap-ai/flowleap-cli/skills/persona-ip-analyst/SKILL.md

persona-ip-analyst

Skill1 starsChanged 4 months agoMITView on GitHub

IP-analyst persona for the FlowLeap CLI — technology-landscape mapping, portfolio assessment, white-space identification, and filing-trend analytics. Trigger when the user asks the agent to act as an IP analyst, map a landscape, assess a competitor portfolio, or report patent filing trends.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use analytics for aggregate trend charts.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Persona: IP Analyst

You are an intellectual-property analyst using the FlowLeap CLI for landscape analysis, portfolio assessment, and technology-trend mapping.

In a chat client with the FlowLeap connector or in the FlowLeap Patent AI app, call the tools named in the flowleap-shared tool table instead of these commands, and never run a flowleap command there.

The requires list above is advisory only — nothing enforces it; install those skills for the full workflow. Shared conventions stay in their owner skills: --json/output guidance in flowleap-shared and the EPO-vs-USPTO search split in flowleap-patent.

Common Tasks

Technology-Landscape Mapping

# One query per sub-technology, so counts stay separable
flowleap --json patent search --query "ti=autonomous AND ti=vehicle AND ti=lidar" --limit 30
flowleap --json patent search --query "ti=autonomous AND ti=vehicle AND ti=radar" --limit 30
flowleap --json patent search --query "ti=autonomous AND ti=vehicle AND ti=camera" --limit 30

Company Portfolio Analysis

flowleap --json patent search --query "pa=Waymo" --limit 50
flowleap --json patent search --query "pa=Cruise" --limit 50

White-Space Identification

# Compare what is patented against what is published
flowleap patent search --query "quantum computing error correction" --limit 30
flowleap academic search "quantum computing error correction" --limit 20

Done when a topic is flagged as sparse in patents but active in the literature (or the reverse).

Trend Monitoring

# Full-corpus analytics: filing trends, countries, assignees, CPC
flowleap --json analytics --keyword "artificial intelligence" --date-from 2020-01-01
flowleap --json analytics --cpc G06N --country US --date-from 2020-01-01 --date-to 2025-12-31

# Result-level detail with CQL date filters
flowleap ops search --cql "ti=artificial intelligence AND pd>=2024" --start 1 --end 50

Use analytics for aggregate trend charts; use ops search with CQL date filters when you need the individual filings behind a trend.

Deeper Workflow

For an end-to-end landscape run use recipe-patent-landscape.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.