Back to browse
GitHub Repository

SF Civic Intelligence Skill

5 starsPython

An agent skill that tracks SF city hearings, permits, lobbying etc.

by sgillen·Mar 31, 2026·1 point·0 comments

AI Analysis

●●SolidNiche GemBig Brain

Pulls from 22 local data sources including Planning Commission hearings and eviction notices.

Strengths
  • Aggregates fragmented civic data layers: permits, lobbying contacts, 311 requests, supervisor votes.
  • All 11 supervisorial districts supported with neighborhood-specific filtering and alerts.
  • Honest limitations documented: RSS feeds cover ~3 weeks, some sources still missing.
Weaknesses
  • SF-only scope limits audience; doesn't generalize to other cities without重写.
  • OpenClaw skill framework has limited adoption compared to mainstream agent platforms.
Category
Target Audience

SF residents, housing advocates, local civics participants

Similar To

OpenCivic · Placer.ai · Local government transparency dashboards

Post Description

I was frustrated not knowing where decisions that affect me were being made, or how my city government actually works. Why has 400 Divisadero been an abandoned car wash for years? Who decides what art to put in Golden Gate Park? I didn't know, but I wanted to, and I wanted to move the needle on issues I care about. I wanted to show up and advocate for more housing.

So to help with that I built this OpenClaw skill, it pulls from 22 government data sources and synthesizes them according to my own interests. It has allowed me to understand better how my local government actually works, and now gives me a weekly update on upcoming town halls, trash pickups, and other events I might want to attend.

I'm relatively new to the world of civics, discussions and contributions are more than welcome.

Similar Projects

Developer Tools●●Solid

Agnix – lint your AI agent configs (Claude.md, skills, MCP, hooks)

Makes agent configs first-class with 229 domain-specific rules, autofix, and LSP support — so a tiny syntax mistake stops being a silent failure. The cross-editor plugins and GitHub Action are the standout moves: lint in your IDE and enforce checks in CI. I want a clearer map of which rules target which toolchains, but the breadth of integrations is impressive.

Niche GemSolve My ProblemSlick
anotherCodder
113mo ago