Run any Skill in Manus with one click

german-technical-writing

Stars7

Forks0

UpdatedJune 20, 2026 at 11:49

Use this skill when the user asks in German for technical explanations, documentation, README text, release notes, CLI help text, commit or PR descriptions, architecture summaries, or precise editing of German developer-facing prose.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

SimonWaldherr

SimonWaldherr/RustyLLM

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	german-technical-writing
description	Use this skill when the user asks in German for technical explanations, documentation, README text, release notes, CLI help text, commit or PR descriptions, architecture summaries, or precise editing of German developer-facing prose.

German Technical Writing

Style

Use clear, direct German with technical terms where they are normal for developers.
Prefer active voice and concrete nouns over abstract filler.
Keep sentences short when explaining commands, flags, errors, or implementation behavior.
Preserve code identifiers, CLI flags, API paths, filenames, and English library names exactly.

Structure

State the key point first.
Explain the relevant mechanism or tradeoff.
Give commands, examples, or next steps only when they help the user act.

Output Rules

Do not translate identifiers such as --skills-dir, SKILL.md, GenerationOptions, or /v1/chat/completions.
Use German punctuation and capitalization.
Avoid marketing tone, exaggerated claims, and vague words like "einfach", unless the simplicity is the actual point.
When editing existing prose, keep the original intent and shorten where possible.

More from this repository

same repository

local-llm-troubleshooting

SimonWaldherr/RustyLLM

Use this skill when diagnosing local LLM startup speed, prompt latency, GGUF model loading, tokenizer/chat-template issues, Metal or CPU backend behavior, model selection problems, context-window limits, sampling settings, or API compatibility for OpenAI, LM Studio, Ollama, and MCP routes.

2026-06-207

rust-code-review

SimonWaldherr/RustyLLM

Use this skill when reviewing Rust code, diagnosing borrow checker errors, checking unsafe code, improving Cargo feature boundaries, or evaluating performance-sensitive Rust changes. Also use it when the user asks for a Rust review, Rust bug hunt, compiler error explanation, or refactoring guidance.

2026-06-207

skill-authoring

SimonWaldherr/RustyLLM

Use this skill when creating, reviewing, or improving SKILL.md files, agent skills, workflow instructions, trigger descriptions, progressive disclosure structure, bundled skill examples, or skill-selection behavior. Also use it when the user asks for best practices for skills.

2026-06-207

name	german-technical-writing
description	Use this skill when the user asks in German for technical explanations, documentation, README text, release notes, CLI help text, commit or PR descriptions, architecture summaries, or precise editing of German developer-facing prose.

German Technical Writing

Style

Use clear, direct German with technical terms where they are normal for developers.
Prefer active voice and concrete nouns over abstract filler.
Keep sentences short when explaining commands, flags, errors, or implementation behavior.
Preserve code identifiers, CLI flags, API paths, filenames, and English library names exactly.

Structure

State the key point first.
Explain the relevant mechanism or tradeoff.
Give commands, examples, or next steps only when they help the user act.

Output Rules

Do not translate identifiers such as --skills-dir, SKILL.md, GenerationOptions, or /v1/chat/completions.
Use German punctuation and capitalization.
Avoid marketing tone, exaggerated claims, and vague words like "einfach", unless the simplicity is the actual point.
When editing existing prose, keep the original intent and shorten where possible.