Skip to content
Agentmart
Submit a tool

gov-uk-style

Use when writing public-facing content, government or civic communication, help pages, policy summaries, or content requiring maximum-scope readability…

Skill by surendranb

IndexedMIT★ 50
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/surendranb-gov-uk-style

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when writing public-facing content, government or civic communication, help pages, policy summaries, or content requiring maximum-scope readability according to GOV.UK standards.

Use cases: writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/gov-uk-style

What's inside

Skill name
gov-uk-style
Description
Use when writing public-facing content, government or civic communication, help pages, policy summaries, or content requiring maximum-scope readability according to GOV.UK standards.
License
MIT
Compatibility
Requires standard Markdown parser and agent context
Instructions
51 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • REFERENCE.md · references/

SKILL.md (first lines)

# GOV.UK Style

Make complex information instantly clear, scannable, and accessible to every citizen.

## The core rule

**Start with the user's need. Sentences under 25 words, paragraphs under 5 lines, active voice, zero jargon.**

Workflow: `state user goal immediately` → `bullet points for eligibility or steps` → `plain active verbs` → `delete preamble`.

## Mechanics

1. **User need first.** Every page starts with what the user can do or find.
2. **Short sentences.** Maximum 25 words; vary length for rhythm.
3. **Active voice.** "You must apply online" not "Applications must be submitted".
4. **No jargon.** Replace bureaucratic terms with plain English (e.g. "pay" instead of "remuneration").
5. **Bulleted lists for steps.** Use bullet points for conditions, steps, or requirements instead of dense paragraphs.
6. **Bold sparingly.** Use bold only for critical warnings or key criteria.
7. **No Latin or Latinisms.** Use "for example" instead of "e.g." and "that is" instead of "i.e.".
8. **Anchor links.** Clear, descriptive link text that explains where the link goes.

## Verify

- First sentence directly addresses the user's primary intent
- Sentences average under 20 words
- Bullet points used for lists of 3 or more items
- Zero Latin abbreviations (e.g., i.e., et al.)
- Active voice used throughout

## Do not

- Use introductory throat-clearing ("It is important to note that...")
- Assume prior knowledge of government processes
- Write paragraphs longer than 5 lines
- Use passive voice for user instructions

## References

For exact mechanical rules (numbers, dates, times, money, measurements, links, abbreviations, punctuation), read `references/REFERENCE.md` when a draft includes any of these — load on demand, not upfront.

## Example transformations

**Before:** "In the event that an individual wishes to make an application for financial assistance, it is required that they submit documentation demonstrating eligibility prior to the commencement of the review process."

**After:** "You must send your eligibility documents before we review your financial aid application."

**Before:** "Users should note that e.g. tax returns must be filed by January 31st i.e. the end of the month."

**After:** "You must file your tax return by 31 January."

From surendranb/writing-skills, MIT.

More from surendranb/writing-skills

Signals

Stars
50
Forks
3
Open issues
0
Last commit (this folder)
Aug 18, 2026 (2 months ago)
Last release
Sep 2, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from surendranb

Cite this page

gov-uk-style skill. Agent Mart. https://agentmart.dev/skills/surendranb-gov-uk-style (last updated 2026-10-24)