co-pro-se SKILL.md skillA
co-pro-se from codearranger/claude-legal is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add codearranger/claude-legal/co-pro-se@v0.1.0Pins v0.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- codearranger/claude-legal
- Path
plugins/co-court-docs/skills/co-pro-se/SKILL.md- Versions recorded
- 1
- Latest version
- v0.1.0, committed May 28, 2026
- Size
- 9,250 bytes
- Repository stars
- 23
- License
- a license file GitHub does not identify
This skill should be used when drafting Colorado court documents for a self-represented (pro se) litigant. Triggers include "pro se", "self-represented", "in pro per", "drafting a pro se motion in Colorado", "drafting an answer without a lawyer", "filing without a lawyer in Colorado". Covers the pro-se drafting framework adapted for Colorado civil practice, the C.R.C.P. 5 service rules and CCEFS Pro Se workflow, the JDF (Judicial Department Forms) catalog, the Self-Help Center resources at…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Pro Se Drafting for Colorado > **NOT LEGAL ADVICE.** This skill helps unrepresented parties > prepare paper and procedure. It does not substitute for advice from > a licensed Colorado attorney. Use this skill in addition to `co-statewide-format` whenever the filer is unrepresented. Colorado uses the terms "pro se" and "self-represented" interchangeably; "in pro per" is also accepted but less common. ## The pro-se drafting framework — adapted for Colorado The pro-se drafting framework (from *Parker v. Dist. Court for City & County of Denver*, 173 Colo. 537 (1971), and its successors) sets out the two-track standard Colorado courts use when reviewing pro se filings: 1. **Substantial compliance with form.** Courts construe pro se filings liberally and look past minor formatting errors so long as the substantive components are present (caption, claim or defense, signature, verification when required). 2. **No substantive advocacy from the bench.** The court will not reframe a pro se filer's argument, supply missing elements of a claim, or fill gaps in the record. The practical takeaway: a pro se filing must clearly **name the …
Read the whole file at its exact version.
How to install
mdr add codearranger/claude-legal/co-pro-se@sha256:e2e4b33ad7cf95d2The line at the top of this page pins the label v0.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_btg7vkbcobzbhqgi)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 28, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9250 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
codearranger/claude-legal · 23 stars · license a license file GitHub does not identify · pushed 2026-10-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_btg7vkbcobzbhqgi GET https://markdownregistry.com/api/v1/resolve?ref=codearranger/claude-legal/co-pro-se GET https://markdownregistry.com/api/v1/blob/e2e4b33ad7cf95d2b2070daed771beb9b016ac21ace7c63a5e3c8f57074c85b5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.