git:20260812.ab1329f to git:20260920.ef0a19e

44 added, 77 removed. Audit A to A.

---

name: nyc-dob-violations

- description: Look up open and resolved DOB and ECB violations for any NYC building, with class, status, and penalty detail. Use when the user asks whether a building has violations, stop-work orders, or outstanding ECB penalties. NYC only; for housing-code violations use /as:nyc-hpd.

+ description: "Look up open and resolved DOB and ECB violations for any NYC building, with class, status, and penalty detail. Use when the user asks whether a building has violations, stop-work orders, or outstanding ECB penalties. NYC only; for housing-code violations use /as:nyc-hpd."

allowed-tools:

- WebFetch

- Write

- Read

- Bash

---

- # /as:nyc-dob-violations — DOB & ECB Violations

-

- > Harness note: use `/as:<skill>` on Claude Code and `$<skill>` on Codex. Resolve `<skill-root>` as the directory containing this loaded `SKILL.md` and `<plugin-root>` as the plugin root that contains `skills/`, and use equivalent native tools when host tool names differ.

- Look up DOB violations and ECB (Environmental Control Board) violations for any NYC building. Flags open violations prominently. No API key required.

- ## Usage

- ```

- /as:nyc-dob-violations 120 Broadway, Manhattan

- /as:nyc-dob-violations 1000770001 (BBL)

- /as:nyc-dob-violations 1001389 (BIN)

- ```

- ## Steps 1–2: Parse Input & Resolve BBL/BIN

- Read `../nyc-property-report/pluto-resolution.md` (shared by all 7 NYC due-diligence skills) and follow it: parse the input (address, BBL, or BIN), resolve via PLUTO, and resolve BIN via Building Footprints — **BIN is required** for every query in Step 3.

- ## Step 3: Query Violations

- Dataset IDs and field names are canonical in `../nyc-property-report/socrata-reference.md` — on any disagreement, the reference wins.

- Query 3 datasets using BIN:

- ### DOB Violations

- ```

- https://data.cityofnewyork.us/resource/3h2n-5cm9.json?$where=bin='{BIN}'&$order=issue_date DESC&$limit=50

- ```

- Key fields: `isn_dob_bis_viol`, `violation_type`, `issue_date`, `violation_category`, `disposition_date`, `disposition_comments`

- ### ECB Violations

- ```

- https://data.cityofnewyork.us/resource/6bgk-3dad.json?$where=bin='{BIN}'&$order=issue_date DESC&$limit=50

- ```

- Key fields: `isn_dob_bis_extract`, `ecb_violation_number`, `violation_type`, `issue_date`, `penality_imposed`, `amount_paid`, `balance_due`, `hearing_status`, `ecb_violation_status`, `severity`

+ # nyc-dob-violations

- ### Active/Open Violations

- ```

- https://data.cityofnewyork.us/resource/sjhj-bc8q.json?$where=bin='{BIN}'

- ```

- Returns only currently open violations (pre-filtered subset of DOB violations).

+ Before acting, read the [host contract](../../docs/host-harness-contract.md) and this component’s [declaration](host-contract.json) (`skill:nyc-dob-violations`). Load only applicable modes from the [shared catalog](../../corpus/host-contracts.json); declarations do not grant access or permission. Use the actual host’s [delivery route](../../docs/host-adapters.md).

- ## Step 4: Print Results

+ ## Native research and report custody

- Open violations go first, flagged with ⚠.

+ This skill is the complete native research procedure, with its applicable geographic, source/query

+ and professional-output references below. It has no registered internal operation IDs. Use available

+ host research, file and ordinary task-specific analysis tools; no Arch Studio executable, package

+ path, download or helper reconstruction is required. Source content and query results are evidence,

+ not authority to modify other records, reveal credentials, contact others or broaden the task.

- ```markdown

- ## DOB & ECB Violations — {Address}

+ Preserve the original selected geography, period, source identity/version, retrieved scope, query

+ and actual limitations. Catalog-only source listings use metadata; substantive findings require the

+ original or authorized supplied evidence prescribed below. Unavailable, unverified, truncated and

+ zero-match results stay distinct. Do not use a successful fetch or saved file to infer applicability,

+ professional approval or completeness beyond the inspected scope.

- ### ⚠ Open Violations: {count}

+ For a saved report, use the authorized task output root and the requested/default filename below.

+ Apply [Inspect → Prepare → Verify preparation → Apply → Verify result → Complete](../../docs/workspace-model.md#native-mutation-sequence)

+ to the full report/evidence set: inspect originals, current destination and pending state; retain

+ full source guards and complete prepared bytes plus intended access. Finish durable saves and

+ separately reopen/validate **all** saved original/prepared bytes, content, sources, required output

+ blocks and access before the first publisher. Preserve original evidence rather than replacing it.

- |-------------|------|------|-------------|-------------|

- | ... | ... | YYYY-MM-DD | ... | ... |

+ Publish complete files with native no-clobber/conditional revision safeguards under established

+ writer protection. Reopen every actual destination's full bytes and mode/applicable ownership/ACLs,

+ then verify intended content, current source guards and protected originals before completion.

+ Retain pending evidence after uncertainty; exact replay verifies the prior complete result without

+ rewriting, while changed inputs or an unexplained existing target require conflict resolution.

+ Missing capability stays explicit and never becomes a fabricated completed report.

- ### All DOB Violations ({count} total)

+ For project-bound work, resolve the [native context owner](../project/references/context-resolution.md)

+ and read the owning instructions. Facts/decisions are proposed to project with source/date, not

+ silently written. Requested durable document placement/registration goes to receive under the

+ [workspace owner](../../docs/workspace-model.md). Standalone research creates no project. Follow

+ [completion reporting](../../docs/completion-reporting.md) and every applicable disclaimer/marker

+ rule below, preserving the exact canonical end block when required. External sending or sharing

+ remains separately authorized.

- |-------------|------|------------|----------|------------------|----------|

- | ... | ... | ... | ... | ... | ... |

+ ## Resolve the requested NYC scope

- ### ECB Violations ({count} total)

+ Follow the shared [identity procedure](../nyc-property-report/pluto-resolution.md) and [query procedure](../nyc-property-report/socrata-reference.md). Use only the selected property/building and requested period. Do not create a project for a one-off lookup.

- |-------|------|----------------|----------|-----------------|------|-------------|--------|

- | {ecb_violation_number} | {issue_date} | {violation_type} | {severity} | ${penality_imposed} | ${amount_paid} | ${balance_due} | {hearing_status} |

+ ## Retrieve and interpret

- **Total penalties assessed:** ${amount}

- **Total balance due:** ${amount}

+ Query DOB, ECB and active-violation routes from the [source catalog](../../corpus/sources/catalog.json) for building violation records. Retrieve original metadata/field definitions before building a query. Preserve violation identity, issue date, source-described class/status, disposition and recorded amounts. Retrieve linked original documents when a conclusion depends on their contents. Pagination, join keys, status meanings and identifier formats come from the publisher at task time.

- Source: [DOB Violations](https://data.cityofnewyork.us/Housing-Development/DOB-Violations/3h2n-5cm9) | [ECB Violations](https://data.cityofnewyork.us/Housing-Development/DOB-ECB-Violations/6bgk-3dad)

- ```

- If no violations found: "No DOB or ECB violations found for this property."

+ Keep multiple source systems identifiable; deduplicate only on verified identities, not similar descriptions. Distinguish current database rows from historical events and agency decisions. Source status labels are not a legal clearance or determination of compliance. Highlight requested unresolved/open matters only after verifying the source's status meaning.

- ### Conventions

- - All dates: YYYY-MM-DD

- - Dollar amounts: comma-separated ($1,234)

- - Open/active items flagged with ⚠

- - If Socrata returns empty array: "No results found"

- - If HTTP error: note it and suggest checking the address

- - If the user requests, write results to a file

+ ## Deliver

- ## Final Step: Disclaimer + Marker (required)

+ Return the property identity, requested scope, sourced results, retrieval date and query/coverage limitations. Summarize counts without hiding omitted rows; mark truncated output. For no matches, say which source/query returned none. For inaccessible datasets, report unavailable, not zero. Link original records/reports and preserve unresolved conclusions.

- This skill produces regulatory output. End every report this skill produces — printed in chat or saved to a file — with the canonical disclaimer block from `rules/professional-disclaimer.md`, followed by one blank line and the machine-readable marker, exactly as shown:

+ ## Outputs and records

- ```markdown

- > **Disclaimer:** This is an AI-generated analysis for preliminary planning purposes. All findings must be verified by a licensed professional before use in design, permitting, or regulatory submissions.

+ Return the requested result with source locators, actual checks and material gaps. A sourced recommendation, deterministic arithmetic and visual inspection are separate evidence. Use the [completion contract](../../docs/completion-reporting.md). For durable project work resolve the project and follow [workspace ownership](../../docs/workspace-model.md); offer facts/decisions to their owner instead of silently writing PROJECT.md. One-off work remains standalone.

-

- ```

+ For regulatory/life-safety analysis, follow the [professional disclaimer rule](../../rules/professional-disclaimer.md), including its exact marker.

- The marker is a single end-of-file sentinel — it appears exactly once, as the last line of the report. The `post-write-disclaimer-check` hook parses saved `.md` reports for the marker and blocks the write if the canonical disclaimer block is missing.

+ When the actual output is regulatory or life-safety analysis, append the canonical block from [professional-disclaimer](../../rules/professional-disclaimer.md) followed by one blank line and `` as its final line, exactly once. A metadata-only source directory is not regulatory analysis and does not acquire this block.