casemark/patent-summary
skills/legal/patent-summary/SKILL.md
Generates structured, prosecution-ready summaries of patent applications covering bibliographic data, claims analysis, and strategic observations. Use when summarizing patent filings, preparing for prosecution, conducting portfolio review, licensing negotiations, or freedom-to-operate analysis.
$ install --global
skillsauthnpx skillsauth add casemark/skills patent-summaryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 2:13 PM419.1s1 file scanned
SKILL.md
- name:
- patent-summary
- description:
- Generates structured, prosecution-ready summaries of patent applications covering bibliographic data, claims analysis, and strategic observations. Use when summarizing patent filings, preparing for prosecution, conducting portfolio review, licensing negotiations, or freedom-to-operate analysis.
Patent Application Summary
Produces a structured summary of a patent application for prosecution, licensing, litigation, or portfolio management. Requires the application document (specification, claims, abstract, drawings) and any priority/related filings.
Quick Start
- Gather the patent application and any related filings
- Identify target audience (prosecution, licensing, litigation, portfolio)
- Generate the summary following the output structure below
- Flag prosecution risks and strategic observations
- Review against checks at the bottom
Output Structure
1. Executive Overview
Two to three sentences: invention essence, technical field, broadest claim scope.
2. Bibliographic Data
| Field | Extract | |---|---| | Application No. | — | | Filing Date | — | | Inventor(s) | — | | Assignee | — | | Priority Claims | — | | Related Applications | — | | Technical Field | — |
3. Background & Problem
- Problem the invention addresses
- Key prior art cited; how applicant distinguishes
- Novelty and non-obviousness positioning
4. Invention Description
- How it works — components, steps, or architecture
- Core innovations vs. prior art
- Key embodiments with practical applications
- Write accessibly for non-specialist attorneys; maintain technical precision
5. Drawings & Figures
| Figure | Description | |---|---| | Fig. N | — |
Summarize each referenced figure. Omit unreferenced figures.
6. Claims Analysis
| Claim | Type | Scope Summary | |---|---|---| | 1 | Independent | — | | N | Independent | — | | Key dependents | Dependent | — |
- Total claims: [count] — Independent: [count]
- Format flags: Note means-plus-function (§ 112(f)), Beauregard, or Jepson claims
7. Strategic Observations
Scope & Strength
- Claim breadth assessment
- Design-around vulnerabilities
- Commercially significant dependent claim narrowings
Prosecution Risk Flags
| Issue | Risk | Notes | |---|---|---| | Enablement (§ 112(a)) | Low/Med/High | — | | Written Description | Low/Med/High | — | | Indefiniteness (§ 112(b)) | Low/Med/High | — | | Prior Art Overlap | Low/Med/High | — |
Commercial & Portfolio
- Licensing or FTO considerations
- Recommended next steps
Checks
- Cite specific section headings, claim numbers, and figure references throughout
- Target 1–3 pages; balance comprehensiveness with conciseness
- Use precise IP terminology; keep descriptions accessible to non-specialist attorneys
- Flag potentially relevant uncited prior art with
[NOTE] - Do not opine on patentability — present observations only
- For continuations/divisionals, note parent filing relationship
- Default jurisdiction: U.S. (USPTO) unless specified otherwise
Shall I try writing this to the file again?
Related Skills
casemark/skills/legal/automated-contract-summary
development
VerifiedTrustedCommunity
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
21SKILL.mdUpdated May 26, 2026
casemark/obligation-mapping
tools
VerifiedTrustedCommunity
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
21SKILL.mdUpdated May 25, 2026
casemark/horizon-scanning
development
VerifiedTrustedCommunity
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
21SKILL.mdUpdated May 25, 2026
casemark/gap-analysis
testing
VerifiedTrustedCommunity
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.
21SKILL.mdUpdated May 25, 2026