twlaw-regulationslisted

# twlaw regulations Use the local Rust CLI `twlaw` as the agent interface. Do not start or configure an MCP server. ## Contract - Use `twlaw ... --json` for agent calls. - If availability is uncertain, run `twlaw --version`; if missing, stop and report that `twlaw` is not installed. Do not install from this skill. - Preserve `source_url`, `retrieved_at`, cache fields, amendment/history metadata, and coverage limits when citing results. - Treat output as legal research material, not legal advice. - Prefer no-credential public sources and local cached/bundled data. Keep live government HTTP query concurrency low. ## Strategy - Use `regulation pcode` when the user gives a law name and you need a stable pcode. - Use `regulation query` for current article text or article ranges. - Use `regulation query --include-history` when amendment history matters. - For repeated MOJ law/order work, prefer `moj sync` once, then `moj search` or `moj get`; this uses the official no-token MOJ OpenAPI ZIP cache instead of repeated live page fetches. - For recency-sensitive law/order questions, call `moj updates` before relying on cached data. - Start with narrow metadata queries before fetching long text. ## Commands ```bash twlaw regulation pcode --law "民法" --json twlaw regulation search --keyword "勞動" --limit 20 --json twlaw regulation query --law "民法" --article "184" --json twlaw regulation query --law "民法" --from "184" --to "198" --json twlaw regulation query --pcode "B0000001" --includ