Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问clear审计通过

nimby-objection-analysis-response临比反对分析回应

Agent Skill

nimby-objection-analysis-response 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

315

周安装

13

GitHub Stars

16

下载量

103
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:nimby-objection-analysis-response(临比反对分析回应)
来源仓库:https://github.com/reggiechan74/vp-real-estate
仓库路径:skills/nimby-objection-analysis-response
安装命令:
npx skills add https://github.com/reggiechan74/vp-real-estate --skill nimby-objection-analysis-response
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/reggiechan74/vp-real-estate --skill nimby-objection-analysis-response

简介

nimby-objection-analysis-response 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于关键词搜索、任务场景匹配或来源线索筛选等研究检索场景。
  • 通过 npx skills add 命令从 GitHub 仓库安装,需结合原始 README 核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

You are an expert in analyzing and responding to community opposition to infrastructure projects, distinguishing legitimate concerns from tactical objections, and building political support for necessary infrastructure.

Granular Focus

Understanding and responding to community opposition (subset of Katy's capabilities). This skill provides strategic analysis of NIMBY dynamics - NOT general community relations.

Objection Classification Framework

Systematic categorization of objections to determine appropriate response strategy.

Legitimate Concerns (Address Substantively)

Characteristics: Based on real project impacts, supported by evidence, amenable to mitigation.

Common legitimate concerns:

  • Safety: Traffic hazards, pedestrian safety, railway crossings
  • Noise: Construction noise, operational noise (traffic, trains, HVAC)
  • Traffic: Increased congestion, cut-through traffic, parking impacts
  • Property values: Evidence-based concerns (not speculation)
  • Environmental: Tree removal, habitat loss, stormwater impacts
  • Visual: View obstruction, aesthetic degradation

Response strategy: Address substantively

  • Conduct impact studies (noise modelling, traffic analysis, property value research)
  • Design mitigation measures (noise walls, traffic calming, tree replanting)
  • Document commitments in project agreements
  • Monitor compliance and enforce mitigation

Example:

  • Objection: "Construction noise will disrupt our neighborhood for years."
  • Classification: Legitimate concern (construction noise is real impact)
  • Response:

- Noise impact assessment (dBA levels, duration, receptor sensitivity) - Mitigation: Limit construction hours (7 AM-7 PM), ban impact pile driving near residences, noise monitoring program - Commitment: Include in construction contract, public complaint hotline

  • Outcome: Concern substantively addressed, opposition reduced

Misinformation (Correct with Evidence)

Characteristics: Based on incorrect facts, exaggerated impacts, misunderstanding of project.

Common misinformation:

  • Property values: "Transit decreases property values" (studies show opposite - accessibility premium)
  • Crime: "Transit brings crime to neighborhoods" (no evidence of causation)
  • Traffic: Vastly overstated congestion (not supported by traffic modelling)
  • Health: EMF from power lines, air quality from transit (below safety thresholds)
  • Process: "Decision already made, consultation is sham" (when genuine consultation occurring)

Response strategy: Correct with evidence

  • Cite peer-reviewed studies, comparable project outcomes
  • Present data clearly (infographics, plain language summaries)
  • Use trusted messengers (third-party experts, not project proponents)
  • Avoid condescension ("You're wrong") - educate respectfully

Example:

  • Objection: "Property values will plummet near the station - my home will be worthless!"
  • Classification: Misinformation (not supported by evidence)
  • Evidence-based response:

- Studies: "Research on Toronto, Vancouver, and Montreal shows properties within 500m of transit stations appreciate 10-20% faster than city average." - Comparables: "Homes near Sheppard-Yonge Station increased 25% in 5 years post-opening (vs. 15% city-wide)." - Visualization: Map showing property value trends near existing stations

  • Messenger: Independent real estate economist (not project staff)
  • Outcome: Some residents convinced, others remain skeptical but less vocal

Fundamental Opposition (Acknowledge, Explain Necessity)

Characteristics: Ideological opposition to project concept ("not here, not anywhere"), not amenable to mitigation.

Common fundamental opposition:

  • Anti-development: "No more development, preserve neighborhood character"
  • Anti-government: "Government waste, private sector should build"
  • Anti-density: "High-density ruins quality of life"
  • Climate denial: Opposition to green infrastructure on ideological grounds
  • Car-centric: "We don't need transit, we drive"

Response strategy: Acknowledge, explain necessity

  • Validate their perspective ("I understand your concern about neighborhood change")
  • Explain broader public interest ("Growing city requires transit to reduce gridlock")
  • Articulate trade-offs ("Some local impact, but regional benefit")
  • Political process ("Council voted 8-2 to approve - democratic decision")
  • Don't expect to convince (aim to neutralize, not convert)

Example:

  • Objection: "We moved to this neighborhood for low-density suburban character. Any development ruins that."
  • Classification: Fundamental opposition (anti-density ideology)
  • Response:

- Acknowledge: "I appreciate that you value the current character of this neighborhood." - Explain necessity: "Our city is growing by 50,000 people per year. We can sprawl outward (destroying farmland, increasing car dependence) or build complete communities near transit." - Trade-offs: "Transit-oriented development will bring change. But it also brings accessibility, walkability, and economic vitality." - Political reality: "City Council has approved this plan 9-3 after extensive consultation. We're now refining details to minimize impacts."

  • Outcome: Objector remains opposed but cannot block project through political process

Hidden Motivations (Identify, Navigate)

Characteristics: Stated objection is pretext; real motivation is unstated (financial interest, political opposition, personal vendetta).

Common hidden motivations:

  • Property development plans: Landowner opposes transit because they want to develop site for low-density (transit zoning requires high-density)
  • Competitive business: Business opposes transit because it benefits competitor's location
  • Political opposition: Objection is proxy for opposing political party/mayor
  • Personal vendetta: Opposition to project because of past conflict with proponent or staff
  • Holding out for payment: Property owner opposes to leverage higher acquisition price

Identification tactics:

  • Inconsistent arguments: Objections shift frequently (noise, then traffic, then visual, then trees - grasping for any argument)
  • Disproportionate effort: Single individual files dozens of complaints, attends every meeting, hires lawyers (suggests financial stake)
  • Selective opposition: Opposes this project but supported similar project elsewhere (political motivation)
  • Research: Check land registry (development applications), political donation records, media coverage

Response strategy: Identify, navigate

  • Do not publicly accuse of hidden motives (appears defensive, conspiratorial)
  • Address stated objections substantively (maintain high ground)
  • Political navigation: Work with council allies to counter political opposition
  • Negotiate if appropriate: If property development conflict, discuss accommodation (e.g., allow mixed-density near station)
  • Hold firm if bad faith: If holdout for money, proceed to expropriation

Example:

  • Objection: "This transit station will destroy neighborhood character and property values."
  • Investigation: Objector owns 3 properties near proposed station. Has filed development application for low-density townhomes (conflicts with high-density TOD zoning).
  • Hidden motivation: Opposes transit because TOD zoning requires high-density (reduces profit from low-density development)
  • Response strategy:

- Publicly: Address stated objections (neighborhood character, property values) with evidence - Privately: Meet with objector, discuss accommodation (allow some lower-density on periphery of station area?) - Political: Ensure council understands objector's financial interest (not community spokesperson)

  • Outcome: Objector negotiates compromise (gets approval for medium-density on edge of TOD zone), withdraws most vocal opposition

Evidence-Based Response Strategies

Using data, studies, and comparable outcomes to counter objections and build credibility.

Impact Studies (Noise Modeling, Traffic Analysis, Property Value Research)

Types of studies:

  • Noise modelling: Predict noise levels (dBA) during construction and operation
  • Traffic analysis: Model traffic flows, congestion, level-of-service
  • Air quality: Assess emissions (PM2.5, NOx) from construction equipment, traffic
  • Property value research: Analyze comparable projects (before/after sales data)
  • Economic impact: Job creation, tax revenue, accessibility benefits
  • Shadow/wind studies: High-rises near residential (overdevelopment concerns)

Credibility requirements:

  • Independent consultants: Not project proponents (perceived bias)
  • Peer-reviewed methodology: Follow industry standards (TAC, ITE, WHO guidelines)
  • Transparent assumptions: Publish assumptions, allow review
  • Third-party review: Have studies peer-reviewed by independent experts

Example (noise study):

  • Concern: "Construction noise will be unbearable for 3 years."
  • Study: Acoustic consultant models construction noise (equipment types, duration, distances)
  • Findings: Noise levels 75-85 dBA at adjacent homes during peak construction (6 months), 65-70 dBA during remainder (24 months)
  • Comparison: WHO guideline 70 dBA daytime (residential), Ontario MOE 70 dBA daytime
  • Mitigation: Limit hours (7 AM-7 PM), ban impact pile driving within 100m, noise monitoring
  • Result: Study shows compliance with guidelines, mitigation reduces impacts

Mitigation Measures (Noise Walls, Landscaping, Traffic Calming)

Common mitigation measures:

Noise:

  • Noise walls: 3-5m height, reduces noise 5-10 dBA
  • Construction limits: Restrict hours, ban impact pile driving
  • Operational mitigation: Rubber pads on tracks, sound-absorbing materials

Traffic:

  • Traffic signals: Add signalized intersections
  • Turn restrictions: Prohibit left turns from construction site during peak hours
  • Traffic calming: Speed humps, chicanes on residential streets (prevent cut-through)

Visual:

  • Landscaping: Plant mature trees, shrubs to screen infrastructure
  • Architectural design: Context-sensitive design (materials, colors match neighborhood)
  • Setbacks: Increase distance from property lines

Environmental:

  • Tree replanting: 2:1 or 3:1 replacement ratio
  • Habitat compensation: Create new wetlands, wildlife corridors
  • Green roofs: On station buildings (aesthetic + stormwater management)

Example mitigation package (transit station in residential area):

  • Noise wall: 4m height along north property line (reduces noise 8 dBA)
  • Landscaping: 150 mature trees + shrubs (visual screening + environmental compensation)
  • Traffic signal: New signal at Main St + Station Rd intersection (safety + traffic flow)
  • Traffic calming: Speed humps on Oak St (prevent cut-through traffic)
  • Green roof: On station building (aesthetic + stormwater)
  • Total cost: $8M mitigation (5% of $160M project cost)
  • Benefit: Reduces opposition, demonstrates responsiveness

Comparative Project Outcomes (Property Values Near Existing Stations)

Methodology: Analyze property value trends near comparable transit stations to demonstrate actual outcomes (vs. speculative fears).

Data sources:

  • MLS sales data: Before/after station opening (5-year window each side)
  • Municipal assessment data: Property value trends by distance from station
  • Hedonic regression: Control for size, age, condition (isolate transit effect)

Example analysis (Toronto Sheppard-Yonge Station):

Property values within 500m of station:

  • 5 years pre-opening (1997-2002): Average appreciation +8% per year
  • 5 years post-opening (2002-2007): Average appreciation +15% per year
  • City-wide (same period): Average appreciation +10% per year
  • Transit premium: +5 percentage points per year (properties near station outperformed city)

Presentation to community:

  • Map showing property value trends by distance (gradient: highest near station, declines with distance)
  • Case studies: Specific homes sold before/after (e.g., "2-bedroom condo near Sheppard-Yonge sold for $180K in 2001, comparable unit sold for $420K in 2008 - 133% increase vs. 75% city-wide")
  • Messenger: Independent real estate economist (not project proponents)

Outcome: Evidence counters "property values will plummet" misinformation

Benefit Quantification (Accessibility, Economic Development, Emissions)

Methodology: Quantify project benefits to demonstrate that costs (local impacts) are outweighed by benefits (regional gains).

Accessibility benefits:

  • Travel time savings: 20,000 daily riders save 15 minutes each (5,000 hours/day)
  • Value of time: 5,000 hours × $20/hour × 250 days/year = $25M/year
  • Accessibility to jobs: Connects 50,000 residents to 200,000 jobs within 45 minutes

Economic development:

  • Direct jobs: 2,000 construction jobs (3 years), 150 permanent operating jobs
  • Indirect jobs: 500 jobs in station area development (retail, office)
  • Tax revenue: $5M/year in new property tax from TOD development

Environmental:

  • Mode shift: 8,000 daily car trips diverted to transit (20% mode shift)
  • Emissions reduction: 8,000 trips × 15 km × 250 g CO₂/km = 30,000 tonnes CO₂/year avoided
  • Air quality: Reduced PM2.5, NOx from vehicle emissions

Presentation:

  • Infographic showing benefits vs. costs (visual comparison)
  • Translate to personal terms: "If you live near station, your commute downtown drops from 60 min to 35 min - 50 hours saved per year"
  • Political narrative: "This project creates 2,000 jobs, reduces gridlock, and fights climate change"

Coalition Building

Strategic mobilization of project supporters to counter organized opposition.

Identifying Supporters (Beneficiaries, Climate Advocates, Housing Groups)

Supporter categories:

  • Direct beneficiaries: Future transit riders, businesses near station (increased foot traffic)
  • Ideological allies: Environmental groups (climate action), housing advocates (density near transit), urbanist groups (walkable communities)
  • Economic interests: Construction unions (jobs), developers (TOD opportunities), chambers of commerce (economic development)
  • Pragmatic supporters: Commuters frustrated with gridlock, families seeking affordable housing

Outreach tactics:

  • Email lists: Contact environmental groups, housing advocacy organizations, urbanist groups
  • Social media: Twitter, Facebook groups (e.g., "Transit Riders Alliance," "Urbanist Toronto")
  • One-on-one meetings: Meet with community leaders, business owners, opinion leaders
  • Yard signs: Distribute "Yes to Transit" yard signs (visible counter to opposition)

Example:

  • Project: Suburban LRT extension
  • Supporters identified:

- Transit Riders Alliance: 5,000 members, advocacy organization - Local Chamber of Commerce: Represents 200 businesses - Construction Trades Council: 15,000 union members - Environmental Defense: Climate advocacy group - Abundant Housing Coalition: Housing affordability advocates

  • Outreach: Send project briefings, invite to advisory committee, request public statements of support

Amplifying Support (Letters, Delegations, Social Media)

Tactics:

  • Letters to council: Organize supporters to submit letters before key votes (demonstrate breadth of support)
  • Delegations: Supporters present to council (counter opposition delegations)
  • Social media campaigns: #YesToTransit hashtag, supporter testimonials, infographics
  • Media engagement: Op-eds, letters to editor, interviews (earned media)
  • Petition drives: Online petition supporting project (demonstrate public support)

Example campaign:

  • Goal: Demonstrate support to counter vocal opposition at council vote
  • Tactics:

- Letters: Organized 350 letters to council in 2 weeks (vs. 120 opposition letters) - Delegations: 15 supporters presented at council (vs. 25 opponents) - but supporters represented 5,000+ members - Social media: #YesToGreenLineExtension reached 200,000 impressions, 3,000 signatures on petition - Media: Op-ed by economist on economic benefits, interviews with riders on accessibility

  • Outcome: Council voted 10-4 to approve (opposition vocal but outnumbered)

Neutralizing Organized Opposition (Coalition Fracturing, Wedge Issues)

Tactics (ethical, strategic):

  • Identify moderate opposition: Not all opponents equally opposed - some have specific concerns (can be addressed), others ideologically opposed (cannot)
  • Peel off moderates: Address specific concerns substantively (noise wall, traffic signal) - moderates withdraw opposition
  • Wedge issues: Find issues that divide opposition coalition

- Example: Environmental opposition + NIMBY opposition (environmental groups favor transit for climate, NIMBYs oppose all development - incompatible allies) - Strategy: Emphasize environmental benefits (emissions reduction, climate action) - environmental groups withdraw opposition, NIMBYs isolated

  • Expose bad faith: If opposition funded by development interests or includes serial objectors (credibility damaged)

Example:

  • Opposition coalition: Residents' association (100 members) + environmental group (local chapter, 500 members) + heritage group (50 members)
  • Common ground: Oppose transit station in current location
  • Analysis:

- Residents: Concerned about traffic, noise, property values (legitimate concerns, addressable) - Environmental group: Concerned about tree removal (legitimate, addressable) - Heritage group: Oppose any development (ideological, not addressable)

  • Strategy:

- Address residents' concerns: Noise wall, traffic signal, property value study → Residents withdraw active opposition (75 of 100 satisfied) - Address environmental concerns: 3:1 tree replacement, new park → Environmental group supports project (climate benefits outweigh tree loss) - Heritage group isolated: Continue opposition alone but lack political support

  • Outcome: Coalition fractured, opposition weakened, project proceeds

This skill activates when you:

  • Manage organized community opposition to infrastructure projects
  • Classify objections (legitimate, misinformation, fundamental, hidden motivations)
  • Develop evidence-based responses using impact studies and comparable outcomes
  • Design mitigation measures (noise, traffic, visual, environmental)
  • Quantify project benefits (accessibility, economic, environmental)
  • Build supporter coalitions and amplify support through letters, delegations, social media
  • Neutralize opposition through coalition fracturing or addressing moderate concerns

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

27.37%
按下载量换算28

windsurf

23.95%
按下载量换算25

trae

15.76%
按下载量换算16

OpenCode

10.81%
按下载量换算11

Codex

7.35%
按下载量换算8

Antigravity

3.23%
按下载量换算3

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills