skills.rest
strigov
strigovCOMMUNITY
Explore all skills by this author →
GitHub

analyze-hearing

Analyze court hearing transcripts and generate a markdown analysis artifact.

5|Updated Mar 30, 2026
Search Tags:#automation#markdown#transcripts#analyze#case-management#legal-analysis#hearing
One-click install
npx skills add https://github.com/strigov/vassal-litigator --skill analyze-hearing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-hearing
Source: https://github.com/strigov/vassal-litigator/tree/main/skills/analyze-hearing
Command: npx skills add https://github.com/strigov/vassal-litigator --skill analyze-hearing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes court hearing transcripts to extract structured insights and generate a formal analysis artifact, saving time and ensuring consistent documentation.

Core Features & Use Cases

  • Accepts and normalizes hearing transcription text, saving it to the per-hearing directory.
  • Delegates deep legal analysis to Opus-subagent under contract 3.1c.
  • Produces the final artifact at hearings/YYYY-MM-DD/analysis.md (no .docx).

Quick Start

Provide a hearing transcription text to the skill to generate the analysis artifact.

Frequently Asked Questions about analyze-hearing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate court hearing transcript analysis for legal case management?▼

Court hearing transcript analysis is automated by normalizing transcription text and delegating deep legal analysis to an Opus-subagent, generating a structured markdown artifact. This process saves time and ensures consistent legal documentation.

Can I generate a markdown analysis from a hearing transcript without a case context file?▼

No, a valid case context file such as a .vassal/case.yaml is required alongside the hearing transcript to generate the markdown analysis. The skill uses this case context to accurately structure the extracted legal insights.

What is the output format for structured hearing transcript insights?▼

The output format for structured hearing insights is a markdown file saved at hearings/YYYY-MM-DD/analysis.md. It does not generate .docx files, strictly producing a formal markdown analysis artifact.

How does the Opus-subagent contract work for legal transcript analysis?▼

The Opus-subagent contract 3.1c delegates deep legal analysis of normalized hearing transcripts. The skill preserves the original transcripts while the subagent extracts structured insights and outputs the formal markdown analysis artifact.

Are there limitations on exporting hearing analysis artifacts to .docx format?▼

Yes, the hearing analysis artifact is strictly output as markdown at hearings/YYYY-MM-DD/analysis.md and does not support .docx export. You must use a separate conversion tool to convert the generated markdown legal analysis.

Related Skills

Explore More Legal & Compliance Skills→
strigovstrigov
5

add-opponent

Automate intake, classification, labeling, and routing of opponent-provided legal documents.

Community
Intermediate
strigovstrigov
5

legal-review

Analyze legal cases and generate auditable Markdown and DOCX reports.

Community
Advanced
strigovstrigov
5

prepare-hearing

Coordinate red/blue-team notes and motions for hearing preparation.

Community
Advanced
cat-xierluocat-xierluo
557

litigation-analysis

Analyze legal documents to extract facts, evidence, and judicial reasoning.

Community
Advanced