formated-results
Closing skill for the research-executor, loaded as the last step of formated-specs. Summarize the design just produced into one research-result JSON fenced…
Deep claim scope analysis — decompose independent/dependent claims and
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill claim-analysis --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/claim-analysisContext preview
The summary Claude sees to decide when to auto-load this skill.
Deep claim scope analysis — decompose independent/dependent claims and
name: claim-analysis description: 'Deep claim scope analysis — decompose independent/dependent claims and assess protection scope breadth. Budget: 30 patent families, 30 claim parses, 20 web searches.' execution: strategy dependencies: tactics: - classification-navigation - knowledge-acquisition-claim-decomposition - patent-family-tracing sops: - citation-network-analysis - claim-parsing - legal-status-assessment - patent-query-formulation - patent-synthesis - quality-scoring
Deep analysis of patent claim scope. Decomposes claim structure, maps element relationships, and assesses the breadth and strength of patent protection.
Provide detailed claim-level analysis for a set of target patents. Determines protection scope, identifies claim vulnerabilities, and maps the relationship between independent and dependent claims.
| Metric | Target | |--------|--------| | Patent families analyzed | 30 | | Claim parses | 30 | | Web searches completed | 20 |
| Metric | Target | Current | % | |--------|--------|---------|---| | Patent families analyzed | 30 | 0 | 0% | | Claim parses completed | 30 | 0 | 0% | | Web searches completed | 20 | 0 | 0% | | Independent claims parsed | — | 0 | — | | Claim elements extracted | — | 0 | — |
**HARD-GATE**: Cannot exit iteration loop until 80% of claim parses (24) and patent families (24) budget met.
| Tactic | When to Use | |--------|-------------| | claim-decomposition | Primary tactic — parse all claims and extract elements | | patent-family-tracing | Find family members with different claim scope | | classification-navigation | Understand technical context of claim elements |
| SOP | Role in This Strategy | |-----|----------------------| | claim-parsing | Core SOP — parse claim syntax and extract elements | | patent-query-formulation | Find related patents for scope comparison | | citation-network-analysis | Identify patents that cite or are cited by target | | legal-status-assessment | Confirm target patents are active | | quality-scoring | Assess claim quality (breadth, specificity, support) | | patent-synthesis | Produce claim analysis report |
1. **Target identification** — Identify patents for deep claim analysis 2. **Legal status check** — Confirm targets are active with `legal-status-assessment` 3. **Claim retrieval** — Fetch full claim text via web searches 4. **Claim parsing** — Use `claim-decomposition` tactic for full structural analysis 5. **Element extraction** — Extract all claim elements and map relationships 6. **Scope assessment** — Determine breadth of independent claims 7. **Vulnerability analysis** — Identify potential design-arounds and invalidity arguments 8. **Family comparison** — Check claim scope variations across jurisdictions 9. **Synthesis** — Produce detailed claim analysis report
# Claim Analysis Report: [Patent Number(s)] ## Patent Overview [Title, assignee, filing date, status] ## Claim Structure ### Independent Claims | Claim # | Type | Element Count | Scope Assessment | |---------|------|---------------|------------------| ### Claim Tree [Dependency hierarchy visualization] ## Element-by-Element Analysis ### Claim 1 | Element | Technical Feature | Breadth | Potential Design-Around | |---------|-------------------|---------|------------------------| ## Scope Assessment - Broadest claim: [claim #, scope description] - Narrowest claim: [claim #, scope description] - Key limitations: [elements that narrow scope] ## Vulnerability Analysis - Prior art risks: [elements with known prior art] - Enablement concerns: [overly broad elements] - Design-around paths: [alternative implementations] ## Cross-Jurisdiction Comparison [Claim scope differences across patent family members]
<!-- BEGIN available-tables (generated) -->
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use | | --- | --- | | classification-navigation | IPC/CPC hierarchy drill-down and lateral expansion for patent discovery | | knowledge-acquisition-claim-decomposition | Independent/dependent claim parsing, element extraction, and feature mapping to technical domains | | patent-family-tracing | Forward/backward patent citation and priority tracing until saturation |
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | citation-network-analysis | Build and analyze patent citation networks — main path analysis, PageRank, cluster detection | | claim-parsing | Patent claim syntax parsing — independent/dependent relationships and element extraction | | legal-status-assessment | Determine patent legal status — active, expired, pending, lapsed, or revoked | | patent-query-formulation | Construct keyword + IPC/CPC + assignee combination search strategies for patent databases | | patent-synthesis | Produce final structured patent intelligence report from all analysis results | | quality-scoring | Multi-dimensional patent quality assessment — forward citations, family size, claim count, geographic breadth |
<!-- END available-tables (generated) -->
The complete research orchestration system for AI-native science. What It Does Design Philosophy Architecture (v3.2.2) Quick Start Configuration Roadmap License DARE is not a tool that helps you do research. It is the researcher.
Repo: yogsoth-ai/de-anthropocentric-research-engine
Closing skill for the research-executor, loaded as the last step of formated-specs. Summarize the design just produced into one research-result JSON fenced…
Spec-slot skill for the research-executor. Emit the 4-layer DARE orchestration of the assigned topic as one research-graph JSON fenced block in your reply.…
Loss-1 judge (codex role). Given one sample's de-identified dialogue and its PolicyCard, decide axis-by-axis whether the user-simulator enacted the card's…
Loss-2 judge (codex role). Over one topic's 6 shuffled research-design samples, pairwise-rank by quality using the D1–D5 standard. Emit the pairwise log; the…
The optimizer brain for the ladder-foundry pretraining loop. Runs the two-level nested batch loop, delegates gating to gate_eval, attributes a failing batch to…
Tactic: Extract atomic units from one paper and score how much of a caller-supplied summary covers. Use for ACU-style binary or Nugget-style ternary recall…