Message Tone — Kristian Garza
Use when drafting rental inquiry messages for Kristian. Captures his writing register so messages are authentic and not AI-flavored.
What this skill does
## Kristian's Register
Messages are warm-professional: confident without being pushy, specific without being long-winded. They read like a capable adult wrote them in 5 minutes, not like a cover letter.
**Sentence count:** Max 5 in the body. Not 5 paragraphs — 5 sentences total.
**Opener rule:** Reference exactly ONE specific detail from the listing. Not the address, not "your beautiful flat" — something that proves you read the full listing: a floor, an available-from date, a specific feature (Altbau, Parkett, Balkon Richtung Süden, frei ab Juli).
**Clichés to avoid:**
- "Ich schreibe Ihnen bezüglich Ihrer Anzeige" — never
- "Ich bin auf der Suche nach einer Wohnung" — too generic
- "Ich würde mich sehr über eine Besichtigung freuen" — keep but don't open with it
- Any sentence starting with "Als" ("Als zuverlässiger Mieter...")
## Template
```
Guten Tag [Frau/Herr LastName if known, else no salutation],
[One sentence: specific listing detail + why it fits.]
[One sentence: employed at Digital Science, stable income, employed since [reasonable year].]
[One sentence: Schufa ready, non-smoker, no pets, move-in from 1. Juni 2026.]
Ich freue mich auf Ihre Rückmeldung und stehe gerne für eine Besichtigung zur Verfügung.
Mit freundlichen Grüßen,
Kristian Garza
```
## Word Count
80–140 words. Count the body only (not salutation, not sign-off). Under 80 reads as dismissive. Over 140 reads as desperate.
## Language
German by default. English fallback only if:
- The listing is written entirely in English, OR
- The contact name is clearly non-German and the listing has no German text
Never mix languages within a message.
## What Makes It Sound Human
- Use "ich" naturally — don't avoid first person out of politeness
- One contraction is fine ("bin's", "hab'") if it fits the tone
- If the flat has something genuinely appealing (Altbau, great location), one word of genuine response is fine ("... was mich besonders anspricht")
- Do NOT explain why you're moving, describe your current situation, or apologize for anything
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.