Skip to content

搵技能.../

Agent Skill Search Engine

搜尋

搜尋
分類
職業

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

Compare | Skills Pool

技能檔案

Compare

Find connections between civic problems — do crashes happen where pavement is worst? Do complaints match what imagery shows? Compare data across cities.

roadgnar0 星標2026年3月28日

職業
分類: 除錯

技能內容

Compare — Cross-Source and Cross-City Analysis

Find connections between different civic datasets or compare the same metric across cities.

Two Supported Patterns

Pattern A: Same City, Two Data Types

Examples: crashes + pavement quality, 311 complaints + street imagery, housing violations + demographics

Workflow:

Identify the two data sources needed
Query each source independently
Join results by coordinates (within ~200m) or by neighborhood/area name
Present side-by-side with a "what this means" summary

Pattern B: Same Topic, Two Cities

Examples: NYC vs Boston 311 volume, population trends, restaurant inspection rates

Workflow:

Query each city's MCP for the same metric
Use Data Commons get_observations for population to normalize per-capita

相關技能

快速安裝

Compare

npx skillvault add roadgnar/roadgnar-mcp-demo-claude-skills-compare-skill-md

下載 Skill 打開源碼倉庫

作者: roadgnar
星標: 0
更新時間: 2026年3月28日
職業

本頁內容

01Compare — Cross-Source and Cross-City Analysis

Present a comparison table with raw numbers AND per-capita rates

Note differences in how each city collects/categorizes the data

Supported Comparisons (not exhaustive)

Crashes and bad pavement: Cyvl pavement scores + Boston crash data
311 complaints and actual conditions: Socrata/Boston 311 + Cyvl imagery
NYC vs Boston on any metric: Socrata + Boston open data + Data Commons
Housing violations and demographics: Socrata housing data + Data Commons income/population
Complaints over time vs construction activity: 311 data + work zone permits

Presenting Results

Always include these three sections:

Side-by-side data — table or paired bullet points showing both sources
The connection — one paragraph on what the correlation suggests in plain language
Caveats — correlation is not causation, note any data gaps (date ranges differ, categories don't map perfectly, coverage area mismatch)

Rules

Always normalize cross-city comparisons by population (use Data Commons Count_Person)
Discover columns before querying — never assume column names
When joining by location, state the matching radius used
Cite every number's source: which MCP and which dataset
If one data source is empty or unavailable, present what you have and note the gap

02

Two Supported Patterns

03Pattern A: Same City, Two Data Types

04Pattern B: Same Topic, Two Cities

05Supported Comparisons (not exhaustive)

06Presenting Results

Urban and Regional Planners

Session Logs

Search and analyze your own session logs (older/parent conversations) using jq.

OpenClaw Test Heap Leaks

Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.

Node Connect

Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

Openclaw Qa Testing

Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.

Openclaw Secret Scanning Maintainer

Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.

Flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

Urban and Regional Planners