git:20260812.ab1329f to git:20260920.ef0a19e

44 added, 64 removed. Audit A to A.

---

name: nyc-landmarks

- description: Check whether a NYC building is landmarked or in a historic district using LPC data. Use when the user asks "is this building landmarked", whether a site sits in a historic district, or whether LPC review applies. NYC only.

+ description: "Check whether a NYC building is landmarked or in a historic district using LPC data. Use when the user asks \"is this building landmarked\", whether a site sits in a historic district, or whether LPC review applies. NYC only."

allowed-tools:

- WebFetch

- Write

- Read

- Bash

---

- # /as:nyc-landmarks — LPC Landmark & Historic District Check

-

- > 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.

- Check if a NYC building is individually landmarked or within a historic district using the LPC Individual Landmark & Historic District Building Database. No API key required.

- ## Usage

- ```

- /as:nyc-landmarks 120 Broadway, Manhattan

- /as:nyc-landmarks 1000770001 (BBL)

- /as:nyc-landmarks 1001389 (BIN)

- ```

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

- 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) and resolve via PLUTO.

- **This skill's extra:** also store `histdist` from PLUTO — used in Step 3.

+ # nyc-landmarks

- ## Step 3: Query LPC Database

+ Before acting, read the [host contract](../../docs/host-harness-contract.md) and this component’s [declaration](host-contract.json) (`skill:nyc-landmarks`). 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).

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

+ ## Native research and report custody

- Use the Individual Landmarks dataset (`buis-pvji`). Query by BBL first:

- ```

- https://data.cityofnewyork.us/resource/buis-pvji.json?bbl={BBL}

- ```

+ 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.

- If no results, fallback by block + lot. **This dataset stores block/lot WITHOUT zero-padding** (e.g. block `47`, lot `7501`) — strip leading zeros from the parsed BBL components:

- ```

- https://data.cityofnewyork.us/resource/buis-pvji.json?$where=block='{BLOCK}' AND lot='{LOT}' AND borough='{BOROUGH}'

- ```

+ 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.

- Key fields: `lpc_name`, `lpc_lpnumb`, `desdate`, `landmarkty`, `lpc_sitede`, `lpc_sitest`, `lpc_altern`, `address`, `url_report`

+ 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.

- Also check PLUTO's `histdist` field from Step 2 — if it has a value, the property is in a historic district even if not individually listed in the LPC dataset.

+ 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.

- ## Step 4: Print Results

+ 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.

- ```markdown

- ## Landmark Status — {Address}

+ ## Resolve the requested NYC scope

- **Status: LANDMARKED / IN HISTORIC DISTRICT / NOT DESIGNATED**

+ 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.

- | Field | Value |

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

- | LP Number | {lpc_lpnumb} |

- | Name | {lpc_name} |

- | Designation Date | {desdate} |

- | Type | {landmarkty} |

- | Site Description | {lpc_sitede} |

- | Site Style | {lpc_sitest} |

- | Also Known As | {lpc_altern} |

- | LPC Report | {url_report} |

- | Historic District | {histdist from PLUTO} |

+ ## Retrieve and interpret

- **Implications:** Exterior alterations require LPC Certificate of Appropriateness before DOB permit.

+ Query LPC dataset and designation-report routes from the [source catalog](../../corpus/sources/catalog.json) for landmark and historic-district records. Retrieve original metadata/field definitions before building a query. Preserve designation status, names, dates and original report links. 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: [LPC Individual Landmarks](https://data.cityofnewyork.us/Housing-Development/Individual-Landmarks/buis-pvji)

- ```

- If not landmarked and not in a historic district: "No landmark designation 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

- - 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.