[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGF7MG0TTYQ7JHXMZDH0XG":3,"skill-same:01M6MGF7MG0TTYQ7JHXMZDH0XG":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6MGF7MG0TTYQ7JHXMZDH0XG","court-rules",null,"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.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ffoklepoint\u002Fcourt-rules-codex-plugin\u002Fskills\u002Fcourt-rules\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"court rules","Rules","court","local","when","limits","source","which","answer","judge","timing","filing","MCP","fees","orders","task","document","motion","use","page","Word","Tools","2026-11-10 10:12:30",false,"---\nname: court-rules\ndescription: 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.\n---\n\n# Court Rules\n\nUse 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.\n\n## Workflow\n\n1. **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.\n2. **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.\n3. **Get the rules.**\n   - 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.\n   - For every rule held for one judge, call `get_judge_rules` with `judge_slug` and `district_id`.\n4. **Court closures.** Call `list_court_holidays` with `district_id` and either `year` or `date_from` and `date_to`.\n5. **Compliance check.** `check_compliance` does not run a check. It returns the request parameters for the REST compliance check (documented at https:\u002F\u002Fdocs.courtrules.app\u002Fapi-reference\u002Fcheck), 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.\n\n## Filter values\n\n- `logic_type`: `CourtesyCopyRule`, `PageWordLimitRule`, `PreMotionConferenceRule`, `AdjournmentRequirementRule`, `BundlingRule`, `FormatConstraint`, `DocumentRequirement`, `CommunicationRule`, `SealingProcedure`, `ElectronicFilingRule`, `FilingTimingRule`, `ServiceRule`, `FilingFeeRule`, `JuniorLawyerIncentive`.\n- `workflow_phase`: `FILING`, `CASE_INITIATION`, `MOTION_PRACTICE`, `TRIAL_PREP`, `POST_JUDGMENT`.\n- Narrow with `district_id`, `judge_slug` or `logic_type` before searching broadly. A search that is too broad is refused.\n\n## How to answer\n\n- Quote or summarize the rule, then give the `source_url` and any page, section or paragraph from the citation fields.\n- Fields the server omits are not stated in the source text. Do not fill them in with defaults, and do not turn a missing field into \"no limit\" or \"not required\".\n- If a search returns nothing, say so and name the court page or document the user should read. Do not answer from memory for a specific court or judge.\n- Rules and holidays change. Tell the user to confirm the cited source before filing. This is reference information, not legal advice.\n- The enforcement tools (`search_enforcement_actions`, `get_enforcement_details`, `get_enforcement_stats`) cover privacy and regulatory enforcement actions. Use them only when the question is about enforcement, not filing rules.\n\n## Sign-in\n\nThe server asks the MCP client to sign in on first use (a browser window opens console.courtrules.app; Google or email). Clients without a browser can send an API key from the same console as an `Authorization: Bearer \u003Capi_key>` header. See https:\u002F\u002Fdocs.courtrules.app\u002Fauthentication.\n","# Court Rules\n\nUse 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.\n\n## Workflow\n\n1. **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.\n2. **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.\n3. **Get the rules.**\n   - 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.\n   - For every rule held for one judge, call `get_judge_rules` with `judge_slug` and `district_id`.\n4. **Court closures.** Call `list_court_holidays` with `district_id` and either `year` or `date_from` and `date_to`.\n5. **Compliance check.** `check_compliance` does not run a check. It returns the request parameters for the REST compliance check (documented at https:\u002F\u002Fdocs.courtrules.app\u002Fapi-reference\u002Fcheck), 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.\n\n## Filter values\n\n- `logic_type`: `CourtesyCopyRule`, `PageWordLimitRule`, `PreMotionConferenceRule`, `AdjournmentRequirementRule`, `BundlingRule`, `FormatConstraint`, `DocumentRequirement`, `CommunicationRule`, `SealingProcedure`, `ElectronicFilingRule`, `FilingTimingRule`, `ServiceRule`, `FilingFeeRule`, `JuniorLawyerIncentive`.\n- `workflow_phase`: `FILING`, `CASE_INITIATION`, `MOTION_PRACTICE`, `TRIAL_PREP`, `POST_JUDGMENT`.\n- Narrow with `district_id`, `judge_slug` or `logic_type` before searching broadly. A search that is too broad is refused.\n\n## How to answer\n\n- Quote or summarize the rule, then give the `source_url` and any page, section or paragraph from the citation fields.\n- Fields the server omits are not stated in the source text. Do not fill them in with defaults, and do not turn a missing field into \"no limit\" or \"not required\".\n- If a search returns nothing, say so and name the court page or document the user should read. Do not answer from memory for a specific court or judge.\n- Rules and holidays change. Tell the user to confirm the cited source before filing. This is reference information, not legal advice.\n- The enforcement tools (`search_enforcement_actions`, `get_enforcement_details`, `get_enforcement_stats`) cover privacy and regulatory enforcement actions. Use them only when the question is about enforcement, not filing rules.\n\n## Sign-in\n\nThe server asks the MCP client to sign in on first use (a browser window opens console.courtrules.app; Google or email). Clients without a browser can send an API key from the same console as an `Authorization: Bearer \u003Capi_key>` header. See https:\u002F\u002Fdocs.courtrules.app\u002Fauthentication.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Ffoklepoint\u002Fcourt-rules-codex-plugin\u002Fskills\u002Fcourt-rules",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill court-rules",{"tool":70,"command":71},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill court-rules",{"tool":73,"command":74},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill court-rules","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ffoklepoint\u002Fcourt-rules-codex-plugin\u002Fskills\u002Fcourt-rules\u002FSKILL.md",true,[],[79,89,97,105,113,121],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":88},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":88},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":88},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":88},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":88},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":88},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]