nyc-landmarks

Name: nyc-landmarks
Author: AlpacaLabsLLC

260stars54forks

How to install nyc-landmarks?

alpacalabsllc/skills-for-architects/nyc-landmarks

$npx -y skills add AlpacaLabsLLC/skills-for-architects --skill nyc-landmarks

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# /nyc-landmarks — LPC Landmark & Historic District Check
2
3	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.
4
5	## Usage
6
7	```
8	/nyc-landmarks 120 Broadway, Manhattan
9	/nyc-landmarks 1000770001 (BBL)
10	/nyc-landmarks 1001389 (BIN)
11	```
12
13	## Steps 1–2: Parse Input & Resolve BBL
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) and resolve via PLUTO.
16
17	This skill's extra: also store `histdist` from PLUTO — used in Step 3.
18
19	## Step 3: Query LPC Database
20
21	Dataset IDs and field names are canonical in `../nyc-property-report/socrata-reference.md` — on any disagreement, the reference wins.
22
23	Use the Individual Landmarks dataset (`buis-pvji`). Query by BBL first:
24	```
25	https://data.cityofnewyork.us/resource/buis-pvji.json?bbl={BBL}
26	```
27
28	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:
29	```
30	https://data.cityofnewyork.us/resource/buis-pvji.json?$where=block='{BLOCK}' AND lot='{LOT}' AND borough='{BOROUGH}'
31	```
32
33	Key fields: `lpc_name`, `lpc_lpnumb`, `desdate`, `landmarkty`, `lpc_sitede`, `lpc_sitest`, `lpc_altern`, `address`, `url_report`
34
35	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.
36
37	## Step 4: Print Results
38
39	```markdown
40	## Landmark Status — {Address}
41
42	Status: LANDMARKED / IN HISTORIC DISTRICT / NOT DESIGNATED
43
44	\| Field \| Value \|
45	\|-------\|-------\|
46	\| LP Number \| {lpc_lpnumb} \|
47	\| Name \| {lpc_name} \|
48	\| Designation Date \| {desdate} \|
49	\| Type \| {landmarkty} \|
50	\| Site Description \| {lpc_sitede} \|
51	\| Site Style \| {lpc_sitest} \|
52	\| Also Known As \| {lpc_altern} \|
53	\| LPC Report \| {url_report} \|
54	\| Historic District \| {histdist from PLUTO} \|
55
56	Implications: Exterior alterations require LPC Certificate of Appropriateness before DOB permit.
57
58	Source: [LPC Individual Landmarks](https://data.cityofnewyork.us/Housing-Development/Individual-Landmarks/buis-pvji)
59	```
60
61	If not landmarked and not in a historic district: "No landmark designation found for this property."
62
63	### Conventions
64	- All dates: YYYY-MM-DD
65	- If Socrata returns empty array: "No results found"
66	- If HTTP error: note it and suggest checking the address
67	- If the user requests, write results to a file
68
69	## Final Step: Disclaimer + Marker (required)
70
71	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:
72
73	```markdown
74	> 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.
75
76	<!-- architecture-studio:requires-disclaimer -->
77	```
78
79	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.

People who liked this also viewed

6 picks

Type

nyc-landmarks

260stars54forks

View on GitHub

How to install nyc-landmarks?

alpacalabsllc/skills-for-architects/nyc-landmarks

$npx -y skills add AlpacaLabsLLC/skills-for-architects --skill nyc-landmarks

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# /nyc-landmarks — LPC Landmark & Historic District Check
2
3	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.
4
5	## Usage
6
7	```
8	/nyc-landmarks 120 Broadway, Manhattan
9	/nyc-landmarks 1000770001 (BBL)
10	/nyc-landmarks 1001389 (BIN)
11	```
12
13	## Steps 1–2: Parse Input & Resolve BBL
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) and resolve via PLUTO.
16
17	This skill's extra: also store `histdist` from PLUTO — used in Step 3.
18
19	## Step 3: Query LPC Database
20
21	Dataset IDs and field names are canonical in `../nyc-property-report/socrata-reference.md` — on any disagreement, the reference wins.
22
23	Use the Individual Landmarks dataset (`buis-pvji`). Query by BBL first:
24	```
25	https://data.cityofnewyork.us/resource/buis-pvji.json?bbl={BBL}
26	```
27
28	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:
29	```
30	https://data.cityofnewyork.us/resource/buis-pvji.json?$where=block='{BLOCK}' AND lot='{LOT}' AND borough='{BOROUGH}'
31	```
32
33	Key fields: `lpc_name`, `lpc_lpnumb`, `desdate`, `landmarkty`, `lpc_sitede`, `lpc_sitest`, `lpc_altern`, `address`, `url_report`
34
35	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.
36
37	## Step 4: Print Results
38
39	```markdown
40	## Landmark Status — {Address}
41
42	Status: LANDMARKED / IN HISTORIC DISTRICT / NOT DESIGNATED
43
44	\| Field \| Value \|
45	\|-------\|-------\|
46	\| LP Number \| {lpc_lpnumb} \|
47	\| Name \| {lpc_name} \|
48	\| Designation Date \| {desdate} \|
49	\| Type \| {landmarkty} \|
50	\| Site Description \| {lpc_sitede} \|
51	\| Site Style \| {lpc_sitest} \|
52	\| Also Known As \| {lpc_altern} \|
53	\| LPC Report \| {url_report} \|
54	\| Historic District \| {histdist from PLUTO} \|
55
56	Implications: Exterior alterations require LPC Certificate of Appropriateness before DOB permit.
57
58	Source: [LPC Individual Landmarks](https://data.cityofnewyork.us/Housing-Development/Individual-Landmarks/buis-pvji)
59	```
60
61	If not landmarked and not in a historic district: "No landmark designation found for this property."
62
63	### Conventions
64	- All dates: YYYY-MM-DD
65	- If Socrata returns empty array: "No results found"
66	- If HTTP error: note it and suggest checking the address
67	- If the user requests, write results to a file
68
69	## Final Step: Disclaimer + Marker (required)
70
71	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:
72
73	```markdown
74	> 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.
75
76	<!-- architecture-studio:requires-disclaimer -->
77	```
78
79	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.

People who liked this also viewed

6 picks

Type