casemark/biotech-patent-summaries
skills/legal/biotech-patent-summaries/SKILL.md
Summarizes biotech patent families and disputes into litigation-ready intelligence briefs. Trigger when the user provides patent applications, issued patents, PTAB filings, prosecution histories, licensing materials, or litigation documents in biotechnology domains and requests a summary, risk assessment, or FTO analysis.
$ install --global
skillsauthnpx skillsauth add casemark/skills biotech-patent-summariesInstall 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: May 25, 2026, 3:29 AM20.5s1 file scanned
SKILL.md
- name:
- biotech-patent-summaries
- language:
- en
- description:
- >-
Biotechnology Patent Summaries
Produce a source-grounded intelligence brief on biotech patents and disputes for litigation, portfolio, and executive decisions.
Quick Start
- Collect inputs: patent corpus, dispute materials, parties/products map, jurisdiction scope, and clear objective (litigation exposure, licensing, design-around, or FTO).
- Run the core workflow below.
- Deliver the output template with uncertainty tags on every analytical assertion.
Core Workflow
- Ingest & normalize — Gather patent identity, claim sets, prosecution history, and dispute metadata. Normalize dates to ISO format. Define technical terms on first use.
- Extract & map claims — Identify independent claims first, quote critical language verbatim, then map dependents and fallback embodiments.
- Analyze validity/infringement — Test enforceability vectors:
- §101 eligibility (methods, diagnostics, natural products)
- §102/103 novelty and obviousness
- §112 enablement/written description (especially genus claims over biological matter)
- Assess procedural & business impact — Quantify litigation risk (timeline, injunction exposure, claim-construction volatility), cross-jurisdiction differences, and commercial consequences.
- Compile deliverable — Fill the output template; tag every item as confirmed fact, party argument, or analytical assessment.
Input Capture
| Bucket | Key Fields | |---|---| | Patent identity | Patent/app no., family ID, filing/priority/grant dates, assignee | | Technical scope | Mechanism, target, platform, key molecules/processes | | Claim set | Independent/dependent claims, types, limitations, embodiments | | Status | Pending/granted/abandoned, IPR/opposition posture, deadlines | | Dispute metadata | Court/tribunal, parties, accused products, allegations | | Procedural calendar | Hearings, motions, claim construction, trial dates (with certainty rating) | | Strategic posture | Commercial significance, exclusivity, competitor landscape, remedies sought |
Output Template
# [Matter Title]
Current through: [DATE]
## 1) Executive Summary
Three short paragraphs: patent landscape, key legal issues, action recommendations.
## 2) Patent/Dispute Snapshot
| Field | Value |
|---|---|
| Identifier | |
| Jurisdiction(s) | |
| Parties | |
| Status | |
| Urgency | |
## 3) Claim & Scope Analysis
| Claim # | Text excerpt | Breadth | FTO relevance | Risk flags |
|---|---|---|---|---|
## 4) Validity & Prior-Art Assessment
| Ground | Basis | Record support | Counterargument strength | Probability |
|---|---|---|---|---|
## 5) Infringement Analysis
| Accused product/method | Claim-mapped match | Defense argument space | Exposure |
|---|---|---|---|
## 6) Dispute Timeline
| Date | Event | Forum | Strategic effect |
|---|---|---|---|
## 7) Strategic Recommendations
- [ ] Litigation strategy
- [ ] Licensing / settlement
- [ ] Design-around / alternative pathway
- [ ] Portfolio filing or challenge
- [ ] Regulatory and exclusivity coordination
## 8) Uncertainty Register
Confirmed facts | Documented allegations | Analytical assumptions | Open gaps
Deliverable Rules
- Citation discipline — Cite patent numbers, claim/paragraph refs, docket entries; no uncited assertions.
- Scope discipline — Label each statement as fact, party argument, or analysis.
- Technical precision — Keep scientific language exact; do not oversimplify in ways that change meaning.
- Jurisdiction tags — Label every legal standard by jurisdiction and confidence level.
- Currency — State explicit "current through" date and stop-line assumptions.
Pitfalls & Checks
- No legal advice; provide neutral counsel-grade analysis only.
- Default to US jurisdiction unless explicitly labeled otherwise.
- Do not overstate claim scope where specification support is thin.
- Flag missing records as "needs confirmation" — never infer.
- [VERIFY] Confirm current case law before finalizing eligibility/invalidation analysis, especially for biotech diagnostic and sequence-related claims.
- [VERIFY] Cross-check AIA first-inventor-to-file effects, PGR/IPR timing windows, and equitable doctrines for US patents.
- For biologics, evaluate regulatory exclusivities (orphan, pediatric, biologics data exclusivity) alongside patent rights.
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