317
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill xe/x --skill xe-writing-style- SKILL.md8.7 KB
Overview
This skill transforms unstructured notes, outlines, or brain dumps into polished blog posts in Xe Iaso's voice. It organizes messy thoughts, applies Xe's technical, candid, and opinionated tone, and returns MDX-ready drafts with the expected structural and stylistic devices. Use it for full drafts, stylistic rewrites, or targeted reviews to match Xe's signature cadence.
How this skill works
Provide raw notes, an outline, or an existing draft and indicate the intended emotional register (narrative, personal, satirical, mythic, or spiritual). The skill reads the voice and reference scaffolds, chooses an appropriate structure, and outputs an MDX-formatted post with dialogue components, napkin math, and other Xe devices where useful. It also enforces hard constraints like peer-level language, explicit tradeoffs, and admission of uncertainty.
When to use it
- You have a messy brain dump that needs shaping into a publishable Xe-style post.
- You want an existing draft rewritten to match Xe Iaso's technical, candid voice.
- You need the post converted into MDX with dialogue blocks and signature devices.
- You want a review that enforces voice rules and structural scaffolds (story circle, satire, etc.).
- You need a first-pass structure recommendation using Xe's narrative patterns.
Best practices
- Give the emotional register upfront (story, personal, satire, mythic, or spiritual).
- Include 2–3 sample Xe posts or a short pointer to which reference modes apply for tighter calibration.
- Provide any factual links, code snippets, or napkin-math numbers to preserve accuracy.
- Ask for targeted edits (tone, pacing, dialogue use) rather than vague ‘make it sound like Xe’.
- Expect tradeoffs: stronger voice often shortens technical exposition—specify if you want extra depth.
Example use cases
- Turn a weekend’s worth of project notes into a 1,000–1,500 word MDX post with Cadey/Aoi dialogue as aside beats.
- Rewrite a tutorial to be opinionated and peer-focused, adding napkin math and tradeoff sections.
- Edit a personal essay for emotional register, tightening openings and closing with a forward-looking question.
- Convert a cursed-project rant into a satirical post with warning boxes and comedic pacing.
- Review a draft to enforce hard rules: no marketing words, admit uncertainty, and vary paragraph starters.
FAQ
I can craft the MDX scaffolding and image placeholders; provide the image paths or prompts for final assets.
Will it preserve technical accuracy in code examples?
Yes, but supply the code or exact commands you want included—I'll format and wrap them in <details> if long. I’ll call out assumptions and tradeoffs when unsure.