federal-register-doc-fetch
Fetch Federal Register document search results with explicit term, publication-window, agency, document-type, topic, docket, and RIN filters, then return structured official-policy records with retries, throttling, pagination, and validation. Use when tasks need authoritative U.S. Federal Register notices, proposed rules, final rules, or presidential documents for policy verification and regulatory context.
What this skill does
# Federal Register Doc Fetch ## Core Goal - Search the Federal Register `documents` API with one bounded request plan. - Retrieve official notices, proposed rules, final rules, or presidential documents relevant to one mission topic. - Return machine-readable JSON records with publication dates, agencies, URLs, excerpts, docket IDs, and RIN metadata. - Keep execution deterministic with retries, throttling, pagination caps, and payload validation. ## Repository Policy - This is the only Federal Register source skill in this repository. - Do not create or invoke parallel Federal Register wrappers for the same `documents` endpoint. - When eco-council or OpenClaw assigns a raw artifact path, write this skill's full JSON payload to that exact path with `--output`. ## Required Environment - Configure runtime by environment variables in `references/env.md`. - Start from `assets/config.example.env`. - Load env values before running commands: ```bash set -a source assets/config.example.env set +a ``` ## Workflow 1. Validate effective configuration. ```bash python3 scripts/federal_register_doc_fetch.py check-config --pretty ``` 2. Dry-run the search plan before making remote calls. ```bash python3 scripts/federal_register_doc_fetch.py fetch \ --term "wildfire smoke EPA" \ --start-date 2023-06-01 \ --end-date 2023-06-10 \ --agency environmental-protection-agency \ --document-type NOTICE \ --max-pages 2 \ --max-records 20 \ --dry-run \ --pretty ``` 3. Fetch one bounded search window and write the payload. ```bash python3 scripts/federal_register_doc_fetch.py fetch \ --term "wildfire smoke EPA" \ --start-date 2023-06-01 \ --end-date 2023-06-10 \ --agency environmental-protection-agency \ --document-type NOTICE \ --output ./data/federal-register-docs.json \ --pretty ``` 4. Use task-specific structured filters when the mission already knows them. ```bash python3 scripts/federal_register_doc_fetch.py fetch \ --term "greenhouse gas" \ --start-date 2024-03-01 \ --end-date 2024-03-31 \ --regulation-id-number 3235-AM87 \ --document-type RULE \ --document-type PRORULE \ --max-records 50 \ --pretty ``` ## Output Record Shape Each item in `records` is one Federal Register document record, typically including: - `document_number`, `title`, `type` - `publication_date`, `effective_on` - `agencies`, `topics` - `abstract`, `excerpts` - `html_url`, `pdf_url`, `raw_text_url`, `comment_url` - `docket_ids`, `regulation_id_numbers` - `source_query_url`, `source_page_number` The full raw payload also keeps request metadata, page summaries, and validation output for downstream auditing. ## Scope Boundaries - This skill targets the Federal Register `documents` search endpoint only. - This skill does not crawl linked HTML, PDF, or raw-text bodies. - This skill does not infer legal meaning or summarize regulations. - This skill does not need an API key. - This skill is the canonical Federal Register fetch interface for this repository. ## References - `references/env.md` - `references/federal-register-api-notes.md` - `references/federal-register-limitations.md` - `references/openclaw-chaining-templates.md` ## Script - `scripts/federal_register_doc_fetch.py`
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.