Menu

Individual skill

court-rules

Find U.S. federal and state court filing rules, local rules, judge standing orders and court holidays with the Court Rules MCP tools, and answer with the source document cited. Use when a task asks about page or word limits, courtesy copies, pre-motion conferences, e-filing, service, filing timing or fees, a specific judge's practices, or which days a court is closed.

plugins/foklepoint/court-rules-codex-plugin/skills/court-rules/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Court Rules

Use the `court-rules` MCP server (tools listed below) to answer questions about how to file in a specific court or in front of a specific judge. Every rule the server returns carries the URL of the court's own document. Report that URL with the answer.

## Workflow

1. **Find the court.** Call `list_courts` with `query` set to part of the court name or ID (for example `"eastern district of new york"`, `"edny"`, `"cook"`). Copy the `district_id` from the result (examples: `edny`, `sdny`, `il-cook-circuit`, `ca-los-angeles-superior`). Results come in pages: to read on, call again with `offset` set to the previous `next_offset`; `next_offset` is null on the last page.
2. **Find the judge, if the question names one.** Call `search_judges` with `district_id` and `name` (partial match). Copy the `judge_slug`. Judges who no longer sit are hidden by default because they carry no current rules; set `include_inactive` only when the user asks about a former judge.
3. **Get the rules.**
   - For a topic across a court or a judge, call `search_filing_rules` with `district_id`, and optionally `judge_slug`, `q` (search terms such as `"courtesy copies"` or `"rejected cure"`), `logic_type`, `workflow_phase`, `case_type` and `limit`. Use `judge_slug` `"court"` for court-wide rules. When `judge_slug` is a judge, court-wide rules are included unless `include_court_rules` is false.
   - For every rule held for one judge, call `get_judge_rules` with `judge_slug` and `district_id`.
4. **Court closures.** Call `list_court_holidays` with `district_id` and either `year` or `date_from` and `date_to`.
5. **Compliance check.** `check_compliance` does not run a check. It returns the request parameters for the REST compliance check (documented at https://docs.courtrules.app/api-reference/check), which needs an API key and runs for the Eastern District of New York (`edny`) today. Show the parameters to the user and say that the check itself is a separate API call they make with their own key.