agentleFS
simonstrumsesimonstrumse/vibelabs-skills/skills/klarsprak/SKILL.md

klarsprak

Skill0 starsChanged 9 months agoMITView on GitHub

Norwegian plain language (klarspråk) guidelines from Språkrådet. Use when writing Norwegian website copy, marketing text, UI labels, documentation, or any user-facing Norwegian content. Triggers on Norwegian text, norsk tekst, klarspråk, markedsføring, nettsidetekst, brukergrensesnitt, or when reviewing/improving Norwegian copy quality.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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 "du/dere" (you) and "vi" (we) instead of passive constructions.

    line 32
  2. Distinctive:

    Put the actor first, then the action.

    line 41
  3. Distinctive:

    Avoid jargon, use everyday Norwegian.

    line 50
  4. Distinctive:

    Before publishing Norwegian text, verify:

    line 163

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Klarspråk - Norwegian Plain Language Skill

Official guidelines from Språkrådet (Norwegian Language Council) for writing clear, effective Norwegian text.

Legal basis: Norwegian law (språkloven § 9) requires public communication to use "klart og korrekt språk som er tilpassa målgruppa" (clear and correct language adapted to the target audience).


Core Definition

Klarspråk is communication with such clear wording, structure, and design that readers:

  1. Find the information they need
  2. Understand what they find
  3. Can use it for their purpose

The 7 Principles of Klarspråk

1. Know Your Reader

Before writing, answer:

  • Who will read this?
  • What do they already know?
  • What do they need to do with this information?

2. Write Directly to the Reader

Use "du/dere" (you) and "vi" (we) instead of passive constructions.

AvoidPrefer
"Det tilbys kurs i...""Vi tilbyr kurs i..."
"Påmelding kan gjøres...""Meld deg på..."
"Brukeren må...""Du må..."

3. Use Active Voice

Put the actor first, then the action.

PassiveActive
"Kurset holdes av eksperter""Eksperter holder kurset"
"Systemet ble utviklet""Vi utviklet systemet"
"Det ble besluttet at...""Vi besluttet at..."

4. Choose Simple, Precise Words

Avoid jargon, use everyday Norwegian.

Complex/WrongSimple/Correct
"implementere""innføre, ta i bruk"
"utøvere" (athletic performers)"folk som jobber med", "praktikere"
"fasilitere""legge til rette for"
"leveranse""levering"
"kompetanseheving""opplæring"
"skalere""utvide, vokse"

5. Write Short Sentences

  • Aim for 15-20 words per sentence
  • One idea per sentence
  • Break long sentences into shorter ones
LongShort
"Vi tilbyr praktisk opplæring som gjør at teamet ditt kan bygge AI-drevne løsninger raskere enn før, fra prototype til produksjon.""Vi tilbyr praktisk opplæring. Teamet ditt lærer å bygge AI-drevne løsninger. Fra prototype til produksjon på dager, ikke måneder."

6. Use Logical Structure

  • Most important information first
  • Clear headings and subheadings
  • Lists for multiple items
  • White space for readability

7. Test with Real Readers

Have someone from your target audience read the text before publishing.


Common Norwegian Marketing Copy Mistakes

Words Often Misused

WordActually MeansUse Instead
utøvereAthletic performers (skiutøvere, idrettsutøvere)"folk som", "de som jobber med", "praktikere"
eksponeringBeing exposed to danger/harm"synlighet", "oppmerksomhet"
adressereTo put an address on something"ta opp", "se på", "løse"
løfte (noun)A physical lift"mål", "ambisjon", "satsing"
prosessOften overusedBe specific: "arbeid", "utvikling", "behandling"

Anglicisms to Avoid

AnglicismNorwegian
"shippe""levere, sende ut"
"booste""øke, styrke"
"pitche""presentere"
"onboarde""ta imot, sette i gang"
"deale med""håndtere"
"value proposition""verdi, nytte"

Awkward Constructions

AwkwardNatural
"Vi hjelper team å...""Vi lærer team å...", "Lær å..."
"Tilbud på opplæring""Kurs i..."
"Løsninger som gjør at...""Med X kan du..."

Norwegian Website Copy Patterns

Headlines (Overskrifter)

Pattern: Verb + benefit

Lær å bygge [thing] med [technology]
Bli bedre på [skill]
Fra [problem] til [solution]

Examples:

  • "Lær å bygge ekte produkter med AI"
  • "Bli en AI-drevet utvikler"
  • "Fra idé til ferdig produkt på dager"

Subheadlines (Underoverskrifter)

Pattern: Concrete outcome + timeframe

[What you get]. [How fast/easy].

Examples:

  • "Praktisk opplæring som gjør teamet ditt til AI-drevne utviklere. Fra prototype til produksjon på dager, ikke måneder."

CTAs (Handlingsknapper)

Pattern: Short imperative verb

Long/WeakShort/Strong
"Klikk her for å registrere deg""Meld deg på"
"Les mer om våre tjenester""Se tjenester"
"Ta kontakt med oss i dag""Ta kontakt"
"Book en gratis konsultasjon""Book møte"

Social Proof

InflatedCredible
"Verdensledende ekspertise""800+ fagfolk opplært"
"Best i bransjen""4.8 i gjennomsnittlig vurdering"
"Revolusjonerende""50+ bedrifter transformert"

Quality Checklist

Before publishing Norwegian text, verify:

  • Reader focus: Is it clear who this is for?
  • Active voice: Are sentences mostly active?
  • Simple words: No unnecessary anglicisms or jargon?
  • Short sentences: Average under 20 words?
  • Correct vocabulary: No misused words (especially "utøvere")?
  • Direct address: Using "du/dere/vi"?
  • Clear structure: Most important info first?
  • Actionable CTAs: Clear what reader should do?

Resources


Quick Reference Card

┌─────────────────────────────────────────────────────────────┐
│  KLARSPRÅK QUICK CHECK                                      │
├─────────────────────────────────────────────────────────────┤
│  ✓ Du/vi instead of passive                                 │
│  ✓ Active voice: "Vi tilbyr..." not "Det tilbys..."        │
│  ✓ Short sentences (15-20 words)                            │
│  ✓ Norwegian words over anglicisms                          │
│  ✓ "utøvere" = athletes, NOT practitioners                 │
│  ✓ Most important info first                                │
│  ✓ Clear, short CTAs                                        │
└─────────────────────────────────────────────────────────────┘

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.