Structured Element Extraction logo

Structured Element Extraction

Community
THUYRan
structured-element-extraction

When the AI agent must systematically analyze a legal question, case facts, legal provision, or legal relationship, it must first decompose it into a structured element checklist. Trigger this skill when: - A description of case facts is received and all legal elements must be extracted before analysis - Determining whether a legal relationship is established (e.g., contract formation, tort composition, crime composition) - Comparing similarities and differences among two or more legal facts or provisions - As a pre-quality gate before downstream tasks such as legal reasoning, application of law, or legal advice - The user expressly asks to "list elements," "analyze item by item," or "check for omissions" Core goal: ensure element extraction is complete and without omission, forming a traceable, verifiable structured checklist before allowing the next stage of reasoning. It is the "quality gate" in the legal analysis chain.

Overview

PublisherTHUYRan
RepositoryLegal-Skills-Chinese
Skill namestructured-element-extraction
Stars
876
Forks
97
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by THUYRan on GitHub. Read the source before you install it.

Installation

Install the Structured Element Extraction AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/THUYRan/Legal-Skills-Chinese/tree/main/English/skills/structured-element-extraction
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/THUYRan/Legal-Skills-Chinese.git /tmp/Legal-Skills-Chinese
mkdir -p .claude/skills
cp -r /tmp/Legal-Skills-Chinese/English/skills/structured-element-extraction .claude/skills/structured-element-extraction
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Structured Element Extraction in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Structured Element Extraction on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Structured Element Extraction is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Chinese source (authoritative): ../../skills/structured-element-extraction/SKILL.md

07 Structured Element Checklist

I. Overview Table

ItemContent
Capability nameStructured Element Checklist
Capability typePre-analysis / Quality gate
Core functionDecompose a legal question into a complete, mutually exclusive, verifiable element checklist
Upstream inputCase facts, legal provisions, user questions, contract text, and other raw materials
Downstream outputVerified structured element checklist for legal reasoning, application of law, risk assessment, etc.
Key principlesCompleteness first (prefer over-listing to omission); exhaust then prune; status-label each item
Quality standardEnter the next stage only after passing the "triple completeness check"

II. Legal Disclaimer

Important: This skill file is an operational guide for an AI agent and does not constitute legal advice. Extraction of a structured element checklist depends on accurate understanding of the constituent elements of the relevant legal field. In actual legal services, the checklist should be reviewed and confirmed by a licensed legal professional. When outputting an element checklist, the AI agent should clearly label confidence and prompt the user to manually review key elements.

III. Core Concepts

3.1 What Are "Structured Elements"

Structured elements are the result of breaking a legal question into minimal decidable units. Each element should satisfy:

  • Atomicity: Cannot be further meaningfully subdivided
  • Decidability: Can receive a clear judgment of "satisfied / not satisfied / to be verified"
  • Independence: Elements do not logically contain one another (MECE)
  • Traceability: Each element can be traced to a specific legal provision or doctrinal basis

3.2 Three Sources of Elements

Source typeExplanationExample
Statutory elementsConstituent requirements expressly provided in lawFour elements of tort under Civil Code Art. 1165
Judicial-interpretation elementsRefinement or supplementation of statutory elements in judicial interpretationsSPC standards for recognizing "经营场所" (business premises)
Doctrinal / practice elementsJudgment standards formed in prevailing doctrine or adjudicative practiceFactors for judging "substantial modification" of a contract

3.3 Element Status Labeling System

Each extracted element must be labeled with one of the following statuses:

StatusSymbolMeaning
Satisfied✅Existing materials sufficiently prove the element
Not satisfied❌Existing materials clearly show the element is not established
To be verified⚠️Existing materials insufficient to judge; information needed
Not applicable➖The element need not be examined on these facts
Disputed🔶Whether the element is satisfied admits different interpretations

3.4 MECE in Legal Element Extraction

MECE = Mutually Exclusive, Collectively Exhaustive

  • Mutually exclusive: No containment or overlap between any two elements at the same level
  • Collectively exhaustive: Together, the elements cover all judgment dimensions of the legal question

Typical MECE violations:

  • Listing "fault" and "intent" as same-level elements (containment)
  • Omitting "causation" (not exhaustive)
  • Mixing "questions of fact" and "questions of law" at the same level (inconsistent classification)

IV. Complete Workflow

Phase 1: Identify Problem Type and Fix the Element Framework

Step 1.1 → Identify the type of legal question
         ├── Contract disputes (formation, validity, performance, breach, termination)
         ├── Tort liability (general tort, special tort, product liability, etc.)
         ├── Crime composition (four-element / three-stratum systems)
         ├── Administrative acts (five elements of legality review)
         ├── Procedural matters (jurisdiction, limitation, standing)
         └── Other types (by specific field)

Step 1.2 → Retrieve the corresponding standard element framework
         - Prefer statutory constituent elements
         - If statutory elements unclear, refer to judicial interpretations
         - If neither is clear, refer to prevailing doctrine

Step 1.3 → Confirm hierarchical structure of the framework
         - Level-1 elements: statutory constituent elements (must all be covered)
         - Level-2 elements: refinements of level-1 elements
         - Level-3 elements: concrete factual judgment points (optional, by complexity)

Phase 2: Extract and Fill Elements Item by Item

Step 2.1 → Against the framework, extract corresponding facts from raw materials
         - Extract each element independently; do not skip
         - Quote key sentences from raw materials directly
         - Mark unextractable elements as "to be verified"

Step 2.2 → Label status for each element (✅/❌/⚠️/➖/🔶)

Step 2.3 → Record evidence / basis source for each element
         - Fact elements: which part of which material
         - Legal elements: corresponding article numbers

Phase 3: Completeness Check (Triple Check)

First check: Framework completeness
  → Ask: Any level-1 element in the standard framework omitted?
  → Method: Compare extraction result with the standard framework item by item
  → If omitted: Supplement and label status

Second check: Fact coverage
  → Ask: Are there important facts in the raw materials not yet "digested" by any element?
  → Method: Re-read raw materials; mark uncited fact fragments
  → If omitted: Assign to an element, or add a new element if needed

Third check: Logical coherence
  → Ask: Are there logical contradictions among elements?
  → Method: Check logical relations (e.g., consistency of causation and damage elements)
  → If contradiction: Label conflict points and note need for further analysis

Phase 4: Output and Handoff

Step 4.1 → Output structured element checklist per standard template
Step 4.2 → Attach completeness declaration (passed / failed triple check)
Step 4.3 → Label overall confidence
Step 4.4 → List items to be verified (if any)
Step 4.5 → Confirm ready for next stage / need more information before continuing

V. Common Fields and Legal Sources

5.1 Contract Dispute Element Framework

Level-1 elementLegal sourceLevel-2 elements
Proper contractual partiesCivil Code Art. 143Capacity for civil acts, agency authority, subject qualification
Genuine expression of intentCivil Code Art. 143No fraud, duress, major misunderstanding, or obvious unfairness
Lawful contentCivil Code Arts. 143, 153No violation of mandatory provisions; no breach of public order and good morals
Contract formationCivil Code Arts. 471–495Offer, acceptance, meeting of minds, form requirements
Contract performanceCivil Code Arts. 509–534Performing party, content, manner, time, place
Breach factsCivil Code Art. 577Non-performance, incomplete performance, delayed performance, defective performance
Breach remediesCivil Code Arts. 577–594Specific performance, remedial measures, damages, liquidated damages
ExemptionsCivil Code Art. 590 etc.Force majeure, exemption clauses, counterparty fault

5.2 General Tort Liability Element Framework

Level-1 elementLegal sourceLevel-2 elements
Injurious actCivil Code Art. 1165Act / omission; unlawfulness of conduct
DamageCivil Code Art. 1165Personal, property, mental harm; certainty of damage
CausationCivil Code Art. 1165Factual causation (condition theory); legal causation (adequate causation)
Subjective faultCivil Code Art. 1165Intent / negligence; degree of fault; standard of care

5.3 Crime Composition Framework (Four-Element System)

Level-1 elementLevel-2 elements
Object of the crimeDirect object, indirect object, object of the act
Objective aspectHarmful act, harmful result, causation, time/place/method (for specific crimes)
SubjectAge of criminal responsibility, capacity, special identity
Subjective aspectIntent (direct/indirect), negligence (carelessness/overconfidence), purpose, motive

5.4 Administrative-Act Legality Review Framework

Level-1 elementLegal sourceExplanation
Authority basisAdministrative Litigation Law Art. 70Whether there is statutory authority
Fact-findingAdministrative Litigation Law Art. 70Whether primary evidence is sufficient
Application of lawAdministrative Litigation Law Art. 70Whether laws and regulations are correctly applied
Procedural legalityAdministrative Litigation Law Art. 70Whether statutory procedure is followed
Reasonable discretionAdministrative Litigation Law Art. 70Abuse of power or manifest inappropriateness

5.5 Labor Dispute Element Framework

Level-1 elementLegal sourceLevel-2 elements
Establishment of labor relationshipMOLSS Fa [2005] No. 12Proper parties; personal, economic, and organizational subordination
Facts of employmentLabor Contract Law Art. 7Actual start date, work content, work location
Written contractLabor Contract Law Art. 10Whether signed, signing time, term, mandatory clauses
Wages and remunerationLabor Contract Law Art. 30Wage standard, payment method, cycle, whether below minimum wage
TerminationLabor Contract Law Arts. 36–50Type of termination, grounds, procedure, economic compensation

VI. Verification and Screening Rules

6.1 Five Verification Rules for Element Extraction

Rule IDNameContentConsequence of failure
V-01Legal-source anchoringEach level-1 element must have a clear statutory or doctrinal basisMay not serve as analysis basis; must reconfirm
V-02Atomicity testLowest-level elements cannot be further meaningfully subdividedContinue subdividing to atomic level
V-03MECE testSame-level elements: no overlap, no omissionAdjust element structure
V-04Status labelingEach element must have exactly one status labelSupplement labels before continuing
V-05Source tracingEach "satisfied" element must cite a fact sourceDowngrade to "to be verified"

6.2 Priority Rules for Element Screening

When raw materials are insufficient, proceed by priority:

  1. Must elements: Every statutory constituent element — must be listed even if marked "to be verified"
  2. Should elements: Elements affecting severity of legal consequences — should be listed
  3. May elements: Auxiliary but not essential — may be listed
  4. Exclude elements: Irrelevant to the case — do not list, but briefly record exclusion reasons

VII. Output Format Templates

Template A: Standard Element Checklist

markdown
## Structured Element Checklist

**Legal question:** [brief description]
**Question type:** [contract / tort / crime composition / administrative act / other]
**Applicable framework:** [framework name and legal source]
**Extraction date:** [YYYY-MM-DD]

### Element Checklist

| No. | Level | Element name | Status | Fact summary | Source / basis | Notes |
|------|------|----------|------|----------|-----------|------|
| 1 | L1 | [Level-1 element 1] | ✅/❌/⚠️/➖/🔶 | [corresponding facts] | [article] | [notes] |
| 1.1 | L2 | [Level-2 element 1.1] | ✅/❌/⚠️/➖/🔶 | [corresponding facts] | [article] | [notes] |
| ... | ... | ... | ... | ... | ... | ... |

### Completeness Check Results

| Check item | Result | Explanation |
|--------|------|------|
| Framework completeness | ✅ Pass / ❌ Fail | [explanation] |
| Fact coverage | ✅ Pass / ❌ Fail | [explanation] |
| Logical coherence | ✅ Pass / ❌ Fail | [explanation] |

### Items to Be Verified

1. [Element X]: Need to supplement [specific information]
2. [Element Y]: Need to confirm [specific issue]

### Overall confidence: [High/Medium/Low] — [brief reason]

### Conclusion: [May enter next stage / Need more information before continuing]

Template B: Concise Element Checklist (Quick Verification)

markdown
## Element Checklist — [brief legal question]

**Framework:** [name] | **Legal source:** [core articles]

- [ ] Element 1: [name] — [status] — [one-sentence note]
- [ ] Element 2: [name] — [status] — [one-sentence note]
- [ ] Element 3: [name] — [status] — [one-sentence note]
- [ ] Element 4: [name] — [status] — [one-sentence note]

**Omission check:** ✅ None / ⚠️ Omissions: [explanation]
**May continue:** ✅ Yes / ❌ No, reason: [explanation]

VIII. Confidence Labeling System

8.1 Single-Element Confidence

ConfidenceStandardLabeling
HighFacts clear + legal source clear + no disputeStatus ✅ or ❌
MediumFacts basically clear but details fuzzy, or legal source admits multiple readingsStatus 🔶
LowFacts unclear or legal source unclearStatus ⚠️

8.2 Overall Checklist Confidence

Overall confidenceCriteria
HighAll level-1 elements ✅ or ❌, no ⚠️, triple check all passed
Medium1–2 ⚠️ or 🔶 elements that do not affect core judgment; triple check basically passed
Low3+ ⚠️ elements, or core element is ⚠️, or triple check failed

8.3 Confidence and Next Actions

Overall confidenceAllowed next action
HighProceed directly to legal reasoning / application of law
MediumMay proceed, but must clearly label uncertainties in the analysis
LowMust not enter next stage; first supplement information or request user confirmation

IX. Common Errors and Prevention

9.1 Fatal Error Table

Error IDNameDescriptionSeverityPrevention
F-01Omitting statutory elementsFailure to list a statutory constituent element⭐⭐⭐⭐⭐ FatalFix complete statutory framework first; compare item by item
F-02Confused element levelsListing level-2 elements alongside level-1⭐⭐⭐⭐ SeriousStrict hierarchy; same level uses same classification standard
F-03Skipping check before outputDelivering without triple completeness check⭐⭐⭐⭐⭐ FatalMake check mandatory; results must appear in output
F-04Missing status labelsElements listed without satisfaction status⭐⭐⭐⭐ SeriousExactly one status per element
F-05Fact–element mismatchAssigning a fact to the wrong element⭐⭐⭐⭐ SeriousAfter extraction, back-check: does this fact prove this element?
F-06Forcing ahead on low confidenceEntering reasoning when overall confidence is "Low"⭐⭐⭐⭐⭐ FatalStrictly follow confidence–action table

9.2 Common Traps

TrapManifestationCorrect approach
Conclusion instead of elementsWriting "constitutes tort" without splitting four elementsSplit into each independent element
Omitting negative elementsFocusing only on "establishment," ignoring exemptions/defensesExemptions and defenses are also necessary elements
Mixing fact and legal evaluationPutting legal conclusions in the fact-summary columnFact summary records objective facts only; legal evaluation goes in notes
Over-splittingSplitting a simple element into a dozen sub-itemsSplit to "independently decidable"; do not pursue extreme granularity
Rigid frameworksApplying one framework to all casesChoose framework by question type
Ignoring time dimensionIgnoring element changes from statutory amendmentsConfirm applicable law version; label time nodes
Omitting procedural elementsFocusing only on substantive elements; ignoring limitation, jurisdictionList procedural elements as a separate group

X. Special Scenario Handling

10.1 Intersecting Legal Relationships

Scenario: Same facts involve multiple legal relationships (e.g., concurrent contract breach and tort)

Handling:

  1. Build an independent element checklist for each legal relationship
  2. Cross-reference shared fact elements between checklists
  3. Explicitly state "This case involves N legal relationships; separate checklists established"
  4. If claim concurrence exists, note the concurrence relationship

10.2 Vague or Blank Law

Scenario: Legal standard for an element is unclear; no direct provision to cite

Handling:

  1. Label legal source as "prevailing doctrine" or "similar-case adjudicative rules"
  2. List at least two reference cases or scholarly views
  3. Mark element confidence as Medium or Low
  4. Note the specific source of uncertainty

10.3 Severely Insufficient Facts

Scenario: User information extremely limited; many elements cannot be judged

Handling:

  1. Still list the complete element framework (do not omit for lack of information)
  2. Mark all undecidable elements as ⚠️
  3. Generate an "information supplementation request list" by priority
  4. Overall confidence Low; expressly state next stage must not begin

10.4 Multiple Time Nodes for Applicable Law

Scenario: Facts span before and after a statutory amendment

Handling:

  1. Fix the time of each fact element
  2. Fix the effective law version for each time point
  3. If different versions apply at different times, build separate checklists
  4. Clearly label the temporal dividing line for applicable law

10.5 Party Dispute Focus Not Fully Aligned with Framework

Scenario: Parties dispute something outside the core elements of the standard framework

Handling:

  1. Still complete full extraction under the standard framework (no omission)
  2. Add a "dispute-focus elements" section for issues actually disputed
  3. Note the relationship between dispute focus and standard elements

XI. Quality Checklist

Before outputting a structured element checklist, the AI agent must complete:

Pre-extraction Checks

  • Legal question type clearly identified
  • Correct element framework selected
  • Applicable law version (time node) confirmed
  • All raw materials read at least once

Extraction Process Checks

  • Every level-1 element listed (no omission)
  • Every element status-labeled (✅/❌/⚠️/➖/🔶)
  • Every "satisfied" element has fact summary and source citation
  • Same-level elements have no overlap (MECE–exclusive)
  • All level-1 elements together cover all judgment dimensions (MECE–exhaustive)
  • Exemptions / defenses and other negative elements considered
  • Procedural elements considered (limitation, jurisdiction, etc., if applicable)

Pre-output Checks

  • Triple completeness check executed and results recorded
  • Overall confidence labeled
  • Items to be verified listed (if any)
  • Explicitly labeled "may enter next stage" or "need more information"
  • Output format matches standard template
  • Fact summaries do not mix in legal conclusions

XII. Complete Examples

Example 1: Simple Scenario — General Tort Element Extraction

Raw materials:

On 15 March 2024, while reversing in a shopping-mall parking lot, Zhang San failed to observe behind and knocked down Li Si who was walking through. Li Si was taken to hospital, diagnosed with a right-leg fracture, hospitalized 20 days, medical expenses RMB 32,000. Traffic police issued an accident determination finding Zhang San fully liable. Li Si lost RMB 15,000 in wages during hospitalization.


Structured Element Checklist

Legal question: Zhang San reversed into Li Si; can Li Si require Zhang San to bear tort damages? Question type: Tort liability (general tort — fault liability) Applicable framework: Four elements of general tort (Civil Code Art. 1165(1)) Extraction date: 2024-03-20

Element Checklist

No.LevelElement nameStatusFact summarySource / basisNotes
1L1Injurious act✅Zhang San knocked down Li Si while reversingCivil Code Art. 1165Injurious act in form of commission
1.1L2Manner of act✅Driving in reverse (commission)——
1.2L2Unlawfulness✅Failed to observe behind; breached safe-driving dutyRoad Traffic Safety Law Art. 22Police found Zhang San fully liable
2L1Damage✅Li Si right-leg fracture; 20 days hospitalizationCivil Code Art. 1165—
2.1L2Personal injury✅Right-leg fractureCivil Code Art. 1179—
2.2L2Property damage✅Medical RMB 32,000 + lost wages RMB 15,000Civil Code Art. 1179Total RMB 47,000
2.3L2Mental harm⚠️Materials do not mention mental harmCivil Code Art. 1183Fracture may support mental damages claim; to verify
3L1Causation✅Reverse collision directly caused fractureCivil Code Art. 1165Factual causation clear; police determination corroborates
3.1L2Factual causation✅Collision was direct cause of fracture—Condition theory: no collision, no fracture
3.2L2Legal causation✅Fracture from reverse collision is ordinarily foreseeable—Adequate causation established
4L1Subjective fault✅Failed to observe behind; negligenceCivil Code Art. 1165Police full liability
4.1L2Type of fault✅Negligence (carelessness)—Ought to have foreseen but did not
4.2L2Degree of fault✅Full fault (police full liability)Accident determination—
5L1Exemptions❌No exemption shownCivil Code Arts. 1174–1177—
5.1L2Victim fault❌Materials do not show Li Si at faultCivil Code Art. 1173Police found Zhang San fully liable
5.2L2Third-party cause❌No third-party intervention shownCivil Code Art. 1175—
5.3L2Force majeure❌NoneCivil Code Art. 180—
5.4L2Self-defense / necessity➖Not involved——
6L1Procedural elements————
6.1L2Limitation✅Accident 15 March 2024; within 3-year limitationCivil Code Art. 188Expires 14 March 2027
6.2L2Jurisdiction⚠️Materials do not name a courtCivil Procedure Law Art. 29Court of place of tort or defendant’s domicile

Completeness Check Results

Check itemResultExplanation
Framework completeness✅ PassFour elements + exemptions + procedural elements covered
Fact coverage✅ PassAll facts in raw materials assigned to elements
Logical coherence✅ PassNo logical contradiction among elements

Items to Be Verified

  1. Mental harm (element 2.3): Confirm whether Li Si claims mental damages; disability rating from fracture
  2. Forum (element 6.2): Confirm place of accident and defendant’s domicile for jurisdiction

Overall confidence: High

Core four elements (injurious act, damage, causation, subjective fault) all "satisfied"; facts clear; legal sources clear. Items to verify do not affect the basic judgment that tort liability is established.

Conclusion: ✅ May enter next stage (application of law and liability determination)


Example 2: Complex Scenario — Labor Relationship Confirmation + Unlawful Termination

Raw materials:

Wang joined a tech company on 1 June 2022 as a software engineer, monthly salary RMB 20,000; the company did not sign a written labor contract. Wang worked at the company office during company hours (9:00–18:00), used company computer and workstation, and accepted project-manager assignments and appraisals. Wages paid monthly by bank transfer.

On 10 August 2023, the company orally told Wang "due to business adjustment, no need to come tomorrow," without stating specific termination grounds, without 30 days’ advance notice, and without any economic compensation. Wang asked for a written termination notice; the company refused.

Wang had no disciplinary record; performance appraisals were all "合格" (合格) or above. The company did not pay social insurance for Wang.

On 1 September 2023 Wang applied to the local labor arbitration commission seeking: (1) confirmation of labor relationship; (2) double-wage differential for failure to sign a written contract; (3) compensation for unlawful termination; (4) make-up of social insurance.


Structured Element Checklist

Legal question: Is there a labor relationship between Wang and the tech company? Was termination unlawful? Can Wang’s claims be supported? Question type: Labor dispute (relationship confirmation + unlawful termination + multiple claims) Applicable framework: Labor-relationship confirmation elements + legality of labor-contract termination Extraction date: 2024-03-20

Note: Multiple legal issues; separate element checklists established.


Checklist 1: Labor Relationship Confirmation

Applicable framework: MOLSS Fa [2005] No. 12, Art. 1

No.LevelElement nameStatusFact summarySource / basisNotes
1L1Proper parties✅—MOLSS Fa [2005] No. 12 Art. 1(1)—
1.1L2Employer qualification✅"A tech company" has employer capacity—Company form to confirm further (LLC / sole prop., etc.)
1.2L2Worker qualification✅Wang natural person, software engineer—Age not stated; presumed statutory working age
2L1Personal subordination✅—MOLSS Fa [2005] No. 12 Art. 1(2)—
2.1L2Observe rules✅Worked company hours (9:00–18:00)—Fixed hours
2.2L2Accept management✅Accepted project-manager assignments and appraisals—Clear managerial hierarchy
2.3L2Designated workplace✅Worked at company office——
3L1Economic subordination✅—MOLSS Fa [2005] No. 12 Art. 1(3)—
3.1L2Remuneration✅RMB 20,000/month by bank transfer—Fixed salary, not project settlement
3.2L2Means of production✅Company provided computer and workstation—Tools provided by employer
4L1Organizational subordination✅Wang’s work part of company businessMOLSS Fa [2005] No. 12 Art. 1(3)Software engineer is core business role for a tech company

Checklist 2: Double Wages for Unsigned Written Contract

Applicable framework: Labor Contract Law Arts. 10, 82; Implementing Regulations Arts. 6, 7

No.LevelElement nameStatusFact summarySource / basisNotes
1L1Labor relationship established✅See Checklist 1—Prerequisite confirmed
2L1No written contract✅"Company did not sign a written labor contract"Labor Contract Law Art. 10—
3L1Beyond statutory signing period✅Hired 1 June 2022 to termination 10 Aug 2023; over one monthLabor Contract Law Art. 82Over one month from start of employment
4L1Double-wage calculation period🔶1 July 2022 to 31 May 2023 (11 months)Labor Contract Law Arts. 82, 14(3)After one year deemed open-ended; double wage max 11 months
5L1Arbitration limitation🔶Arbitration filed 1 Sept 2023Labor Dispute Mediation and Arbitration Law Art. 27Whether double-wage claims subject to 1-year arbitration limitation is disputed; July 2022 portion may be time-barred; depend on local adjudicative practice
6L1Fault for non-signing⚠️Materials do not say whether company failed to offer or Wang refused—Usually employer bears signing duty; different if worker refused

Checklist 3: Unlawful Termination

Applicable framework: Labor Contract Law Arts. 36–43, 48, 87

No.LevelElement nameStatusFact summarySource / basisNotes
1L1Fact of termination✅10 Aug 2023 oral notice "no need to come tomorrow"—Unilateral employer termination
2L1Lawfulness of termination grounds❌Only "business adjustment"; no specific statutory groundLabor Contract Law Arts. 39–41—
2.1L2Fault-based dismissal (Art. 39)❌No disciplinary record; performance合格 or aboveLabor Contract Law Art. 39Fits none
2.2L2Non-fault dismissal (Art. 40)❌No proof of incompetence / major change of objective circumstances, etc.Labor Contract Law Art. 40"Business adjustment" may relate to objective change, but no evidence
2.3L2Economic layoff (Art. 41)⚠️Only oral "business adjustment"; no layoff plan, etc.Labor Contract Law Art. 41Even if layoff, statutory procedure not followed
3L1Lawfulness of termination procedure❌———
3.1L2Advance notice❌No 30 days’ written notice or payment in lieuLabor Contract Law Art. 40—
3.2L2Written form❌Oral notice; refused written termination noticeLabor Contract Law Art. 50—
3.3L2Union procedure⚠️Materials silent on whether union exists / was notifiedLabor Contract Law Art. 43To verify
4L1Economic compensation / damages————
4.1L2Length of service✅1 June 2022 to 10 Aug 2023 ≈ 1 year 2 monthsLabor Contract Law Art. 47Count as 1.5 months (≥6 months <1 year counts as 1 year)
4.2L2Monthly wage standard✅RMB 20,000/monthLabor Contract Law Art. 47Confirm whether includes overtime, bonuses, etc.
4.3L2Unlawful-termination damages✅Twice economic compensation standardLabor Contract Law Art. 872 × 1.5 × 20000 = RMB 60,000
5L1Prohibited-termination situations⚠️Materials silent on medical period, pregnancy, etc.Labor Contract Law Art. 42To verify; if present, further aggravates unlawfulness

Checklist 4: Social Insurance Make-up

No.LevelElement nameStatusFact summarySource / basisNotes
1L1Period of labor relationship✅1 June 2022 to 10 Aug 2023——
2L1Non-payment of social insurance✅"Company did not pay social insurance for Wang"Social Insurance Law Art. 58—
3L1Arbitration acceptance scope🔶Whether social-insurance make-up is within labor arbitration acceptance—Most localities treat make-up as administrative; complain to social-insurance authority; some localities’ arbitration may accept

Completeness Check Results

Check itemResultExplanation
Framework completeness✅ PassFour legal issues each have independent complete checklists
Fact coverage✅ PassAll facts assigned; performance records under Checklist 3 item 2.1
Logical coherence✅ PassChecklists consistent; Checklist 1 conclusions are prerequisites for 2–4

Items to Be Verified (by priority)

  1. [High] Fault for non-signing (Checklist 2–element 6): Confirm whether company failed to offer or Wang refused
  2. [High] Union procedure (Checklist 3–element 3.3): Confirm whether company has a union
  3. [Medium] Prohibited-termination situations (Checklist 3–element 5): Medical period, pregnancy, etc.
  4. [Medium] Double-wage arbitration limitation (Checklist 2–element 5): Local arbitration practice on double-wage limitation
  5. [Medium] Social-insurance make-up acceptance (Checklist 4–element 3): Whether local arbitration accepts make-up claims
  6. [Low] Employer form (Checklist 1–element 1.1): Specific organizational form
  7. [Low] Monthly wage composition (Checklist 3–element 4.2): Whether RMB 20,000 is all remuneration

Overall confidence: Medium

Reasons: Checklist 1 (relationship confirmation) high confidence; all four elements satisfied. Checklist 3 (unlawful termination) core judgment high confidence (grounds and procedure both unlawful). But double-wage limitation and social-insurance acceptance vary by locality and need confirmation. Overall, core claims (confirm relationship + unlawful-termination damages) have a sufficient analytical basis to enter the next stage, with uncertainties labeled.

Conclusion: ✅ May enter next stage (application of law and claim assessment), but keep the 7 items to be verified labeled, and recommend the user supplement high-priority information.

Frequently asked questions

What does the Structured Element Extraction AI skill do?

When the AI agent must systematically analyze a legal question, case facts, legal provision, or legal relationship, it must first decompose it into a structured element checklist. Trigger this skill when: - A description of case facts is received and all legal elements must be extracted before analysis - Determining whether a legal relationship is established (e.g., contract formation, tort composition, crime composition) - Comparing similarities and differences among two or more legal facts or provisions - As a pre-quality gate before downstream tasks such as legal reasoning, application o...

Why use Structured Element Extraction on TypingMind?

Because you install it once and use it with any model. Structured Element Extraction is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Structured Element Extraction in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/THUYRan/Legal-Skills-Chinese/tree/main/English/skills/structured-element-extraction. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Structured Element Extraction?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Structured Element Extraction?

As many as you like. As long as a model supports skills, you can use Structured Element Extraction with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Structured Element Extraction AI skill free?

It is published on GitHub by THUYRan. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇