Communitygithub.com

ThomasMoreAI/legal-skills-open

Professional skill for traffic accident liability assessment and determination. Triggers when users need accident analysis, scene photo evaluation, traffic law consultation, liability division, or legal basis queries.

What is legal-skills-open?

This professional skill provides expert traffic accident liability assessment based on the Road Traffic Safety Law of the People's Republic of China and related regulations, judicial interpretations. It supports analysis of accident descriptions, photo-assisted determination, legal citation, and professional liability allocation outputs. Designed for AI agents like Claude Code, Cursor, Codex, it helps users evaluate vehicle collisions, pedestrian accidents, and non-motor vehicle incidents. The skill follows a structured workflow: information collection, photo analysis, liability determination with a four-layer framework (violation identification, fault comparison, proportion determination, legal basis matching), and final report generation. It includes guardrails ensuring legal accuracy, cautious judgment, mandatory disclaimers, and avoidance of absolute predictions. References are loaded on-demand from supplementary files for deeper analysis.

Works with✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/ThomasMoreAI/legal-skills-open/tree/HEAD/cn/personal-injury/skills/traffic-accident-assessor

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Traffic Accident Liability Assessment Professional Skill

Overview

This skill provides professional traffic accident liability assessment services based on the Road Traffic Safety Law of the People's Republic of China and supporting regulations and judicial interpretations. It supports accident description analysis, photo-assisted identification and judgment, legal citation, and professional liability allocation output.

Directory Structure

traffic-accident-assessor/
├── SKILL.md                      # Skill definition file (this file)
├── LICENSE                       # License
├── references/                   # Reference materials
│   ├── traffic-laws.md           # Core provisions of the Road Traffic Safety Law
│   ├── liability-rules.md        # Liability determination rule system
│   └── accident-types.md         # Common accident type determination guide
└── evals/                        # Test cases
    └── evals.json                # Evaluation test set

Trigger Conditions

Automatic trigger:

  • User describes an accident incident and asks about liability division
  • User uploads accident scene photos for analysis
  • User asks about traffic law provisions and applicability
  • User needs compensation or legal advice related to traffic accidents
  • Consultation involving vehicles, pedestrians, or non-motor vehicles in road traffic accidents

Manual trigger:

  • User enters /traffic, /accident, /accident-assessment commands

Core Workflow

Step One: Information Collection and Structuring

When users provide accident information, extract and complete the following structure:

Mandatory Information Checklist

Information CategorySpecific FieldsImportance
Time InformationIncident date, specific period (day/night/dusk), weather conditionsMandatory
Location InformationRoad type (urban road/highway/rural road/intersection, etc.), number of lanes, presence of barriersMandatory
Party InformationVehicle A type (motor vehicle/non-motor vehicle), Vehicle B/person type, travel direction of each partyMandatory
Behavior InformationSpecific actions at the time (speed, lane change, turning, overtaking, red light running, etc.)Core
Environmental InformationTraffic signs, markings, signal light status, road surface conditions, visibilityImportant
Consequence InformationCasualties, extent of property damageAuxiliary

Handling Insufficient Information:

  • If the user's description lacks key information, proactively ask follow-up questions to complete it
  • For vague descriptions (e.g., "driving very fast"), guide the user to provide more specific details
  • Clearly inform the user which missing information may affect judgment accuracy

Step Two: Photo Analysis and Key Information Extraction

When users upload accident scene photos, perform the following analysis process:

Image Recognition Checklist

Photo analysis process:
1. Confirm photo clarity and shooting angle
2. Identify the following key elements:
   ☐ Vehicle position relationship (relative position, distance)
   ☐ Collision mark position (front/rear/side, height)
   ☐ Pavement markings (lane lines, stop lines, crosswalk lines)
   ☐ Traffic signs (speed limit, no-entry, yield, stop signs)
   ☐ Signal light status (if any)
   ☐ Skid mark length and direction
   ☐ Debris distribution range
   ☐ Road environment (intersection shape, line-of-sight obstructions, etc.)
3. Synthesize multiple photos to reconstruct the accident scene situation map
4. Annotate the potential impact of each element on liability determination

Notes:

  • A single photo may not fully present the accident scene; encourage users to provide photos from multiple angles when possible
  • Night photos require special attention to lighting conditions and visibility
  • If photo quality is insufficient to support judgment, clearly state limitations
  • Image analysis results serve as auxiliary references, not a substitute for on-site investigation conclusions

Step Three: Liability Determination Analysis

Based on collected information, analyze using the following determination framework:

Liability Determination Hierarchy Framework

First Layer: Violation Identification
    ↓ Compare each party's behavior with legal provisions one by one
Second Layer: Fault Severity Comparison
    ↓ Analyze the dangerousness and causal relationship of each violation
Third Layer: Liability Proportion Determination
    ↓ Comprehensive assessment based on all factors
Fourth Layer: Legal Basis Matching
    ↓ Precise to specific article numbers

Common Violations and Corresponding Legal Provisions Quick Reference

ViolationMain Legal BasisTypical Liability Tendency
Red light runningLaw Articles 38, 44Primary or higher liability
Driving against trafficLaw Article 35Full or primary liability
SpeedingLaw Articles 42, 67Determined by circumstances
Illegal lane changeLaw Article 45Primary or equal liability
Failure to yieldLaw Articles 47, 52Primary or higher liability
Drunk/drug drivingLaw Article 22, Paragraph 2Aggravated liability
Driving without a licenseLaw Article 19Increased liability if causally linked
Drowsy drivingLaw Article 22, Paragraph 2Determined by fatigue level
Failure to maintain safe distanceLaw Article 43Rear vehicle primary or equal liability
Illegal parkingLaw Article 56Determined by traffic obstruction
Pedestrian illegal crossingLaw Articles 62, 76Reduces motor vehicle liability
Non-motor vehicle in motor laneLaw Article 57Bears corresponding liability

Liability Classification Standard Reference

Liability LevelProportion RangeCriteria
Full liability100%One party has violation, other has no fault
Primary liability70%-90%One party's fault significantly greater than the other
Equal liability50%-50%Both parties have similar fault severity
Secondary liability10%-30%One party's fault is minor
No liability0%That party has no violation or fault

Note: Actual liability proportions are determined by traffic police based on the Procedures for Handling Road Traffic Accidents. This skill provides a professional reference opinion.

Step Four: Precise Legal Basis Citation

Each liability judgment conclusion must be accompanied by clear legal basis, formatted as follows:

Citation Format Specification:

【Legal Basis】
- Article XX, Paragraph X of the Road Traffic Safety Law of the People's Republic of China: [Specific text]
- Article XX of the Regulation on the Implementation of the Road Traffic Safety Law of the People's Republic of China: [Specific text]
- Article XX of the Procedures for Handling Road Traffic Accidents: [Specific text] (if applicable)
- Relevant judicial interpretations: (if applicable)

Core Regulatory Document Priority:

  1. Road Traffic Safety Law of the People's Republic of China (2021 amendment) — Highest hierarchy
  2. Regulation on the Implementation of the Road Traffic Safety Law of the People's Republic of China (2017 revision) — Supporting details
  3. Procedures for Handling Road Traffic Accidents (2020 amendment) — Procedural norms
  4. Local regulations — Supplementary application (specify region)

Step Five: Output Professional Assessment Report

Use the following standard template to output a complete assessment report:


Report Output Template

# Traffic Accident Liability Assessment Report

## 1. Basic Information

| Item | Content |
|------|---------|
| Assessment ID | [Auto-generated] |
| Assessment Date | [Current Date] |
| Accident Type | [Classification: motor vehicle vs motor vehicle/motor vehicle vs non-motor vehicle/motor vehicle vs pedestrian, etc.] |
| Accident Location | [Fill based on description] |
| Occurrence Time | [Fill based on description] |
| Weather Conditions | [Fill based on description] |

## 2. Accident Overview

[Recount the accident concisely and objectively, without subjective judgments]

## 3. Party Behavior Analysis

### Party A ([Party A description])

| Analysis Dimension | Specific Situation |
|------------------|-------------------|
| Behavior Description | [Specific actions during the accident] |
| Whether Violation Exists | [Yes/No, specify] |
| Violated Provisions | [List specific articles] |
| Fault Severity Assessment | [High/Medium/Low, explain rationale] |

### Party B ([Party B description])

[Same format as above]

*[If more parties exist, list them sequentially]*

## 4. Photo Analysis Results (If available)

### Key Findings

1. **[Finding 1]**:[Detailed description and its significance for determination]
2. **[Finding 2]**:[Detailed description and its significance for determination]
...

### Scene Reconstruction

[Text description or ASCII diagram]

## 5. Liability Determination Conclusion

### Comprehensive Determination

| Party | Liability Level | Liability Proportion | Basis Summary |
|------|----------------|---------------------|--------------|
| Party A | [Level] | [XX%] | [Core reason] |
| Party B | [Level] | [XX%] | [Core reason] |

### Determination Reasoning Process

1. **Step One - Violation Identification**:
   - Party A: [List]
   - Party B: [List]

2. **Step Two - Causal Relationship Analysis**:
   - [Analyze the strength of the causal link between each violation and the accident]

3. **Step Three - Fault Comparison**:
   - [Compare the severity of each party's faults]

4. **Step Four - Comprehensive Assessment**:
   - [Complete logical chain leading to the final liability division]

## 6. Detailed Legal Basis

### Substantive Law Basis

**1. Road Traffic Safety Law of the People's Republic of China**

- **Article XX** [Article Title]:
  > [Original citation]
  > *Application note: [Explain how this article applies to the case]*

- **Article XX** [Article Title]:
  > [Original citation]
  > *Application note: [Explain how this article applies to the case]*

**2. Regulation on the Implementation of the Road Traffic Safety Law of the People's Republic of China**

- **Article XX** [Article Title]:
  > [Original citation]

### Procedural Law Basis (If applicable)

**3. Procedures for Handling Road Traffic Accidents**

- **Article XX** [Article Title]:
  > [Original citation]

## 7. Legal Advice

### Advice for Party A
1. [Advice 1]
2. [Advice 2]

### Advice for Party B
1. [Advice 1]
2. [Advice 2]

### Follow-up Procedure Suggestions
1. [Procedure suggestion]
2. [Procedure suggestion]

## 8. Disclaimer

> ⚠️ **Important Note**: This assessment report is generated by an AI system based on user-provided information and is for reference only.
>
> - This report cannot replace an official Road Traffic Accident Determination issued by the public security traffic management department
> - The final liability determination shall be based on the official investigation conclusion of the traffic police department
> - If personal injury or significant property damage is involved, it is recommended to retain a professional lawyer promptly
> - The legal provisions cited in this report are publicly available regulatory content, but specific application requires consideration of all case facts
>
> Generation time: [Timestamp]

---
*End of Report*

Special Scenario Handling Guide

Scenario One: Rear-End Collision

Typical Features: Rear vehicle hits the front vehicle's rear

Determination Key Points:

  • Generally, the rear vehicle bears primary or full liability (Law Article 43: Safe distance)
  • Front vehicle behavior must be reviewed for sudden braking, illegal parking, etc.
  • Multi-vehicle chain rear-end collisions require segment-by-segment analysis

Special Exemption Circumstances:

  • Front vehicle suddenly and illegally changes lanes, leaving rear vehicle no time to avoid
  • Front vehicle brake light is malfunctioning and fails to show braking signal
  • Front vehicle illegally parks or reverses on the highway

Scenario Two: Intersection Collision

Typical Features: Two vehicles conflict at an intersection

Determination Key Points:

  • First confirm signal light status (signal color for each party)
  • When no signal light is present, determine based on yield rules (Law Article 52)
  • Application of the right-side vehicle priority principle
  • Priority of vehicles already inside the intersection

Priority Order (High to Low):

  1. Traffic signal lights
  2. Traffic police direction
  3. Traffic signs and markings
  4. Yield rules (slow down and yield, stop and yield)
  5. Right-side priority principle

Scenario Three: Lane Change/Merge Accident

Typical Features: Collision when changing lanes

Determination Key Points:

  • The lane-changing party usually bears primary liability (Law Article 45)
  • Review whether the lane change timing was safe and whether turn signals were activated in advance
  • Assess whether the party being merged into engaged in improper behavior like accelerating to block
  • "Right of way" concept: Vehicles driving normally in their lane have priority

Scenario Four: Motor Vehicle vs Pedestrian Accident

Typical Features: Motor vehicle collides with pedestrian

Determination Key Points:

  • Motor vehicles bear higher duty of care (Law Article 47)
  • Check whether the pedestrian violated traffic signals, jumped over barriers, etc.
  • Motor vehicles must yield in crosswalk areas (Law Article 47, Paragraph 1)
  • Even if the pedestrian is at fault, the motor vehicle usually still bears some liability

Liability Reduction Conditions (Law Article 76):

  • If the pedestrian intentionally causes the accident, the motor vehicle bears no liability
  • If the pedestrian is grossly negligent, the motor vehicle's liability may be reduced

Scenario Five: Motor Vehicle vs Non-Motor Vehicle Accident

Typical Features: Motor vehicle collides with bicycle/electric bike, etc.

Determination Key Points:

  • Whether the non-motor vehicle is traveling within the non-motor vehicle lane
  • Whether the non-motor vehicle is carrying passengers, going against traffic, running red lights, etc.
  • Motor vehicles on mixed roads must exercise a higher duty of care
  • Electric bikes must be distinguished based on whether they meet the new national standard (whether classified as motor vehicle)

Scenario Six: Drunk/Intoxicated Driving Accidents

Determination Key Points:

  • Drunk driving itself is a serious violation (Law Article 22, Paragraph 2)
  • A causal relationship must be established between drunk driving and the accident
  • Intoxicated driving also violates Criminal Law Article 133-1 (Dangerous Driving)
  • Even if the other party is also at fault, the drunk driving party's liability is usually not waived

Core Legal Provisions Index

The following are the most frequently used core provisions. For full details, refer to references/traffic-laws.md:

Core Provisions of the Road Traffic Safety Law

ArticleCore ContentRelevance to Determination
Article 8Vehicle registration system★★☆
Article 19Driver's license management★★★
Article 22Safe driving duty★★★
Article 35Prohibition of driving against traffic★★★
Article 38Traffic signal passage★★★
Article 42Speed limit regulations★★★
Article 43Safe distance/overtaking rules★★★
Article 44Driving in separate lanes★★★
Article 45Lane changing★★★
Article 47Duty to yield★★★
Article 51Seat belts/helmets★★☆
Article 56Parking regulations★★☆
Article 61Pedestrian passage rules★★★
Article 62Pedestrian prohibited acts★★★
Article 70Accident scene handling★★☆
Article 73Traffic accident determination★★★
Article 76Motor vehicle exemption/liability reduction★★★

Guardrails

Principles That Must Be Followed

  1. Legal Basis Authenticity: All cited legal provisions must be existing and currently effective regulations; do not fabricate or alter legal text
  2. Liability Determination Prudence: For complex or borderline cases, provide multiple possible analyses rather than arbitrary conclusions
  3. Information Completeness Statement: When user-provided information is insufficient for accurate judgment, explicitly point out information gaps
  4. Disclaimer Must Not Be Omitted: Each output assessment report must include a complete disclaimer section
  5. Do Not Replace Law Enforcement: Always emphasize that this assessment is for reference only; final determination authority lies with the traffic police

Prohibited Actions

  • Do not provide definitive predictions like "you will definitely win/lose"
  • Do not fabricate legal provisions or judicial interpretations that do not exist
  • Do not ignore obvious violations without analysis
  • Do not force a specific liability proportion number without sufficient information
  • Do not provide specific compensation amount calculations (due to large regional standard variations)

Uncertainty Handling

When encountering the following situations, mark "Uncertain" in the report and explain the reason:

  • Contradictory accident details
  • Controversial space in legal application
  • Differences between local regulations and higher-level laws
  • Lack of key evidence (e.g., no surveillance, no witnesses)
  • Legal qualification of new types of vehicles (e.g., shared bikes, electric scooters)

Reference Loading Guide

For in-depth analysis scenarios, load the following references as needed:

  • references/traffic-laws.md: Contains key excerpts and interpretations of the full Road Traffic Safety Law
  • references/liability-rules.md: Contains detailed liability determination rule matrix and typical case comparisons
  • references/accident-types.md: Contains standardized analysis processes for various common accident types

Loading Strategy:

  • Simple inquiry → Use only built-in knowledge from SKILL.md
  • Complex case analysis → Load liability-rules.md for auxiliary determination
  • Need precise legal citation → Load traffic-laws.md for complete provisions
  • Special accident types → Load accident-types.md for specialized analysis guide

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

ThomasMoreAI/legal-skills-open

Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.

ThomasMoreAI/legal-skills-open

When the user's message starts with "Canada" (case-insensitive), generate a full Ontario PI Case Assessment Memo from the case_stressor corpus and return it verbatim. This is the primary handler for Canadian fact patterns — DO NOT ask clarifying questions first; run the memo and let the lawyer react.

ThomasMoreAI/legal-skills-open

Für Anmeldestrategie & Markenportfolio für Luxus-Modehäuser: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Verhandlungs- oder Eskalationslinie.

ThomasMoreAI/legal-skills-open

Audit an intellectual-property portfolio for ownership, protection, scope, deadlines, territorial coverage, use, value, encumbrances, and enforcement risk. Use for diligence, integration, financing, governance, renewal planning, product launches, or recurring portfolio reviews.

ThomasMoreAI/legal-skills-open

Use whenever the user asks about a motor-vehicle statute, citation, contributing factor, OR a Canadian personal-injury fact pattern — always query Specter's Harvester API before answering. The API auto-routes between two collections (US statutes + Canadian PI case law).

ThomasMoreAI/legal-skills-open

Assesses product liability exposure on given facts — classifying the defect as manufacturing, design, or warning/instruction, mapping which party in the supply chain is potentially exposed, and grading the realistic exposure. Use this whenever a user wants product liability worked through rather than a general deficiency test — including phrasings like "what's our exposure if this product injured someone", "is this a design defect or a manufacturing defect", "who in the supply chain is on the hook here", "assess our product liability risk on these facts", or "how exposed are we if the warning label was inadequate". Distinct from deficiency-analyst, which tests service and trade-practice thresholds — this is specific to defective products and supply-chain exposure. Fires for any product liability question, in any jurisdiction, for manufacturers, assemblers, sellers, distributors, or importers.

ThomasMoreAI/legal-skills-open

Dubletten und Serienforderungen in Insolvenzanmeldungen erkennen: Anwendungsfall mehrere Gläubiger melden gleichartige oder identische Forderungen an; Inkassounternehmen und Originalgläubiger reichen parallel ein. § 174 InsO Forderungsanmeldung, § 178 InsO Tabelle Bestreiten. Prüfraster Doppelerfassung gleicher Rechnung, Serienrechnungen mit laufenden Nummern, Konzernforderungen und Vertreterwechsel, mehrfach eingereichte Titel. Output Dublettenprotokoll mit Unterscheidung echte Dublette vs. Serienforderung. Abgrenzung zu Aktenanlage-Batchregister und zu Formalprüfung.

ThomasMoreAI/legal-skills-open

Absonderungsrechte und Drittsicherheiten im Insolvenzplan und StaRUG planfest behandeln und Ausfallwerte bestimmen. §§ 49 50 51 224 InsO §§ 2 Abs. 4 StaRUG Drittsicherheiten. Prüfraster: Sicherheitenregister Eingriffsbeschreibung Ausfallwertrechnung gruppeninterne Drittsicherheiten Finanzsicherheiten Eingriffsstopper. Output: Sicherheitenregister Ausfallwertrechnung Drittsicherheitenmodul. Abgrenzung: nicht für allgemeine Gruppenbildung.

ThomasMoreAI/legal-skills-open

Absonderungsrechte und Drittsicherheiten im Insolvenzplan und StaRUG planfest behandeln und Ausfallwerte bestimmen. §§ 49 50 51 224 InsO Absonderung § 2 Abs. 4 StaRUG Drittsicherheiten. Prüfraster: Sicherheitenregister Eingriffsbeschreibung Ausfallwertrechnung Finanzsicherheiten unzulässige Eingriffe. Output: Sicherheitenregister Ausfallwertrechnung Drittsicherheitenmodul. Abgrenzung: nicht für allgemeine Gruppenbildung.

ThomasMoreAI/legal-skills-open

Schnittstelle Zwangsverwaltung und Insolvenz bei Insolvenz des Schuldners. Anwendungsfall Schuldner wird insolvent waehrend Zwangsverwaltung laeuft und Verwalter muss Koordination mit Insolvenzverwalter klaeren. Normen § 165 InsO Absonderungsrecht § 49 InsO Grundpfandgläubiger § 155 ZVG Einnahmen. Prüfraster Insolvenzeroeffnung Absonderung Verwalterkommunikation Forderungsanmeldung Verteilungsauswirkungen. Output Koordinationsprotokoll mit Absonderungsnachweis Forderungsanmeldungsunterlagen und Abstimmungsprotokoll Insolvenzverwalter. Abgrenzung zu zvg-verteilungsplan-155 und zvg-rechnungslegung.

ThomasMoreAI/legal-skills-open

KI-VO Hochrisiko-Anforderungen für Personalwesen in Kanzleien ab August 2026: Anwendungsfall Kanzlei setzt KI im HR-Bereich ein oder beraet Mandanten zum AGG-konformen KI-Einsatz bei Bewerberauswahl. Anhang III Nr. 4 KI-VO Hochrisiko Bewerberauswahl, Inkrafttreten 2. August 2026, AGG Diskriminierungsverbot. Prüfraster Hochrisiko-Klassifizierung eigener HR-KI, Konformitätsbewertung, Transparenzpflichten für Betroffene, Beratungsmandate Arbeitsrecht. Output Checkliste Hochrisiko-Anforderungen mit Umsetzungsplan für August 2026. Abgrenzung zu Bias-und-Diskriminierung-Prüfung und zu KI-VO-Betreiber-Pflichten.

ThomasMoreAI/legal-skills-open

Für /tabellenreview-3d:vorlage-arbeitsvertrag-portfolio: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.

ThomasMoreAI/legal-skills-open

Big-Law Billing Narratives und Abrechnung für M&A-Mandate erstellen: Anwendungsfall Associate oder Partnerassistenz muss taugliche Time Narratives Phasenbudgets Workstream-Rechnungen Cap- und Success-Fee-Hinweise erstellen. § 3a RVG Stundenhonorar, GoBD Buchungsanforderungen, XRechnung ZUGFeRD. Prüfraster Honorarvereinbarung prüfen, Time Entries nach Phase strukturieren, Cap-Verbrauch ueberwachen, Success-Fee-Bedingungen abgleichen. Output deal-tauffähige Rechnungsnarrative mit Matter-Controlling und GoBD-konformem Buchungsnachweis. Abgrenzung zu E-Rechnung-GoBD für freistehende Abrechnung.

ThomasMoreAI/legal-skills-open

Zeiterfassung mit abrechenbaren Narrativen für Kanzlei-Mandate. Anwendungsfall Anwalt hat Tätigkeit ausgeubt und will Zeit mit praezisem Narrativ erfassen für spaetere Rechnungsstellung. Normen § 10 RVG Pflichtangaben Narrative GoBD-Zeitstempel. Prüfraster Akte Dauer Takt 6-Minuten-Bloecke Bearbeiter Tätigkeit Honorargrundlage Abrechenbarkeit Datenschutzreduktion. Output Zeiterfassungsprotokoll mit Narrativ Abrechenbarkeit und Rechnungsvorbereitungsnotiz. Abgrenzung zu timesheet-aktenzeitung (Gesamtzeittabelle) und kanzlei-allgemein-rechnung.

ThomasMoreAI/legal-skills-open

Kanzlei erstellt Rechnung für M&A-Mandat und braucht praezise zeitgerechte Leistungsbeschreibungen: Time Narratives Phasenbudgets Workstream-Rechnungen Cap/Success-Fee-Berechnung. Normen RVG §§ 1 ff. BRAO § 49b AO-Steuerrecht. Prüfraster Workstream-Zeiterfassung Phasenzuordnung Korrektur Mandantsfreigabe. Output Narratives-Dokument Workstream-Abrechnung Rechnungsentwurf. Abgrenzung zu mittelstand-ma-erechnung-gobd (GoBD/XRechnung-Format).

ThomasMoreAI/legal-skills-open

Unternehmen oder Kanzlei muss IP-Portfolio verwalten und anstehende Fristen im Blick behalten. Schutzrechtsportfolio-Verwaltung. Prüfraster: Eintragungen Verlaengerungen Jahresgebühren Benutzungsnachweise Fristkalender. Output: Fristenkalender und Portfolio-Audit mit Luecken Verfall und Benutzungsfragen. Abgrenzung zu schutzschrift-eilverfuegung (Verletzungsverteidigung) und markenanmeldung-dpma.

ThomasMoreAI/legal-skills-open

Für Prozessportfolio-Status: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.

ThomasMoreAI/legal-skills-open

Workflow-Skill zu aufklaerungsfehler beweisstrategie. Nutzt Normtext, Nutzerangaben und verifizierte Quellen; Rechtsprechung nur nach Live-Pruefung mit Gericht, Datum und Aktenzeichen.

ThomasMoreAI/legal-skills-open

Strukturierte Prüfung von Ansprüchen wegen Behandlungsfehler nach §§ 630a ff. BGB iVm § 823 BGB. Behandlungsvertrag Aufklärungspflicht § 630e BGB Dokumentationspflicht § 630f BGB Beweislastregeln § 630h BGB grober Behandlungsfehler Beweislastumkehr voll beherrschbares Risiko Anfaengerstandard Schmerzensgeld § 253 BGB. Schlichtungsstelle Aerztekammer MDK-Gutachten. Verjährung drei Jahre § 195 BGB Hoechstfrist dreissig Jahre § 199 Abs. 2 BGB.

ThomasMoreAI/legal-skills-open

Use when a matter involves marriage, divorce, property division, custody, or inheritance for non-Muslim residents of the UAE under Federal Decree-Law 41/2022 (the UAE Civil Personal Status Law) or the DIFC Wills Service Centre. Covers no-fault divorce, joint-custody default, equal-property division, testamentary freedom for non-Muslims, pre-nuptial agreement enforceability, and the parallel DIFC/ADGM wills regimes. Contrasts with the UAE Personal Status Law 28/2005 (Sharia-based) which governs Muslim residents. Triggers on non-Muslim divorce UAE, UAE civil marriage, DIFC wills, UAE prenup, or expat family law UAE questions.

Related Skills