$npx -y skills add AlpacaLabsLLC/skills-for-architects --skill nyc-dob-violationsLook 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 /nyc-hpd.
| 1 | # /nyc-dob-violations — DOB & ECB Violations |
| 2 | |
| 3 | Look up DOB violations and ECB (Environmental Control Board) violations for any NYC building. Flags open violations prominently. No API key required. |
| 4 | |
| 5 | ## Usage |
| 6 | |
| 7 | ``` |
| 8 | /nyc-dob-violations 120 Broadway, Manhattan |
| 9 | /nyc-dob-violations 1000770001 (BBL) |
| 10 | /nyc-dob-violations 1001389 (BIN) |
| 11 | ``` |
| 12 | |
| 13 | ## Steps 1–2: Parse Input & Resolve BBL/BIN |
| 14 | |
| 15 | 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. |
| 16 | |
| 17 | ## Step 3: Query Violations |
| 18 | |
| 19 | Dataset IDs and field names are canonical in `../nyc-property-report/socrata-reference.md` — on any disagreement, the reference wins. |
| 20 | |
| 21 | Query 3 datasets using BIN: |
| 22 | |
| 23 | ### DOB Violations |
| 24 | ``` |
| 25 | https://data.cityofnewyork.us/resource/3h2n-5cm9.json?$where=bin='{BIN}'&$order=issue_date DESC&$limit=50 |
| 26 | ``` |
| 27 | Key fields: `isn_dob_bis_viol`, `violation_type`, `issue_date`, `violation_category`, `disposition_date`, `disposition_comments` |
| 28 | |
| 29 | ### ECB Violations |
| 30 | ``` |
| 31 | https://data.cityofnewyork.us/resource/6bgk-3dad.json?$where=bin='{BIN}'&$order=issue_date DESC&$limit=50 |
| 32 | ``` |
| 33 | 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` |
| 34 | |
| 35 | ### Active/Open Violations |
| 36 | ``` |
| 37 | https://data.cityofnewyork.us/resource/sjhj-bc8q.json?$where=bin='{BIN}' |
| 38 | ``` |
| 39 | Returns only currently open violations (pre-filtered subset of DOB violations). |
| 40 | |
| 41 | ## Step 4: Print Results |
| 42 | |
| 43 | Open violations go first, flagged with ⚠. |
| 44 | |
| 45 | ```markdown |
| 46 | ## DOB & ECB Violations — {Address} |
| 47 | |
| 48 | ### ⚠ Open Violations: {count} |
| 49 | |
| 50 | | Violation # | Type | Date | Description | Disposition | |
| 51 | |-------------|------|------|-------------|-------------| |
| 52 | | ... | ... | YYYY-MM-DD | ... | ... | |
| 53 | |
| 54 | ### All DOB Violations ({count} total) |
| 55 | |
| 56 | | Violation # | Type | Issue Date | Category | Disposition Date | Comments | |
| 57 | |-------------|------|------------|----------|------------------|----------| |
| 58 | | ... | ... | ... | ... | ... | ... | |
| 59 | |
| 60 | ### ECB Violations ({count} total) |
| 61 | |
| 62 | | ECB # | Date | Violation Type | Severity | Penalty Imposed | Paid | Balance Due | Status | |
| 63 | |-------|------|----------------|----------|-----------------|------|-------------|--------| |
| 64 | | {ecb_violation_number} | {issue_date} | {violation_type} | {severity} | ${penality_imposed} | ${amount_paid} | ${balance_due} | {hearing_status} | |
| 65 | |
| 66 | **Total penalties assessed:** ${amount} |
| 67 | **Total balance due:** ${amount} |
| 68 | |
| 69 | 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) |
| 70 | ``` |
| 71 | |
| 72 | If no violations found: "No DOB or ECB violations found for this property." |
| 73 | |
| 74 | ### Conventions |
| 75 | - All dates: YYYY-MM-DD |
| 76 | - Dollar amounts: comma-separated ($1,234) |
| 77 | - Open/active items flagged with ⚠ |
| 78 | - If Socrata returns empty array: "No results found" |
| 79 | - If HTTP error: note it and suggest checking the address |
| 80 | - If the user requests, write results to a file |
| 81 | |
| 82 | ## Final Step: Disclaimer + Marker (required) |
| 83 | |
| 84 | 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: |
| 85 | |
| 86 | ```markdown |
| 87 | > **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. |
| 88 | |
| 89 | <!-- architecture-studio:requires-disclaimer --> |
| 90 | ``` |
| 91 | |
| 92 | 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. |