agentleFS
jurisdictionaljurisdictional/jurisdictional-skill/CLAUDE.md

jurisdictional-skill

CLAUDE.md0 starsChanged 17 days agoMITView on GitHub

Start with PLAN.md. A Claude Code plugin for jurisdictional.org containing the gather skill — a conversational interface for exploring local government structure and contributing sourced civic data. The skill is a thin client of the Jurisdictional MCP server (~/workspace/jurisdictional, lib/jurisdictional/mcp/tools/). The server's live tools/list is the source of truth for tool names, fields and enums; when it and this repo disagree, fix this repo.

  • Sends data out
  • In this repositoryOne other file it gives its agents.

The file

We split this CLAUDE.md into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Access tiers: no token → 19 public read tools.

    line 28
  2. Distinctive:

    Keep the three stops (after Step 2, each Step 4 review, the next target) and the Step 4 review table.

    line 36
  3. Very specific:

    Keep SKILL.md under 500 lines.

    line 37
  4. Very specific:

    Check enums against the live schemas: curl -s -X POST https://jurisdictional.org/api/mcp/message -H 'content-type: application/json' -d …

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. Start with PLAN.md.

What This Is

A Claude Code plugin for jurisdictional.org containing the gather skill — a conversational interface for exploring local government structure and contributing sourced civic data.

The skill is a thin client of the Jurisdictional MCP server (~/workspace/jurisdictional, lib/jurisdictional/mcp/tools/). The server's live tools/list is the source of truth for tool names, fields and enums; when it and this repo disagree, fix this repo.

Repository Structure

  • .claude-plugin/plugin.json — plugin manifest (bump version on every release)
  • .claude-plugin/marketplace.json — single-plugin marketplace: /plugin marketplace add jurisdictional/jurisdictional-skill
  • .mcp.json — the MCP server, with headersHelper → bin/jurisdictional-headers.sh
  • bin/jurisdictional-headers.sh — sends Authorization: Bearer <~/.jurisdictional/token> when the file holds a jur_... key, {} otherwise
  • skills/gather/SKILL.md — the flow: preflight → location → what exists → research → review → submit → verify
  • skills/gather/references/tools.md — what each MCP tool does to live data, and who can call it
  • skills/gather/references/services.md — gathering services
  • skills/gather/schema.md + examples/austin-tx/ — local-file format; must validate against jurisdictional-data/schemas/
  • TESTING.md — scenarios with checks

Key Concepts

  • Juricode: given an address, every jurisdiction (federal → local) that governs that location.
  • Access tiers: no token → 19 public read tools. Signed in → gather, propose_change, create_entity, import_jurisdiction, image candidates. Admin → reconcile_roster, end_tenure, merge_entities, delete_entity, coverage reports.
  • Auth: no header or an empty bearer gets the public tools; an unknown key gets HTTP 401 for the whole connection, so the helper sends no header unless the file holds a jur_... key. Plugin helpers don't see TOKEN-like env vars, so the token lives in ~/.jurisdictional/token (from /auth/cli).
  • Writes: create_entity and import_jurisdiction apply live; propose_change queues for review, or corroborates when the value is unchanged.
  • Provenance: values come only from the government's own page — fetched with gather, an archived capture (mcc_read from the local Common Crawl server in ~/workspace/municipal-common-crawl, or gather's archived copy; cited with the capture date), the user's browser, or the user's paste — or from the user's own knowledge. Never search snippets or training data.

When Modifying the Skill

  • Invoked via /gather [address or city, state]; arguments arrive as $ARGUMENTS. disable-model-invocation: true keeps it user-invoked.
  • Keep the three stops (after Step 2, each Step 4 review, the next target) and the Step 4 review table; no other pauses.
  • Keep SKILL.md under 500 lines; put detail in references/ (one level deep).
  • Check enums against the live schemas: curl -s -X POST https://jurisdictional.org/api/mcp/message -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'.
  • Validate: claude plugin validate ., and ajv against jurisdictional-data/schemas/ for the examples (see the commit that fixed them).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.