Netresearch Skills Marketplace
Workflow

German Technical Writing

Enforce natural German technical register in Jira tickets, internal docs and team chat. Catches English→German anglicisms (brechen, gefangen, triggern, failen) and substitutes canonical verbs (werfen, abfangen, auslösen, fehlschlagen). Accepts Denglisch loanwords. Skips commit messages.

Latest release v1.1.0

Install

Pick whichever fits your project — they all reach the same skill.

  1. Claude Code via this marketplace 
    /plugin install german-technical-writing@netresearch-claude-code-marketplace
  2. npx any Agent Skills CLI 
    npx skills add https://github.com/netresearch/german-technical-writing-skill --skill german-technical-writing

    Universal Agent Skills CLI from skills.sh — works across Claude Code, Cursor, GitHub Copilot, Codex, Gemini CLI and 30+ more agents.

  3. composer require PHP project, as a package 
    composer require netresearch/german-technical-writing-skill

    Requires netresearch/composer-agent-skill-plugin — resolves Agent Skills as Composer dependencies in PHP projects, auto-discovers skills, generates AGENTS.md.

  4. composer skills:add PHP project, direct source 
    composer skills:add github:netresearch/german-technical-writing-skill

    Provided by netresearch/composer-agent-skill-plugin — pins skill repos directly without going through Packagist, locks them in composer.skills.lock.

What you can do with it

  • Anti-pattern detection: ~60 false-friends catalogued — brechen, gefangen, returnen, failen, triggern, hitten, plus calqued idioms (am Ende des Tages, Low-hanging Fruit) and pseudo-anglicisms (Handy, Beamer)
  • Technical lexicon: preferred German forms with gender for Exceptions, Tests, Git, CI/CD, HTTP, Frontend, Data, and Architecture domains
  • Register enforcement: Präsens-Indikativ default, impersonal voice, no first-person in artifacts, sentence-length and compound-noun rules, ß/ä/ö/ü orthography
  • Artifact-specific conventions: Jira ticket descriptions, Jira comments, internal German wiki/spec pages
  • Worked examples: 6 paired bad-vs-good cases with annotations

What it expects in your project

Tags

  • workflow
  • productivity