AlpacaLabsLLC/skills-for-architects / skills/nyc-property-report
nyc-property-report
VerifiedCompile NYC landmarks, DOB, ACRIS, HPD, and BSA findings into one property due-diligence report. Use for a full report; use individual NYC skills for one dataset.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 336 B |
| SKILL.md | skill md | 5.9 KB |
| host-contract.json | config | 1.7 KB |
| pluto-resolution.md | markdown | 1.3 KB |
| socrata-reference.md | markdown | 1.4 KB |
pluto-resolution.md
View on GitHub# NYC property identity procedure
Before querying, use the [geographic contract](../../docs/geographic-applicability.md) and the selected skill's [declaration](../../corpus/geographic-applicability.json). Require a resolved NYC target from supplied or relevant project evidence. A bare numeric identifier or studio default does not resolve a contradictory/missing jurisdiction. One-off lookups need no project setup.
Accept the supplied address, parcel/building identifier or exact selected source record. Use the PLUTO and Building Footprints routes in the [source catalog](../../corpus/sources/catalog.json); retrieve their current original metadata before interpreting identifiers, columns, normalization or relationships. Use the [query procedure](socrata-reference.md). Preserve the original input and matched source identity.
Try the most specific supplied identity first. Normalize only according to verified source requirements. An address match may be ambiguous; present candidate identities and ask for the material choice. Do not silently merge multiple lots/buildings or pick a first match. Resolve the selected parcel/building relationship from actual publisher fields and retain multiple mappings if the requested scope includes them. Missing or conflicting evidence leaves the identity unresolved. Collect only fields relevant to the requested report.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |