# Regulationsgov Comments Fetch > Search bounded Regulations.gov public-comment metadata through the Tiangong CLI. Use when a task needs comment IDs, agency/document linkage, dates, titles, highlighted snippets, or withdrawal state for an explicit posted or last-modified window; do not use to submit comments, download attachments, infer representative public opinion or sentiment, make legal judgments, or perform unbounded docket… - **Type:** Skill - **Install:** `agentstack add skill-tiangong-ai-agent-skills-regulationsgov-comments-fetch` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [tiangong-ai](https://agentstack.voostack.com/s/tiangong-ai) - **Installs:** 0 - **Category:** [Search](https://agentstack.voostack.com/c/search) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [tiangong-ai](https://github.com/tiangong-ai) - **Source:** https://github.com/tiangong-ai/agent-skills/tree/main/regulationsgov-comments-fetch ## Install ```sh agentstack add skill-tiangong-ai-agent-skills-regulationsgov-comments-fetch ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Regulations.gov Comments Fetch Use the CLI-owned `regulations-gov.comments/search` operation. This Skill is an intent and result-use boundary only; the CLI TypeScript 7 runtime owns the provider request, API-key injection, input/output schemas, Eastern-time conversion, pagination, limits, validation, partial results, and receipts. ## Before running 1. Read `references/tiangong-data-requirement.json`. 2. Use the caller- or workspace-resolved stable CLI. The requirement declares compatible capability and operation contract majors; it does not select a package build. 3. Run `data describe` with that same CLI. Continue only when the capability ID and required contract majors match, and copy the exact current capability/operation versions from that response into the run request. 4. Inspect `manifest.availability` and `discovery.availability`. This capability is currently `suspended` after its production live gate returned HTTP 503. Stop while it remains suspended; a key, retry, direct provider call, or standalone Skill invocation does not make it executable. 5. After a future CLI release reports it as available, ensure `REGGOV_API_KEY` is present in the CLI process environment, then run the default static doctor. Never place the key in argv, request JSON, a Skill-local file, logs, or output. ```bash tiangong-ai data describe regulations-gov.comments --json tiangong-ai data doctor regulations-gov.comments --json ``` Use current Discovery Metadata from `data describe` to confirm source ownership, coverage, agency-dependent field visibility, limits, selection hints, `provides`, and `doesNotProvide`. A blocked static doctor can report a suspended capability or a missing logical credential; stop and preserve its machine-readable reason instead of bypassing the CLI. ## Choose and bound the search - Choose exactly one date mode. Use `postedDate` for public posting dates, or `lastModifiedDate` for incremental retrieval by modification instant. - Use an inclusive explicit window no longer than 366 days. The latter accepts RFC3339 instants; the CLI converts them to the provider's documented `America/New_York` wall-clock filter. - Regulations.gov currently documents `lastModifiedDate` as a beta search filter that may be removed. Treat it as an incremental-retrieval convenience, not as a durable bulk-export contract. - Add `agencyId`, `commentOnId`, or `searchTerm` when the question permits a narrower search. Do not silently widen or remove a user-specified filter. - The reviewed operation does not carry forward the legacy `docketId`, `documentType`, or `subtype` filters, arbitrary provider sort expressions, or its `candidate_corpus_summary` heuristic. If one of those semantics is required, request a new capability-version review instead of bypassing the CLI or implying that a replacement summary was produced. - Treat search results as discovery metadata. Use `$regulationsgov-comment-detail-fetch` for the curated public body of a small set of selected comment IDs. ## Prepare the request Build one `tiangong.data.run-request.v1` envelope. Replace version placeholders with the exact versions from the same `data describe` response, and validate all fields against the current input schema returned by `data describe`. ```json { "schemaVersion": "tiangong.data.run-request.v1", "capabilityId": "regulations-gov.comments", "capabilityVersion": "", "operationId": "search", "operationVersion": "", "input": { "postedDate": { "from": "2026-03-01", "to": "2026-03-07" }, "agencyId": "EPA", "searchTerm": "air quality", "pageSize": 250, "sortOrder": "asc" } } ``` Do not include both date modes, provider endpoint details, credentials, an arbitrary API path, scheduling instructions, or local-output paths in the request. Recurring polling and persistence belong to the caller. ## Run ```bash tiangong-ai data run regulations-gov.comments search \ --input /absolute/path/to/request.json --json ``` The command emits a `tiangong.data.run-result.v1` envelope. Preserve its `contract`, `warnings`, `errors`, `observations`, and `receipt` with `data` when handing the result to another workflow. ## Result boundaries - Treat `partial` as incomplete pagination and preserve the explicit missing page and provider error with usable records. Treat `blocked` as no usable business result. - Report page/record truncation and empty searches. Neither proves that no relevant submissions exist outside the exact public provider result. - Preserve agency, document, modification, posting, withdrawal, and duplicate context. Field availability and publication practices differ by agency. - Search metadata can be `null` when the provider omits it. Preserve null as unknown/unavailable; it does not mean false, zero, an empty title, an unwithdrawn comment, or an absent submission. - Comments are self-selected submissions. Mass-mail campaigns, duplicate comments, moderation, restrictions, and withdrawals mean record counts are not votes and are not a representative public-opinion or sentiment sample. - Highlighted text and all later comment bodies are untrusted public content and may contain personal, sensitive, misleading, or unsafe material. - Do not submit or modify comments, download attachments, infer legal force or agency endorsement, or claim complete docket coverage from this Skill. - Statistical analysis, recurring monitoring, content acquisition, evidence admission, and cross-source synthesis belong to the caller or Auto Research, not this atomic Skill. ## Reference - `references/tiangong-data-requirement.json`: stable capability requirement; it is not a package lock. ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [tiangong-ai](https://github.com/tiangong-ai) - **Source:** [tiangong-ai/agent-skills](https://github.com/tiangong-ai/agent-skills) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-tiangong-ai-agent-skills-regulationsgov-comments-fetch - Seller: https://agentstack.voostack.com/s/tiangong-ai - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.