Write a letter of support
Writes a letter of support for a grant, planning application, partner organisation or community project with specific commitments and evidence of need, to be signed by an organisation or leader.
Funders, panels and committees read many letters of support and discount the generic ones: "we fully support this excellent project" from a body that commits nothing and knows little. The letters that count show a real relationship, add evidence of need the applicant could not provide alone (the supporter's own waiting list, referral numbers or local knowledge), and make specific, quantified commitments. Panels also notice when several letters share the same wording, so each should read as the supporter's own. A letter of commitment, which binds the supporter to cash or resources, carries more weight and must be signed by someone with authority to commit. Planning committees can only weigh material planning considerations (such as design, amenity, traffic, community benefit), so support for a planning application should speak to those rather than to personal loyalty.
Write a letter of support to from .
Only if [COMMITMENTS] is given:
Only if [EVIDENCE] is given:
- If the project or the supporter's relationship to it is unclear, ask up to two questions and stop.
- Layout: the supporter's letterhead placeholder, date, the recipient's name and address placeholders, and a reference line with the project title and the funding call or application reference.
- First paragraph: who the supporter is (one sentence of standing: what they do, scale, area) and the statement of support for the named project and applicant.
- Relationship: how long and in what way the supporter has worked with the applicant, with one concrete example from the input.
- Need: the evidence of need from the supporter's own vantage point, with figures from the input. If none is given, write
[need: one figure or observation from your own work, e.g. waiting list, referrals]rather than inventing one. - Commitments: each commitment as a specific, quantified line (what, how much, when, for how long). If none is given, keep the letter to support only, do not imply resources, and suggest under Notes what commitments would strengthen it.
- For a planning application, frame support around material considerations named in the input (community benefit, design, accessibility, local employment) and avoid irrelevant ones.
- Close: the expected benefit in one or two sentences and a contact for verification, then a signature block with name, title and organisation placeholders as needed.
- One page: about 250 to 400 words.
- Use only facts given. Never invent statistics, history, outcomes or commitments, even if asked to make the case stronger; use
[need: …]placeholders and explain under Notes. - Write in the supporter's voice, specific to them; avoid stock phrases ("wholeheartedly support", "excellent initiative", "will make a real difference") unless backed by a fact in the next sentence.
- Do not overstate the supporter's authority or describe the letter as a binding commitment unless the input says it is one.
Letter
The letter, ready for letterhead.
For the signatory to confirm
Bullets: each commitment, figure and claim the signatory must check, and that they have authority to commit.
Notes
Placeholders, suggestions to strengthen it, and anything left out on purpose. "None" if nothing.
3 required values still a placeholder; the assistant will ask for them.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- Business writing
- level
- Intermediate
- made for
- Founder / business owner, Executive / leader, Researcher / scientist, People manager
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-03
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install write-letter-of-support --target claude-codeThis entry is in the full catalog, not the curated set the skills installer and plugins carry, so install it with the Hodios CLI.
pairs well with
All of Business writingWrite a nonprofit case for support
Writes a nonprofit case for support - the need with evidence, the organisation's approach, its impact, what gifts make possible at each level and why now - plus short versions for reuse.
write-case-for-supportWrite a formal letter
Writes a formal letter to a bank, council, school, supplier or official body in the layout and conventions of the chosen country, with a clear purpose, references and a specific request.
write-formal-letterWrite a project proposal or business case
Writes an internal project proposal or business case covering the problem, options, recommendation, cost, benefits and risks, and marks every missing number instead of inventing it.
write-project-proposalWrite an executive summary
Writes an executive summary of a long document that leads with the bottom line, the key points and the ask, using only facts from the source. Use before sending a report to busy readers.
write-executive-summaryWrite an internal announcement
Writes an internal announcement of a reorg, policy change or launch that explains what is changing, why, the impact on each group and where to ask, plus an FAQ and a pre-send check.
write-internal-announcementWrite a project status report
Writes a project status report with an evidence-based RAG status, progress, risks, decisions needed and next steps, formatted as an email, a document or a single slide.
write-status-report