Transcribing legal
Skill cyanxxy/transcription-agent-go/.skills/transcribing-legal
Agentic audio transcription in Go: parallel transcription agents, an LLM judge agent that picks the best, extensible via Agent Skills.
npx -y skills add cyanxxy/transcription-agent-go --skill transcribing-legalAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Transcribes legal proceedings, depositions, and hearings preserving exact wording, legal terminology, and attribution. Use when expected_format is "legal" or the audio is a deposition, court hearing, or legal consultation.
SKILL.md
0.6 KB, 46 tokens by cl100k_base, as published. Nobody here has run it
Legal Transcription Guidance
Preserve exact wording, legal terminology, and attribution without paraphrasing or summarizing. Do not turn the audio into a different document type; keep the output transcript-first and faithful to the spoken content.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most legal skills give in 46 tokens
Counted across 234 of the 234 authors here whose files we hold, read 2026-08-07
- Use text operators for text fieldsin 11 of 234, across 6 files
- Consult qualified counsel before usein 11 of 234, across 3 files
- Use PatentSearch API for patent searchesin 10 of 234, across 5 files
- Confirm jurisdiction, employment type, and required clausesin 9 of 234, across 2 files
- Choose a document template and tailor role-specific termsin 9 of 234, across 2 files
- Validate compensation, benefits, and compliance requirementsin 9 of 234, across 2 files
- Add signature, confidentiality, and IP assignment terms as neededin 9 of 234, across 2 files
- Open the implementation playbook for detailed templatesin 9 of 234, across 2 files
- Use TSDR for trademark data retrievalin 9 of 234, across 4 files
- Ask for clarification if required inputs are missingin 8 of 234, across 2 files
- Set the USPTO_API_KEY environment variablein 8 of 234, across 3 files
- Use the uspto-opendata-python library for PEDSin 8 of 234, across 3 files
Said here and by no other author read
- preserve exact wording
- preserve legal terminology
- preserve attribution
- keep output transcript-first
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.