AgentStack
SKILL verified MIT Self-run

Site Analysis

skill-amanbh997-urban-design-skills-claude-site-analysis · by Amanbh997

>-

No reviews yet
0 installs
7 views
0.0% view→install

Install

$ agentstack add skill-amanbh997-urban-design-skills-claude-site-analysis

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Site Analysis? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Site Analysis Skill

Comprehensive multi-scale site analysis for urban design and architectural projects. This skill guides the systematic evaluation of a site and its context across three nested scales, twelve analytical layers, and a structured synthesis framework that translates raw data into actionable design implications.


1. Three-Scale Analysis Framework

Every site exists within nested contexts. Effective analysis moves from the broad regional frame down to the specific parcel, ensuring that no critical external force is overlooked before design begins.

Decision Tree for Analysis Depth

START
  |
  v
Is the project a masterplan, new neighborhood, or infrastructure project?
  YES --> Conduct FULL three-scale analysis (Regional + Neighborhood + Site)
  NO  --> Continue
  |
  v
Is the project an infill building, renovation, or single-parcel development?
  YES --> Conduct TWO-SCALE analysis (Neighborhood + Site)
  NO  --> Continue
  |
  v
Is the project an interior renovation or tenant fit-out?
  YES --> Conduct SITE-SCALE analysis only (immediate context + parcel)
  NO  --> Default to TWO-SCALE analysis

Regional Scale (5 km - 50 km radius)

Purpose: Understand the site's position within metropolitan systems.

  • Transportation networks: highways, rail corridors, airports, ports, and

their capacity/planned upgrades. Identify the site's travel-time isochrones to major employment centers (15 min, 30 min, 60 min by car and transit).

  • Economic clusters: major employers, industry sectors, university and

hospital anchors, innovation districts, and economic development zones.

  • Environmental systems: regional watersheds, river basins, protected

landscapes, green belts, agricultural land, air quality zones, and climate risk areas (sea-level rise, wildfire, seismic).

  • Governance: municipal boundaries, special districts, regional planning

authorities, tax increment financing zones, enterprise zones.

  • Regional position: Is the site in a growth corridor, a stable suburb, a

declining industrial area, or a rural fringe? What regional plans affect it?

Neighborhood Scale (500 m - 2 km radius)

Purpose: Map the immediate urban fabric the project must integrate with.

  • Street network morphology: grid, organic, cul-de-sac, superblock. Measure

intersection density (target: >100 per km2 for walkable areas), block size distribution, and connectivity index.

  • Land use patterns: dominant uses, mix ratio, distribution of commercial

frontage, location of institutional anchors, vacant or underutilized parcels.

  • Demographics: population density, age pyramid, household composition,

income brackets, ethnic diversity, education attainment within the walkshed.

  • Amenities and services: schools, parks, healthcare, grocery, transit

stops. Map 5-minute (400 m) and 10-minute (800 m) walksheds to each.

  • Character areas: identify distinct sub-areas by building typology, street

character, era of development, and perceived identity. Name each area.

Site Scale (The Parcel)

Purpose: Document every physical and perceptual attribute of the land itself.

  • Physical attributes: area (m2 and hectares), dimensions, shape regularity,

elevation range, slope and aspect, soil type, bearing capacity.

  • Edges and boundaries: describe each edge (street, party wall, open space,

water body). Note edge conditions: hard/soft, public/private, active/passive.

  • Access points: existing vehicular curb cuts, pedestrian entries, potential

new access points, visibility from approaching routes.

  • Microclimate: on-site sun/shadow patterns at winter solstice, equinox,

and summer solstice at 9:00, 12:00, and 15:00. Wind exposure vs. shelter. Identify frost pockets, heat traps, and comfortable outdoor zones.

  • Views: catalog views OUT from the site (desirable and undesirable) and

views IN to the site from public vantage points. Note landmark visibility.

  • Existing structures: buildings, walls, fences, paving, underground

structures, foundations, contamination history, demolition requirements.


2. Analysis Workflow

Follow this 10-step sequential workflow. Each step builds upon the previous. Do not skip steps; mark any step "Not Applicable" with justification if data is unavailable.

Step 1: Define Study Area Boundaries at Each Scale

  • Draw the site boundary (red line) from cadastral/parcel data.
  • Define the neighborhood study area (typically 800 m walkshed from site

centroid, adjusted for barriers like highways or rivers).

  • Define the regional study area (typically the metropolitan statistical area

or the commuter catchment, whichever is more relevant).

  • Document the coordinate reference system (e.g., WGS 84, UTM zone).
  • Record site area in both metric (m2, hectares) and imperial (sq ft, acres).

Step 2: Physical Context

  • Topography: obtain DEM or contour data. Calculate slope in percent.

Classify: 0-2% flat, 2-5% gentle, 5-10% moderate, 10-15% steep, >15% very steep. Map aspect (N/S/E/W facing).

  • Hydrology: map water bodies, watercourses, flood zones (100-year and

500-year), drainage direction, watershed boundaries, groundwater depth.

  • Vegetation: identify tree canopy coverage (%), significant trees (trunk

diameter >30 cm), protected habitats, invasive species.

  • Soil and geology: soil type, bearing capacity, contamination risk,

bedrock depth, seismic classification.

Step 3: Infrastructure Audit

  • Water supply: nearest main, pipe diameter, pressure, capacity for

projected demand. Fire flow requirements.

  • Sanitary sewer: nearest main, depth, capacity, treatment plant capacity.

Note combined vs. separate storm sewer.

  • Electrical: nearest substation, available capacity (kVA), voltage,

planned upgrades. Assess renewable energy potential.

  • Telecommunications: fiber availability, 5G coverage, data center

proximity for smart building applications.

  • District systems: district heating/cooling if available. Proximity to

waste-to-energy or renewable energy sources.

Step 4: Regulatory Review

  • Zoning: current zone designation, permitted uses (by right and by

special permit), density limits (FAR and units/hectare), height limits, setback requirements, parking minimums/maximums.

  • Building codes: applicable building code edition, fire code, energy

code, accessibility code.

  • Overlay districts: historic preservation, design review, environmental

protection, transit-oriented development, planned unit development.

  • Heritage: listed buildings on or adjacent to site, conservation area

status, archaeological potential.

  • Planned changes: pending rezoning applications, comprehensive plan

future land use designation, infrastructure improvement plans.

Step 5: Environmental Conditions

  • Sun path: document solar altitude and azimuth at solstices and equinoxes

at 9:00, 12:00, and 15:00 local time. Calculate hours of direct sunlight on site at winter solstice (critical for northern/southern latitudes).

  • Wind: obtain wind rose data (ideally 10+ years). Identify prevailing

wind direction by season. Note wind speed distribution. Identify potential channeling effects from surrounding buildings or topography.

  • Noise: identify sources (roads by ADT classification, rail, airports,

industrial). Estimate noise levels at site boundary in dB(A). Note any noise ordinance thresholds.

  • Air quality: check AQI monitoring data for the area. Identify point

sources of pollution. Note prevailing wind direction relative to sources.

  • Flood risk: FEMA (US) or equivalent flood zone designation. Map 100-year

and 500-year flood extents on site plan.

Step 6: Socio-Economic Profile

  • Demographics: total population within walkshed, growth rate (5-year and

projected), age distribution, household size, ethnic composition.

  • Income: median household income, income distribution quintiles, poverty

rate, comparison to metro median.

  • Housing: housing tenure (own/rent), vacancy rate, median home value,

median rent, housing cost burden (% spending >30% on housing).

  • Employment: employment rate, major employers, commute patterns (mode

share), job-housing balance ratio.

  • Growth projections: projected population and employment growth for the

area over 5, 10, and 20 years from official planning documents.

Step 7: Movement Analysis

  • Vehicular: road classification (arterial, collector, local), ADT counts,

LOS at key intersections, planned road projects, speed limits.

  • Pedestrian: sidewalk inventory (width, condition, ADA compliance),

crossing facilities, pedestrian counts if available, Walk Score.

  • Cycling: existing cycling infrastructure (protected, painted, shared),

bike share stations, Bike Score, planned cycling projects.

  • Transit: routes serving the site, frequency (peak and off-peak),

ridership, distance to nearest stop/station, Transit Score, planned service changes or new lines.

  • Freight and servicing: truck routes, loading zones, waste collection

access, emergency vehicle access.

Step 8: Visual and Character Assessment

  • Serial vision walk: conduct a Cullen-method serial vision analysis along

the primary approach routes to the site. Document the sequence of existing views, enclosure, deflection, and anticipation.

  • Landmark views: identify and photograph key views TO the site and FROM

the site. Note any protected view corridors.

  • Character areas: map distinct character areas in the neighborhood.

Document prevailing materials, colors, heights, setbacks, roof forms.

  • Edges and thresholds: identify hard edges (highways, rail), soft edges

(parks, waterfronts), and transition zones. Map gateways and nodes.

  • Sense of place: qualitative assessment of the genius loci. What makes

this place distinctive? What should be preserved, enhanced, or transformed?

Step 9: Stakeholder and Community Mapping

  • Landowners: site owner, adjacent landowners, major landholders in the

neighborhood study area.

  • Community groups: neighborhood associations, business improvement

districts, advocacy groups, cultural organizations.

  • Government agencies: planning department, transportation department,

environmental agencies, utilities, economic development office.

  • Institutional stakeholders: schools, hospitals, universities, religious

institutions, cultural institutions within the study area.

  • Political context: elected officials, upcoming elections, known positions

on development, relevant referenda or ballot measures.

Step 10: SWOT Synthesis and Design Implications

  • Strengths: list 5-8 site advantages that the design should leverage.
  • Weaknesses: list 5-8 site disadvantages that the design must mitigate.
  • Opportunities: list 5-8 external opportunities the project could capture.
  • Threats: list 5-8 external threats the project must defend against.
  • Design implications: translate each SWOT item into a specific design

response, categorized as:

  • Mandatory constraints (non-negotiable: zoning, flood zones, access)
  • Strong influences (should be respected: microclimate, character, views)
  • Opportunities (can be pursued: market gaps, connectivity improvements)

3. Layer-by-Layer Analysis Guide

Each of the 12 analysis layers below follows a consistent structure: what data to collect, what questions to answer, what metrics to apply, and how to synthesize findings into design implications.

Layer 1: Topography and Geomorphology

  • Data: DEM (1 m resolution preferred), contour maps, geological survey.
  • Questions: What is the elevation range? Where are the steepest slopes?

What is the dominant aspect? Are there ridgelines or valleys that create natural drainage or view corridors?

  • Metrics: slope percent by zone, aspect distribution, elevation range.

Cut-and-fill volume estimate for level pad scenarios.

  • Design implications: slopes 0-5% are ideal for building; 5-15% require

stepped foundations or retaining walls; >15% should be preserved as open space or used for dramatic architectural expression. South-facing slopes (northern hemisphere) receive more solar energy. Ridgelines offer views but wind exposure; valleys offer shelter but potential flooding.

Layer 2: Hydrology and Water Systems

  • Data: flood maps (FEMA/equivalent), watershed boundaries, watercourse

centerlines, groundwater monitoring data, stormwater infrastructure maps.

  • Questions: Is any part of the site in a flood zone? What is the drainage

direction? Where does stormwater go? What is groundwater depth?

  • Metrics: flood zone classification, drainage area contributing to site

(hectares), groundwater depth below grade, required stormwater detention volume per local code (typically 10-25 mm for first flush).

  • Design implications: flood zones constrain building placement. High

groundwater limits basement construction. Stormwater management can become an amenity (rain gardens, bioswales, constructed wetlands). Riparian buffers (typically 15-30 m from waterways) must be maintained.

Layer 3: Vegetation and Ecology

  • Data: aerial imagery, tree survey (species, DBH, canopy spread, health),

habitat maps, protected species records.

  • Questions: What percentage of the site is tree canopy? Are there

significant trees or habitats that must be protected? Are there ecological corridors that should be maintained or created?

  • Metrics: canopy cover (%), number of significant trees (DBH >30 cm),

biodiversity index, ecological connectivity score.

  • Design implications: mature trees add significant value and should be

retained where possible (each large tree provides ~$50-100/year in ecosystem services). Ecological corridors should be at least 10 m wide to be functional. Green infrastructure targets: 30% canopy cover, 15% permeable surface for new development.

Layer 4: Climate and Microclimate

  • Data: weather station data (10+ year records), sun path diagrams for

site latitude, wind rose data, temperature and humidity records.

  • Questions: How many hours of sun does the site receive in winter? What

are prevailing wind directions by season? Where are sheltered zones? Where are heat traps? What is the heating/cooling degree day balance?

  • Metrics: solar hours (winter solstice), prevailing wind speed and

direction, annual temperature range, heating degree days, cooling degree days, annual precipitation, design storm intensity.

  • Design implications: orient buildings and streets for solar access (east-

west street orientation maximizes south-facing frontage in northern hemisphere). Shelter outdoor spaces from prevailing cold-season winds. Use building mass to create wind shadows for plazas and parks. Maximize cross-ventilation in cooling-dominated climates.

Layer 5: Transportation and Access

  • Data: road network with classification, traffic counts (ADT), transit

maps and schedules (GTFS), cycling network maps, pedestrian counts.

  • Questions: What is the site's multimodal accessibility? Where are the

congestion points? What is the pedestrian quality of surrounding streets? What transit frequency serves the site?

  • Metrics: ADT on adjacent roads, intersection LOS, transit frequency

(vehicles/hour), Walk Score, Transit Score, Bike Score, distance to nearest transit stop (m), parking supply ratio (spaces per 1000 m2).

  • Design implications: high-frequency transit access (>10 vehicles/hour)

justifies reduced parking ratios. High ADT roads (>15,000) create noise and air quality barriers requiring building setbacks or noise walls. Pedestrian connectivity gaps reveal opportunities for new connections.

#

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.