speak-at-the-council
Turn three minutes at a council or community meeting into the version that actually moves the decision — a public comment built as ask-story-evidenc…
它会碰到什么
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
Speak At The Council Skill
Most public comments are three minutes of justified feeling aimed at a
decision that was effectively made two committee stages earlier. The
residents who win learned the machine: find where the decision actually is
in the process, speak to what the deciding body is allowed to consider, bring
neighbors so it reads as "residents" not "a resident," and hand over a
one-pager — because minutes summarize speeches, but documents get filed.
This skill builds that: the speech, the paper, the allies, and the timing.
What This Skill Produces
- The 3-minute comment: ask first, one human story, two checkable facts,
the ask again with a specific action — written for speaking, timed
- A one-page leave-behind: the ask, the evidence, the map/photo note,
contact details — the artifact that survives the meeting
- A coalition plan: turning three annoyed neighbors into ten present
ones, who says what (non-repeating angles), and the sign-up sheet moment
- The process map: where this decision actually lives, deadlines for
formal objections/comments, and who to lobby before the public bit —
flagged for local verification, since every council's machinery differs
Required Inputs
Ask for (if not already provided):
- The issue and the specific decision coming (a planning application? a
budget line? a road change?) plus any reference numbers/links
- What outcome they want, said plainly — oppose entirely? conditions?
delay? alternative?
- Their story and evidence so far, and how many neighbors are genuinely
bothered
- What they know of the process/dates (the skill flags what to find out at
the council's own site — never invents procedure)
Framework
- Find the real decision point. Public speaking slots are often
ceremonial; the movable moment is usually earlier (officer report,
consultation window, committee agenda-setting). Map: formal objection
deadlines → who writes the officer recommendation → which body decides →
when speaking happens. Each element gets a verify-at-your-council flag
with what to search for.
- Speak to the criteria, not the feeling. Deciding bodies can only
weigh what they're allowed to weigh (planning: material considerations;
budgets: statutory duties and consultation). Translate the grievance
into their categories — "this violates the parking standard in your own
local plan" outworks "this will ruin our street," even though the second
is why everyone came.
- Structure the three minutes as ask-story-evidence-ask. Open with the
ask in one sentence (they're deciding X; we ask you to Y) → one specific
human story, 45 seconds, concrete → two facts they can check (with the
source named aloud) → close with the ask plus the action ("defer until a
traffic survey is done"). Write it at speaking pace (~130 wpm) and mark
the cut-line for chairs who enforce 2 minutes.
- Multiply witnesses, don't repeat them. Each speaker takes one angle
(safety, precedent, process flaw, alternative); repetition wastes slots.
Non-speakers attend and stand when referenced — visible number, single
voice. The sign-up sheet at the meeting converts the audience into the
mailing list for round two.
- Follow up in writing within 48 hours. The one-pager emailed to every
member who sat there, with thanks, the ask, and the evidence links.
Decisions wobble between meetings; paper is what wobbles them.
Output Format
## The decision, mapped
[What's being decided, by whom, when · the earlier movable moments ·
verify-at-your-council items with search terms]
## Your 3 minutes (speaking pace, cut-line marked)
[The speech, ask-story-evidence-ask]
## The leave-behind (one page)
[Ask · evidence with sources · the visual note · who you represent · contact]
## Coalition plan
[Who takes which angle · the stand-when-referenced move · sign-up sheet]
## The next 48 hours and the next stage
[Follow-up email text · the earlier-stage lobbying if time remains]
Quality Checks
- [ ] The ask appears in the first and last sentences of the speech, and
it's an action the body can actually take
- [ ] Facts in the speech are checkable and sourced aloud; the feeling is
carried by the story, not by adjectives
- [ ] The speech reads aloud inside 3 minutes with a marked 2-minute cut
- [ ] Every procedural claim carries a verify-local flag — no invented
council process
- [ ] Speaker angles don't overlap; the coalition plan survives two
no-shows
Anti-Patterns
- [ ] Do not write outrage — the angriest speech in the room is the most
ignorable; controlled specificity reads as dangerous to ignore
- [ ] Do not attack the members deciding — tonight's opponent is next
round's swing vote
- [ ] Do not spend the three minutes on background; they have the papers,
you have the ask
- [ ] Do not assert planning law or council procedure as fact — criteria
framing yes, legal advice no
- [ ] Do not let ten people say the same thing worse
Related
[[stakeholder-influence-mapper]] for reading the committee;
[[press-release]] when the campaign needs the local paper; [[agm-in-a-box]]
— the same machinery from the chair's side.
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
它属于哪个仓库
exports/openclaw/speak-at-the-council/SKILL.md同一个仓库里的其他技能
同名技能的其他版本
有 3 个不同仓库或目录里都有叫 speak-at-the-council 的技能。它们内容并不相同,别混用:
- mohitagw15856/pm-claude-skills — Summarise what Speak At The Council does in one line. Use when asked to [trigger phrases t
- mohitagw15856/pm-claude-skills — Turn three minutes at a council or community meeting into the version that actually moves