nyc-bsa

Name: nyc-bsa
Author: AlpacaLabsLLC

260stars54forks

How to install nyc-bsa?

alpacalabsllc/skills-for-architects/nyc-bsa

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

Installs into the current project.

Summary

Look up Board of Standards and Appeals (BSA) variances and special permits for any NYC property. Use when checking whether a lot carries zoning relief — variances, special permits, appeals — that modifies its as-of-right envelope. NYC only; for base zoning controls use /zoning-an

Files · 1

View on GitHub

SKILL.md

1	# /nyc-bsa — BSA Variances & Special Permits
2
3	Look up Board of Standards and Appeals (BSA) applications, variances, and special permits for any NYC property. Records available from 1998 to present. No API key required.
4
5	## Usage
6
7	```
8	/nyc-bsa 120 Broadway, Manhattan
9	/nyc-bsa 1000770001 (BBL)
10	/nyc-bsa 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. BSA queries key on BBL; BIN resolution is only needed when the user's input was a BIN.
16
17	## Step 3: Query BSA Applications
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 by BBL first:
22	```
23	https://data.cityofnewyork.us/resource/yvxd-uipr.json?$where=bbl='{BBL}'&$order=date DESC
24	```
25
26	If no results, try address fallback:
27	```
28	https://data.cityofnewyork.us/resource/yvxd-uipr.json?$where=upper(street_name) LIKE '%{STREET}%' AND borough='{BOROUGH}'&$order=date DESC
29	```
30
31	Key fields: `application`, `section`, `status`, `date`, `street_number`, `street_name`, `bbl`, `borough`, `decisions_url`, `project_description`
32
33	## Step 4: Print Results
34
35	```markdown
36	## BSA Variances & Special Permits — {Address}
37
38	\| Application # \| Section \| Status \| Date \| Description \| Decisions \|
39	\|---------------\|---------\|--------\|------\|-------------\|-----------\|
40	\| {application} \| {section} \| {status} \| YYYY-MM-DD \| {project_description} \| {decisions_url} \|
41
42	Note: Approved variances remain with the land. Check if conditions affect proposed work.
43
44	Source: [BSA Applications](https://data.cityofnewyork.us/City-Government/BSA-Applications-Status/yvxd-uipr)
45	```
46
47	If no applications found: "No BSA applications found for this property (records from 1998-present)."
48
49	### Conventions
50	- All dates: YYYY-MM-DD
51	- If Socrata returns empty array: "No results found"
52	- If HTTP error: note it and suggest checking the address
53	- If the user requests, write results to a file
54
55	## Final Step: Disclaimer + Marker (required)
56
57	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:
58
59	```markdown
60	> 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.
61
62	<!-- architecture-studio:requires-disclaimer -->
63	```
64
65	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-bsa

260stars54forks

View on GitHub

How to install nyc-bsa?

alpacalabsllc/skills-for-architects/nyc-bsa

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# /nyc-bsa — BSA Variances & Special Permits
2
3	Look up Board of Standards and Appeals (BSA) applications, variances, and special permits for any NYC property. Records available from 1998 to present. No API key required.
4
5	## Usage
6
7	```
8	/nyc-bsa 120 Broadway, Manhattan
9	/nyc-bsa 1000770001 (BBL)
10	/nyc-bsa 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. BSA queries key on BBL; BIN resolution is only needed when the user's input was a BIN.
16
17	## Step 3: Query BSA Applications
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 by BBL first:
22	```
23	https://data.cityofnewyork.us/resource/yvxd-uipr.json?$where=bbl='{BBL}'&$order=date DESC
24	```
25
26	If no results, try address fallback:
27	```
28	https://data.cityofnewyork.us/resource/yvxd-uipr.json?$where=upper(street_name) LIKE '%{STREET}%' AND borough='{BOROUGH}'&$order=date DESC
29	```
30
31	Key fields: `application`, `section`, `status`, `date`, `street_number`, `street_name`, `bbl`, `borough`, `decisions_url`, `project_description`
32
33	## Step 4: Print Results
34
35	```markdown
36	## BSA Variances & Special Permits — {Address}
37
38	\| Application # \| Section \| Status \| Date \| Description \| Decisions \|
39	\|---------------\|---------\|--------\|------\|-------------\|-----------\|
40	\| {application} \| {section} \| {status} \| YYYY-MM-DD \| {project_description} \| {decisions_url} \|
41
42	Note: Approved variances remain with the land. Check if conditions affect proposed work.
43
44	Source: [BSA Applications](https://data.cityofnewyork.us/City-Government/BSA-Applications-Status/yvxd-uipr)
45	```
46
47	If no applications found: "No BSA applications found for this property (records from 1998-present)."
48
49	### Conventions
50	- All dates: YYYY-MM-DD
51	- If Socrata returns empty array: "No results found"
52	- If HTTP error: note it and suggest checking the address
53	- If the user requests, write results to a file
54
55	## Final Step: Disclaimer + Marker (required)
56
57	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:
58
59	```markdown
60	> 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.
61
62	<!-- architecture-studio:requires-disclaimer -->
63	```
64
65	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