agentleFS
yogsoth-aiyogsoth-ai/de-anthropocentric-research-engine/skills/assess-patent-legal-status/SKILL.md

assess-patent-legal-status

Skill505 starsChanged 53 days agoApache-2.0View on GitHub

Classify observed patent/legal status and flag uncertainty or jurisdiction dependence.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every status is dated and jurisdiction-scoped.

    line 36
  2. Distinctive:

    Do not infer current validity from a filing event alone or transfer one jurisdiction's status to another.

    line 41

≈ “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

assess-patent-legal-status

Purpose

Classify observed patent status by jurisdiction and observation date while preserving uncertainty and source dependence.

Input contract

required: [patent_record, jurisdiction, observation_date, status_sources]
optional: [family_events, prosecution_events]
constraints: [status is an observation tied to dated sources, not an undated legal inference]

Procedure

  1. Normalize application, publication, grant, lapse, expiration, and abandonment events.
  2. Align events to jurisdiction and observation date.
  3. Reconcile conflicting source observations and preserve the disagreement.
  4. Emit status, confidence, and unresolved legal-status questions.

Output contract

produces: [status_timeline, jurisdiction_status, source_reconciliation, status_uncertainties]
delta_fields: [findings, evidence_updates, uncertainties, open_questions]

Quality gates

  • Every status is dated and jurisdiction-scoped.
  • Conflicts retain both source records and a reconciliation note.

Failure and counterexamples

Do not infer current validity from a filing event alone or transfer one jurisdiction's status to another.

Provenance map

  • resolved: knowledge-acquisition-legal-status-assessment

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.