alpacalabsllc/nyc-dob-violations
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.
npx skills add https://github.com/AlpacaLabsLLC/skills-for-architects --skill nyc-dob-violations
Look up DOB violations and ECB (Environmental Control Board) violations for any NYC building. Flags open violations prominently. No API key required.
/as:nyc-dob-violations 120 Broadway, Manhattan
/as:nyc-dob-violations 1000770001 (BBL)
/as:nyc-dob-violations 1001389 (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.
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:
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
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
https://data.cityofnewyork.us/resource/sjhj-bc8q.json?$where=bin='{BIN}'
Returns only currently open violations (pre-filtered subset of DOB violations).
Open violations go first, flagged with ⚠.
## DOB & ECB Violations — {Address}
### ⚠ Open Violations: {count}
| Violation # | Type | Date | Description | Disposition |
|-------------|------|------|-------------|-------------|
| ... | ... | YYYY-MM-DD | ... | ... |
### All DOB Violations ({count} total)
| Violation # | Type | Issue Date | Category | Disposition Date | Comments |
|-------------|------|------------|----------|------------------|----------|
| ... | ... | ... | ... | ... | ... |
### ECB Violations ({count} total)
| ECB # | Date | Violation Type | Severity | Penalty Imposed | Paid | Balance Due | Status |
|-------|------|----------------|----------|-----------------|------|-------------|--------|
| {ecb_violation_number} | {issue_date} | {violation_type} | {severity} | ${penality_imposed} | ${amount_paid} | ${balance_due} | {hearing_status} |
**Total penalties assessed:** ${amount}
**Total balance due:** ${amount}
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."
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:
> **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.
<!-- architecture-studio:requires-disclaimer -->
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.
Take alpacalabsllc/nyc-dob-violations from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.