assess-prior-art-and-claims
Skill504 starsChanged 52 days agoApache-2.0View on GitHub
Assess novelty/prior art and claim scope by decomposing claims, tracing relevant families, and checking status/provenance.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- yogsoth-ai/de-anthropocentric-research-engineword for word, first seen Sep 25, 2026
Other versions1 project uses a version of this.
Word for word · 1
- yogsoth-ai/de-anthropocentric-research-engine★ 505100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository270 other files it gives its agents.
- abstract-structureSkill
- adjudicate-exchangeSkill
- adjust-abstraction-scopeSkill
- adversarial-deliberationSkill
- aggregate-rankingSkill
- analogical-discoverySkill
- analyze-constraints-readinessSkill
- analyze-experiment-resultsSkill
- analyze-future-scenariosSkill
- analyze-heterogeneitySkill
- analyze-interventionSkill
- analyze-leaderboard-dynamicsSkill
- analyze-patent-citation-networkSkill
- analyze-scaling-regimeSkill
- analyze-temporal-trajectorySkill
- apply-perturbationSkill
- apply-question-frameworkSkill
- apply-separation-principleSkill
- apply-stage-gateSkill
- apply-veto-filterSkill
- appreciative-reframeSkill
- assess-construct-validitySkill
- assess-evidence-saturationSkill
- assess-goal-feasibilitySkill
- assess-patent-claim-scopeSkill
- assess-patent-legal-statusSkill
- assess-problem-wickednessSkill
- assess-publication-biasSkill
- assess-question-qualitySkill
- assess-ranking-consistencySkill
- assess-readiness-dimensionSkill
- assess-removabilitySkill
- assess-sensitivitySkill
- assess-system-boundarySkill
- assumption-stress-testSkill
- atomize-claimSkill
- atomize-conceptSkill
- attach-evidence-to-relationSkill
- audit-benchmark-validitySkill
- audit-convergence-independenceSkill
- audit-data-contaminationSkill
- audit-explanatory-compressionSkill
- audit-reporting-qualitySkill
- audit-structural-equivalenceSkill
- audit-structure-consistencySkill
- audit-study-validitySkill
- audit-validator-independenceSkill
- biologize-problemSkill
- biomimetic-transferSkill
- build-concept-fanSkill
- build-current-reality-treeSkill
- build-domain-ontologySkill
- build-failure-chainSkill
- build-noncircularity-matrixSkill
- calibrate-adversarial-confidenceSkill
- calibrate-probability-forecastSkill
- canonicalize-entitySkill
- categorize-evidenceSkill
- challenge-assumptionSkill
- characterize-anomalySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 22
Do not perform called SOP operations inline.
- Very specific: line 29
If the retained claims expose absent feature combinations, consider map-patent-white-space as the next tactic.
- Distinctive: line 42
Every claim element must map to a cited source or be marked unsupported.
- Distinctive: line 48
Do not call a claim novel because no result was found.
≈ “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.
Files
assess-prior-art-and-claims
Purpose
Assess novelty, prior art, claim scope, legal-status observations, and provenance without making unsupported legal conclusions.
Input contract
required: [claim_set, target_domain, jurisdiction_scope]
optional: [known_families, search_context, evidence_records]
constraints: [claim text and source provenance required, jurisdiction and observation date must be explicit]Execution protocol
Do not perform called SOP operations inline; each loaded SOP owns its contract and thresholds.
- You MUST load skill
parse-patent-claimto parse independent and dependent claims and map elements to technical functions. - You MUST load skill
trace-patent-familyto trace priority, family, continuation, and citation relationships. - You MUST load skill
assess-patent-claim-scopeto assess breadth, limiting elements, overlap, and design-around vulnerability. - You MUST load skill
assess-patent-legal-statusto classify observed status by jurisdiction and date. - You MUST load skill
verify-evidence-independenceto check source independence before synthesizing novelty findings. If the retained claims expose absent feature combinations, considermap-patent-white-spaceas the next tactic.
Deviation: Skip status or independence checks only when the corresponding input is absent; record the omission as an open question. Do not infer legal status from an undated or single-source record.
Output contract
produces: [claim_element_map, prior_art_family_map, scope_assessment, legal_status_observations, novelty_findings]
delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]Thresholds and quality gates
- Every claim element must map to a cited source or be marked unsupported.
- Any acquisition threshold must use a declared eligible family/source universe and relative coverage, not a fixed historical count.
- Status observations require jurisdiction, observation date, source, and uncertainty.
Failure and counterexamples
Do not call a claim novel because no result was found; mark search coverage and unresolved elements. Do not collapse related family members into one record when claim scope or jurisdiction differs.
Provenance map
resolved: prior-art-searchresolved: knowledge-acquisition-claim-analysisresolved: knowledge-acquisition-claim-decompositionresolved: claim-parsingresolved: legal-status-assessment
Preserved source criteria ledger
| source | source line | kind | source criterion |
| claim-analysis | 4435 | numeric/textual | Budget 30 families / 30 claim / 20 web; HARD-GATE. |
Context checkpoint / Delta notes
Append claim elements, family links, scope uncertainties, status observations, source-independence judgments, and unresolved search questions.
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
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.

