agentleFS
peterbamuhigirepeterbamuhigire/proposal-skills/skills/language/east-african-english/SKILL.md

east-african-english

Skill11 starsChanged 17 days agoMITView on GitHub

Use when drafting or reviewing English proposal content for Uganda, Kenya, Tanzania, or regional East African audiences; use language-standards when French or Kiswahili routing is also required.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. About 0 are common, 20 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈20

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when English-language output needs East African professional tone and British spelling.

    line 16
  2. Distinctive:

    Check for hype, awkward phrasing, and non-local wording patterns.

    line 34
  3. Distinctive:

    Stop when an institutional title, official programme name, or local term cannot be verified.

    line 35
  4. Distinctive:

    Read and search are required.

    line 41
  5. Distinctive:

    Prefer clarity, courtesy, and natural local phrasing over flashy copy.

    line 57
  6. Distinctive:

    Use this as a cross-cutting review pass, not as a substitute for domain or procurement logic.

    line 58
  7. Distinctive:

    All proposal text — cover letters, executive summaries, methodology sections, CVs, financial submissions, and supporting documents — must …

    line 86
  8. Distinctive:

    Professionally indirect: Avoid bluntness. Soften directives with courteous phrasing.

    line 93
  9. Distinctive:

    Always use British spelling:

    line 100
  10. Distinctive:

    Write dates in day-month-year order:

    line 120
  11. Distinctive:

    Never use month-first American format (February 17, 2026).

    line 125
  12. Distinctive:

    When the client is based in a specific country, adjust the tone slightly:

    line 129
  13. Distinctive:

    When no specific country is indicated, use the neutral East African style — a balanced blend of all three.

    line 155
  14. Distinctive:

    Should the Evaluation Committee require any further clarification, we remain at your disposal.

    line 166
  15. Distinctive:

    Use simple, professional vocabulary:

    line 174
  16. Distinctive:

    Never use exaggerated marketing language in proposals:

    line 184
  17. Distinctive:

    Instead of abbreviations, write in full:

    line 209
  18. Distinctive:

    No fragments or telegram-style copy

    line 217
  19. Distinctive:

    Name the client: use the client's actual name, not "the client" — it shows the proposal was written for them

    line 241
  20. Distinctive:

    Use this as a benchmark for tone and rhythm:

    line 264

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

East African English — Language & Tone Skill

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

<!-- dual-compat-start -->

Use When

  • Use this skill when English-language output needs East African professional tone and British spelling.
  • Load it as a cross-cutting review or drafting standard for proposals and related business writing.

Do Not Use When

  • The task is purely about procurement mechanics or domain frameworks with no language work.
  • Another loaded skill already defines the exact language treatment and there is no conflict.

Inputs

ArtefactSource/providerRequired?Missing-input behaviour
Draft or planned English textProposal workflowYesStop language review until the text or section purpose is available.
Country, institution, and procurement contextClient brief and sectorsYesUse neutral regional English and state the missing locale context.
Proposer voiceprofilesYes for proposal draftingDo not infer first-person voice or signatory identity.

Workflow

  1. Determine the audience, purpose, and level of formality.
  2. Apply the relevant tone, spelling, vocabulary, and courtesy rules from this skill.
  3. Check for hype, awkward phrasing, and non-local wording patterns.
  4. Stop when an institutional title, official programme name, or local term cannot be verified.
  5. Recover by retaining the source wording, flagging it for review, or using neutral qualified wording.
  6. Return wording that sounds natural in East African professional English.

Capability Contract

Read and search are required. Editing is allowed only for authorised drafting or language correction. Network verification, publishing, submission, and certification of local usage require explicit authority.

Degraded Mode

Fallback: when the country context, proposer profile, approved wording, or verification source is unavailable, return the narrowest useful neutral regional version, mark the affected choice not assessed, and do not claim country-specific authenticity.

Decision Rules

Condition or choiceActionFailure or risk avoided
Ugandan, Kenyan, Tanzanian, or regional professional audienceUse British spelling and formal East African courtesyImported US or sales-heavy register
Buyer supplies official wordingPreserve it exactly even if house style differsProcurement non-compliance
Country-specific term is uncertainUse neutral regional wording and flag reviewInvented localism
French or Kiswahili is also requiredRoute through language-standardsInconsistent multilingual handling

Quality Standards

  • Prefer clarity, courtesy, and natural local phrasing over flashy copy.
  • Use this as a cross-cutting review pass, not as a substitute for domain or procurement logic.
  • Preserve compatibility with existing repository workflows and file paths.

Anti-Patterns

  • Mixing American and British spelling in one document. Fix: select British English and run a consistency pass.
  • Using startup slang in a formal procurement response. Fix: replace it with precise professional wording.
  • Forcing regional idioms into a neutral institutional document. Fix: prefer clear standard English.
  • Claiming country-specific authenticity without context. Fix: use neutral regional tone and mark the locale not assessed.
  • Rewriting official programme names for style. Fix: reproduce the buyer's wording exactly.

Outputs

ArtefactConsumerAcceptance condition
East African English proposal textEvaluator and proposal editorSpelling, register, courtesy, proposer voice, dates, and official names are consistent and traceable.

Evidence Produced

EvidenceConsumerAcceptance condition
Language review recordProposal release ownerLocale, applied standard, preserved official wording, and unresolved choices are recorded.

References

  • Multilingual language standards
  • Proposer profile router
  • Proposal parent router
<!-- dual-compat-end -->

All proposal text — cover letters, executive summaries, methodology sections, CVs, financial submissions, and supporting documents — must follow this style guide. This is the foundational language standard applied before and during every content-writing step.

Core Characteristics

  1. Clear and direct. Sentences are straightforward, grammatically careful, and logically structured. No slang in professional communication.
  2. Formal and respectful. Politeness is essential. Communication shows courtesy and humility.
  3. British English spelling. organisation, programme, centre, colour, travelling (double "l").
  4. Professionally indirect. Avoid bluntness. Soften directives with courteous phrasing.
  5. Measured confidence. Confident without arrogance. No dramatic or exaggerated language.

British English Standards

Spelling

Always use British spelling:

CorrectIncorrect
organisationorganization
programmeprogram
centrecenter
colourcolor
travellingtraveling
specialisespecialize
honourhonor
favouritefavorite
analyseanalyze
defencedefense
licence (noun)license (noun)
cataloguecatalog
enquiryinquiry

Dates

Write dates in day-month-year order:

  • 17 February 2026
  • 17th February 2026

Never use month-first American format (February 17, 2026).

Tone by Country Context

When the client is based in a specific country, adjust the tone slightly:

Uganda — Warm and Relational

  • Very polite and appreciative
  • Frequent use of "kindly"
  • Emphasis on harmony and goodwill

We highly appreciate the opportunity to submit this proposal and look forward to contributing to the Authority's reform programme.

Kenya — Confident and Business-Oriented

  • Efficient and practical
  • Clear timelines and expectations
  • Professional firmness

Our team will mobilise within two weeks of contract signing and deliver the inception report by 21 February 2026.

Tanzania — Calm and Measured

  • Formal and slightly conservative
  • Respectful and patient rhythm
  • Influenced by Swahili sentence structure

We kindly request the Evaluation Committee's guidance on the preferred format for the deliverables outlined in the Terms of Reference.

When no specific country is indicated, use the neutral East African style — a balanced blend of all three.

Courteous Phrases for Proposals

These are natural and expected in East African professional writing:

  • We kindly request…
  • We would like to draw attention to…
  • We wish to highlight…
  • We are pleased to present…
  • We have the honour to submit…
  • Should the Evaluation Committee require any further clarification, we remain at your disposal.
  • We look forward to the opportunity to serve [Client Name].
  • We appreciate the confidence placed in our firm.

Vocabulary Standards

Preferred Professional Words

Use simple, professional vocabulary:

  • facilitate, implement, undertake, liaise, coordinate
  • engage, support, enhance, review, confirm
  • advise, revert (meaning "respond" — widely accepted in East Africa)
  • significant, important, strategic, beneficial, valuable
  • deploy, mobilise, commence, conclude

Words and Phrases to Avoid

Never use exaggerated marketing language in proposals:

AvoidUse Instead
groundbreakingsignificant
revolutionaryinnovative
game-changingstrategic
amazingcommendable
awesomeexcellent
incredibleremarkable
unleashenable
skyrocketimprove significantly
superchargestrengthen
crushing itperforming well
world-class (unless substantiated)proven, established, leading
best-in-classhighly experienced, well-established

Also avoid:

  • American slang and casual abbreviations (FYI, ASAP, BTW)
  • Dramatic emotional tone
  • Complex academic vocabulary that obscures meaning
  • Excessive exclamation marks (none in proposals)
  • AI-sounding vocabulary (delve, tapestry, landscape as metaphor, leverage, navigate as metaphor, foster, realm, harness, synergy, embark, robust, vibrant, holistic, seamless)

Instead of abbreviations, write in full:

Please respond as soon as possible.

Sentence Style

Use Full, Balanced Sentences

  • No fragments or telegram-style copy
  • Moderate length — not too short, not too complex
  • Logical structure with clear subject-verb-object order

Good:

The team has completed the initial assessment and will submit the final report by the end of the week.

Professional Indirectness

Soften directives and assertions. Never sound blunt or commanding.

Too BluntEast African Style
We are the best firm for this.We believe our experience positions us well to deliver this assignment.
The client's current system is failing.The current system presents opportunities for significant improvement.
This timeline is unrealistic.We respectfully note that the proposed timeline may benefit from additional consideration.
Other firms lack our expertise.Our team brings a combination of skills that is directly relevant to this assignment.

Proposal-Specific Style

  • First-person plural throughout: "We propose…", "Our team will…", "We have successfully…"
  • Active voice preferred: "We will conduct stakeholder workshops" not "Stakeholder workshops will be conducted"
  • Quantify wherever possible: "We trained 127 staff across four departments" not "We trained many staff"
  • Name the client: use the client's actual name, not "the client" — it shows the proposal was written for them
  • Reference the ToR: "As outlined in Section 3.2 of the Terms of Reference" — shows careful reading

Openings and Closings (for cover letters and correspondence)

Openings

  • Dear Sir/Madam,
  • Dear Mr. Otieno,
  • The Chairperson, Contracts Committee,
  • The Procurement Officer,

Closings

  • Yours faithfully, (when you do not know the recipient)
  • Yours sincerely, (when you know the recipient)

Often followed by:

We look forward to the opportunity to contribute to [Client Name]'s objectives and remain at your disposal for any further clarification.

Reference Paragraph — Neutral East African Proposal Style

Use this as a benchmark for tone and rhythm:

We have the honour to submit this technical proposal in response to the Terms of Reference for the Development of an Integrated Financial Management Information System for the Ministry of Finance, Planning and Economic Development. Our firm brings over fifteen years of experience in public financial management systems across East Africa, having successfully implemented similar platforms for the Uganda Revenue Authority and the Kenya National Treasury. We are confident that our proposed approach, combined with our team's deep understanding of government financial processes, will deliver a system that meets the Ministry's requirements and supports its reform agenda.

When This Skill Applies

  • All proposal sections — cover letters, executive summaries, methodology, experience, team CVs
  • All supporting documents — EoIs, financial proposals, correspondence with procuring entities
  • All generated content — blog posts, thought leadership articles related to proposals
  • Internal documents — inception reports, progress reports, deliverables produced during assignments

This skill runs alongside every other skill. It governs what the text says and how it sounds.

English collocation and lexical-precision overlay

Load english-collocations-and-lexical-precision-2026-09-02.md. Retain genuine East African courtesy while removing inflated formality, stock phrases, unearned certainty, and unnatural synonym substitutions.

Proposal phrase bank

For proposal sections, apply the tone rules and slot-templates in the proposal phrase bank: measured and courteous, no US hype idioms, currency with thousand separators, districts and towns named, and the client's own words in needs and goals.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.