Agent skill · Workflow & Productivity

report-a-hazard

Report a public hazard or code problem to the authority that can actually fix it — a pothole, broken streetlight, illegal dump, unsafe building, code violation, blocked drain — with the right department, the details that get it actioned, a tracking reference, and an escalation path if it's ignored. Use when someone says 'how do I report a pothole/hazard/violation', 'the council won't fix X', or 'who do I call about Y'. Produces a report ready to submit, the right channel, and a follow-up plan.

mohitagw158561,255★ · 1 repos on radarProfile →
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill report-a-hazard --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/report-a-hazard/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Report A Hazard Skill Reporting a public problem should be simple and usually isn't: the report goes to the wrong department, lacks the details needed to action it, or vanishes with no reference number, so nothing happens and the reporter gives up. Councils and agencies *do* fix things — they fix the reports that land in the right queue with a precise location, evidence, and a hazard framing that raises the priority. This skill writes that report, routes it to the channel that owns it, captures a tracking reference, and sets up the escalation for when the first report is ignored. ## What This Skill Produces - The **right channel**: which department/agency owns this problem and the best way to reach them (the official app/portal/line — many places have a dedicated report-it system) - A **submit-ready report**: precise location, what/when/how-bad, a safety framing where genuine, and a photo checklist — the details that move it from "logged" to "scheduled" - A **tracking plan**: getting a reference number and what response time is reasonable before chasing - An **escalation path**: what to do if it's ignored or bounced — re-report with the reference, go to the supervisor/councillor,

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework
  4. Output Format
  5. Quality Checks
  6. Anti-Patterns
  7. Related
More from pm-claude-skills
All skills →
About this skill
What does the report-a-hazard skill do?

Report a public hazard or code problem to the authority that can actually fix it — a pothole, broken streetlight, illegal dump, unsafe building, code violation, blocked drain — with the right department, the details that get it actioned, a tracking reference, and an escalation path if it's ignored. Use when someone says 'how do I report a pothole/hazard/violation', 'the council won't fix X', or 'who do I call about Y'. Produces a report ready to submit, the right channel, and a follow-up plan.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill report-a-hazard --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going