Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Claim Construction Chart

ASecurity

Drafts Joint Claim Construction Charts for patent litigation Markman hearings in US federal courts. Organizes disputed claim terms with competing party constructions, intrinsic/extrinsic evidence citations, and agreement status. Use when preparing claim construction charts, Markman hearing exhibits, or joint prehearing statements in IP litigation.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationgo

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill claim-construction-chart --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Claim Construction Chart?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Claim Construction Chart
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-claim-construction-chart/badge)](https://www.skillsdirectory.com/skills/lev-os-claim-construction-chart)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: claim-construction-chart
description: Drafts Joint Claim Construction Charts for patent litigation Markman hearings in US federal courts. Organizes disputed claim terms with competing party constructions, intrinsic/extrinsic evidence citations, and agreement status. Use when preparing claim construction charts, Markman hearing exhibits, or joint prehearing statements in IP litigation.
---

# Joint Claim Construction Chart

Drafts a joint claim construction chart presenting parties' competing interpretations of disputed patent claim terms for Markman proceedings.

## Prerequisites

- Asserted patent(s): number, title, issue date, inventors, full claim text
- Case caption: party names, court/division, civil action number
- Identified disputed terms from contentions or meet-and-confer
- Parties' proposed constructions with supporting intrinsic evidence
- Prosecution history: office action responses, amendments, examiner statements
- Applicable local patent rules (e.g., N.D. Cal., E.D. Tex., D. Del.)

## Quick Start

1. Gather patent documents, disputed terms, and both parties' proposed constructions
2. Identify the district's local patent rules for formatting requirements
3. Build the disputed terms table with per-term evidence citations
4. Classify each term as agreed, partially agreed, or disputed
5. Add certifications and signature blocks per local rules

## Output Structure

### Caption and Cover

Include: court (full designation with division), all parties, civil action number, patent(s) with number/title/issue date/inventors, and document title per local rules ("Joint Claim Construction Chart" or "Joint Claim Construction and Prehearing Statement").

### Disputed Terms Table

One row per disputed term with these columns:

| Column | Content |
|--------|---------|
| No. | Sequential or claim-order number |
| Claim Term | Exact language from patent |
| Claim No(s). | All claims where term appears |
| Context | Surrounding claim language for court reference |
| Plaintiff's Construction | Plain-language meaning + intrinsic evidence |
| Defendant's Construction | Plain-language meaning + intrinsic evidence |
| Agreement Status | Agreed / Partial / Disputed |

### Evidence Citations

For each proposed construction, cite intrinsic evidence:

- **Specification** — col:line (utility) or paragraph number (applications)
- **Claims** — related claim language providing definitional context
- **Prosecution history** — office action responses, amendments, applicant arguments
- **Figures/embodiments** — specific figures illustrating term meaning

All constructions follow *Phillips v. AWH Corp.*, 415 F.3d 1303 (Fed. Cir. 2005) (en banc): terms receive ordinary and customary meaning to a POSITA at time of invention, read in light of specification and prosecution history.

If extrinsic evidence is used, it is subordinate to intrinsic evidence per *Phillips*. Acceptable types: contemporaneous technical dictionaries/treatises, expert declarations (with qualifications and POSITA basis), prior art showing terminology usage, admissible inventor testimony.

### Agreement and Disagreement

For each term, classify as:

- **Full agreement** — present agreed construction; note no judicial construction needed
- **Partial agreement** — state agreed portions, isolate remaining disputes
- **Full disagreement** — summarize dispute nature (scope, embodiment limitation, prosecution history impact, indefiniteness)

### Indefiniteness Contentions

If a term is challenged under 35 U.S.C. § 112(b):

- State position in defendant's construction column
- Apply *Nautilus, Inc. v. Biosig Instruments, Inc.*, 572 U.S. 901 (2014): whether claim "inform[s] those skilled in the art about the scope of the invention with reasonable certainty"
- Provide factual and legal basis

### Certifications and Signatures

- Signature blocks for lead counsel (each party): name, bar number, firm, address, phone, email
- Meet-and-confer certification: dates, participants, good-faith compliance with local patent rules
- Any additional certifications required by local rules

## Checks and Pitfalls

- **Pin-cite everything** — specification col:line, prosecution history date/page, case reporter/page
- **Mirror structure** — defendant's section must parallel plaintiff's format exactly
- **Bluebook citations** — proper case names, reporters, pinpoints, parentheticals
- **USPTO conventions** — patent number, inventor names, issue date, col:line references
- **District-specific compliance** — check local rules for meet-and-confer requirements, page limits, font/margin rules, joint vs. separate filing
- **Jury-suitable constructions** — plain-language meanings understandable to a lay jury
- **Omit agreed terms** unless local rules require listing them
- **Flag same-term-different-context** — a term in multiple claims may warrant different constructions
- **Group related terms** by technology concept or claim element when logical

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →