Skip to main content الرئيسية المنشئون thomasmoreai legal-skills-open patent-landscape
patent-landscape Use when analyzing biotech patent landscapes, identifying white spaces in pharmaceutical IP, tracking competitor patents, or assessing freedom to operate for drug development. Provides comprehensive patent analysis and strategic insights for life sciences innovation.
الانتقال إلى التثبيت سوق المهارات اكتشف واستكشف مهارات الذكاء الاصطناعي التي بناها المجتمع.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
عرض تفاصيل Prompt يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill patent-landscapeيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
تحميل Zip جاري التحميل... المزيد من هذا المستودع fetching-arbitration-rules Use when retrieving arbitration institutional rules (ICC, LCIA, SCC, SIAC, HKIAC, VIAC, МКАС/МАК при ТПП України, UNCITRAL) — fetching current version, verifying redaction applicable to the date of arbitration agreement, constructing URLs for official rule texts
determining-pl-request-regime Use when choosing the Polish legal regime for letters, requests, applications, complaints, petitions, public-information requests, KPA filings, PPSA complaints, RODO access requests, registry extracts, court-file access, tax/ZUS/cudzoziemcy/USC procedures, or professional lawyer letters. Prevents mixing UDIP, KPA, PPSA, RODO, registry, special-procedure, and advocate/radca letter regimes.
applying-new-york-convention Use when preparing applications for recognition and enforcement of foreign arbitral awards in Poland, applications for setting aside arbitral awards under KPC art. 1205–1211, or opposing such applications — mapping Article V of the 1958 New York Convention to art. 1214–1215 of the Polish KPC, identifying grounds for refusal, structuring public policy arguments
المهن ذات الصلة SOC
استنادا إلى تصنيف SOC المهني
name patent-landscape title Biotech Patent Landscape Analyzer description Use when analyzing biotech patent landscapes, identifying white spaces in pharmaceutical IP, tracking competitor patents, or assessing freedom to operate for drug development. Provides comprehensive patent analysis and strategic insights for life sciences innovation. author aipoch author_url https://github.com/aipoch/medical-research-skills/tree/main/scientific-skills/Evidence Insight/patent-landscape license MIT version 0.1.0 execution_mode open jurisdiction general practice ip language en
Source : https://github.com/aipoch/medical-research-skills
Biotech Patent Landscape Analyzer
Analyze biotech and pharmaceutical patent landscapes to identify opportunities, assess competition, and guide R&D strategy.
When to Use
Use this skill when the task needs Use when analyzing biotech patent landscapes, identifying white spaces in pharmaceutical IP, tracking competitor patents, or assessing freedom to operate for drug development. Provides comprehensive patent analysis and strategic insights for life sciences innovation.
Use this skill for evidence insight tasks that require explicit assumptions, bounded scope, and a reproducible output format.
Use this skill when you need a documented fallback path for missing inputs, execution errors, or partial evidence.
Key Features
Scope-focused workflow aligned to: Use when analyzing biotech patent landscapes, identifying white spaces in pharmaceutical IP, tracking competitor patents, or assessing freedom to operate for drug development. Provides comprehensive patent analysis and strategic insights for life sciences innovation.
Packaged executable path(s): scripts/main.py.
Reference material available in references/ for task-specific guidance.
Structured execution path designed to keep outputs consistent and reviewable.
Dependencies
Python: 3.10+. Repository baseline for current packaged skills.Third-party packages: not explicitly version-pinned in this skill package. Add pinned versions if this skill needs stricter environment control.
Example Usage
cd "20260318/scientific-skills/Evidence Insight/patent-landscape"
python -m py_compile scripts/main.py
python scripts/main.py --help
Example run plan:
Confirm the user input, output path, and any required config values.
Edit the in-file CONFIG block or documented parameters if the script uses fixed settings.
Run python scripts/main.py with the validated inputs.
Review the generated output and return the final artifact with any assumptions called out.
Implementation Details
See ## Workflow above for related details.
Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable.
Input controls: confirm the source files, scope limits, output format, and acceptance criteria before running any script.
Primary implementation surface: scripts/main.py.
Reference guidance: references/ contains supporting rules, prompts, or checklists.
Parameters to clarify first: input path, output path, scope filters, thresholds, and any domain-specific constraints.
Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects.
Quick Check Use this command to verify that the packaged script entry point can be parsed before deeper execution.
python -m py_compile scripts/main.py
Audit-Ready Commands Use these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.
python -m py_compile scripts/main.py
python scripts/main.py --help
Workflow
Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work.
Validate that the request matches the documented scope and stop early if the task would require unsupported assumptions.
Use the packaged script path or the documented reasoning path with only the inputs that are actually available.
Return a structured result that separates assumptions, deliverables, risks, and unresolved items.
If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion.
Quick Start from scripts.patent_landscape import PatentLandscapeAnalyzer
analyzer = PatentLandscapeAnalyzer()
landscape = analyzer.analyze(
therapeutic_area="CAR-T cell therapy" ,
date_range="2020-2024" ,
assignees=["Novartis" , "Kite Pharma" , "Juno Therapeutics" ]
)
Core Capabilities
1. Patent Search & Analysis results = analyzer.search_patents(
keywords=["CRISPR" , "gene editing" , "therapeutic" ],
classification="C12N15/113" ,
jurisdictions=["US" , "EP" , "WO" ]
)
Keyword-based : Technical terms + synonymsClassification-based : IPC/CPC codesCitation-based : Forward/backward citationsAssignee-based : Company portfolios
2. White Space Analysis opportunities = analyzer.identify_white_spaces(
technology="Antibody-drug conjugates" ,
target_diseases=["breast cancer" , "lung cancer" ],
existing_claims=landscape
)
White Space Opportunities:
Underserved disease indications
Novel combination therapies
Alternative delivery mechanisms
Geographical gaps (emerging markets)
3. Competitor Intelligence competitors = analyzer.analyze_competitors(
companies=["Pfizer" , "Moderna" , "BioNTech" ],
focus_area="mRNA vaccines"
)
Metric Description Portfolio size Total active patents Filing velocity Recent filing trends Geographic coverage Jurisdiction strategy Technology focus Core vs. peripheral areas Partnership patterns Collaboration trends
4. Freedom to Operate (FTO) Assessment fto = analyzer.assess_fto(
product_concept="Bispecific antibody targeting PD-1 and CTLA-4" ,
jurisdictions=["US" , "EU" , "Japan" ]
)
Identify relevant patent claims
Map claims to product features
Assess validity of blocking patents
Design around options
Licensing recommendations
CLI Usage
# Generate patent landscape report
python scripts/patent_landscape.py \
--query "immuno-oncology checkpoint inhibitors" \
--output landscape_report.pdf \
--format comprehensive
# Quick FTO check
python scripts/patent_landscape.py \
--fto "product_description.txt" \
--jurisdictions US EP JP
Data Sources
USPTO (United States)
EPO (Europe)
WIPO (Global)
JPO (Japan)
CNIPA (China)
References
references/ipc-classifications.md - IPC/CPC codes for biotechreferences/patent-search-strategies.md - Advanced search techniquesexamples/landscape-reports/ - Sample reports
Skill ID : 204 | Version : 1.0 | License : MIT
Output Requirements Every final response should make these items explicit when they are relevant:
Objective or requested deliverable
Inputs used and assumptions introduced
Workflow or decision path
Core result, recommendation, or artifact
Constraints, risks, caveats, or validation needs
Unresolved items and next-step checks
Error Handling
If required inputs are missing, state exactly which fields are missing and request only the minimum additional information.
If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.
If scripts/main.py fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.
Do not fabricate files, citations, data, search results, or execution outcomes.
Input Validation This skill accepts requests that match the documented purpose of patent-landscape and include enough context to complete the workflow safely.
Do not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:
patent-landscape only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.
References
Response Template Use the following fixed structure for non-trivial requests:
Objective
Inputs Received
Assumptions
Workflow
Deliverable
Risks and Limits
Next Checks
If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.
