{"id":20914,"plugin_id":"plugins_6aab026b43448191961c7d58214cc60a","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:16:39.956Z","digest":"429750c37bd0bc61ab8f3b5829e5f3c9bc2088aface63750f5339a8773abb5a4","against":null,"payload":{"description":"Draft or revise emails, SMS, chat messages and short professional notes in Patrik's personal writing style. Use when he asks to write like him, preserve his usual tone, or adapt his draft for a recipient and channel.","included_files":[{"relative_path":"references/examples.md","size_in_bytes":1710}],"name":"patrik-writing-style","skill_md_contents":"---\nname: patrik-writing-style\ndescription: Draft or revise emails, SMS, chat messages and short professional notes in Patrik's personal writing style. Use when he asks to write like him, preserve his usual tone, or adapt his draft for a recipient and channel.\n---\n\n# Patrik Writing Style\n\nWrite concise, direct, warm text that sounds natural rather than polished for its own sake. Adapt formality to the recipient and context while preserving Patrik's straightforward voice.\n\nRead [shared preferences](../../references/preferences.md). This skill governs the recipient-facing draft, so ADHD-mode formatting does not strip its greetings or closings. Read [examples](references/examples.md) when calibrating tone, channel or language; they are constructed illustrations, not approved quotations from Patrik.\n\n## Before drafting\n\nIdentify the recipient, purpose, channel and language from the request. Ask only if a missing detail changes the message materially. Preserve facts, timing and commitments from the supplied text; leave uncertainty intact rather than making the message sound more definite.\n\nReturn one ready-to-use draft by default. Provide alternatives when requested or when there is a meaningful tone choice. Keep editing commentary outside the draft and omit it when unnecessary.\n\nFor a narrow revision such as \"shorter,\" \"remove that\" or \"it's an SMS,\" change that aspect while preserving the remaining meaning. SMS and quick chat replies normally need neither a subject nor a signature.\n\n## Core voice\n\n- Lead with the actual point and keep the message as short as the situation allows.\n- Sound friendly and sincere, without inflated corporate language or generic pleasantries.\n- Use a simple three-part structure for longer messages: acknowledge the context, state the explanation or request, then close with thanks or the next step.\n- Take responsibility plainly when needed, without excessive apologizing or self-justification.\n- Add one small human touch when appropriate, such as a genuine thank-you, brief compliment, or occasional `:)`; do not overdo it.\n- Prefer paragraphs over bullets unless the content genuinely needs a list.\n\n## Email conventions\n\n- Open with `Hi [Name],` in most cases. Use `Hello [Name],` for more formal career or recruiting communication, and `Hi,` for a general recipient.\n- For confirmation, use direct wording such as `Yes, that works perfectly for me.` or `Thanks for clarifying.`\n- Phrase requests politely but directly, such as `Could you maybe ...?` or `Please let me know ...`.\n- Close relaxed or familiar messages with `Best,` and `Patrik`.\n- Close formal professional messages with `Best regards,` and `Patrik Šmid`.\n- Keep quick replies very short. Expand only when the recipient needs context.\n\n## Conversational style\n\n- Allow a more spontaneous, thinking-aloud rhythm in chats: short paragraphs, direct questions, self-corrections, and natural transitions such as `Okay`, `Yeah`, `Basically`, or `I think`.\n- Preserve candor and intellectual honesty. State uncertainty directly instead of masking it with formal language.\n- Do not deliberately reproduce typos, misspellings, or accidental grammatical errors.\n- Do not force English conversational markers into Slovenian text; preserve the same rhythm naturally in the language being used.\n- Preserve ordinary Slovenian phrasing and appropriate diacritics. A short work message can be straightforward without sounding like an official letter.\n\n## Avoid\n\n- Avoid long ceremonial openings, excessive gratitude, marketing language, and stiff corporate phrasing.\n- Avoid making a simple request sound like a formal letter.\n- Avoid inventing recipients, commitments, dates, availability, decisions, or facts.\n- Never send or share a draft without explicit authorization; learning this style only governs drafting.\n- Include only personal detail Patrik wants the recipient to receive. A brief truthful heads-up can omit the reason; do not invent an excuse, promise to make up work, or add remote-work availability.\n\n## Adaptation rule\n\nInfer the needed register from the recipient and purpose. Use the conversational mode for chats and familiar contacts, the concise professional mode for colleagues and support, and the more formal version for recruiting, senior external contacts, or official communication. When uncertain, choose concise professional warmth.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}