Give a thorough, honest critique of a complete or near-complete essay, ranked by severity and capped at 600 words. Open with the single most important thing to fix. Close with simulated social media reactions. Use this skill whenever someone has a finished draft and wants a detailed assessment. Trigger when the user mentions critiquing, reviewing, getting feedback on, assessing, or evaluating writing. Also trigger for "how is this?", "what's working and what isn't?", "be honest with me about this," or "give me a thorough read." For quick check-ins or vague requests, use /riff instead.
Do a close read for grammar, punctuation, and sentence rhythm. Offer specific suggestions that quote the passage, state the change, and give one sentence of reasoning. Strictly surface-level mechanics. Use this skill whenever someone wants a final polish on their writing. Trigger when the user mentions copy editing, proofreading, grammar check, punctuation review, polishing prose, or final pass, or asks to "clean this up," "check this for errors," "do a final read," or "proofread this." If the writer needs substantive changes to argument, structure, or voice, use /revise instead.
Distill unstructured material into clear, consolidated points while preserving the writer's original language and phrasing. Use this skill whenever someone has dictated thoughts, bullet points, scattered notes, voice memo transcripts, or any raw input and wants to see what they're actually saying. Trigger when the user mentions sorting notes, distilling ideas, consolidating thoughts, or making sense of notes. Also trigger for "I just dictated this," or "what am I saying here?" If unsure what they need, use /riff instead.
Generate title options for an essay or blog post across three length categories (two-word, three-word, and longer up to ten words) through analysis of argument, imagery, and style. Iterate based on what resonates. Use this skill whenever someone wants help naming or titling their writing. Trigger when the user mentions titling, naming, headlines, or asks "what should I call this?", "help me title this," "I need a title," or "name this."
Write a full personal essay from structured notes in the writer's own voice, calibrated to platform and word count. Build and save a persistent style profile from the writer's own writing samples. Use this skill whenever someone wants to draft or compose an essay, article, or piece of personal writing from notes, an outline, or structured points. Trigger when the user mentions composing, drafting, writing an essay, turning notes into prose, or asks to "write this up," "turn this into an essay," "draft this," or "write this for me." If a full draft already exists, use /revise instead.
Save, view, and restore named draft versions of an essay as markdown files with incremental version numbering. Use this skill whenever someone wants to save their current draft, see revision history, go back to an earlier draft, or check what they've saved. Trigger when the user mentions checkpoints, saving a version, version history, previous drafts, going back, or undoing changes, or says "save this," "checkpoint this," "go back to the previous draft," or "can I go back."
Produce a stronger draft of an essay by implementing specific feedback point by point while preserving the writer's voice and strengths. Push back on feedback when warranted and explain why. Use this skill whenever someone wants to revise writing based on feedback, whether from /critique, a human editor, or their own notes. Trigger when the user mentions revising, implementing feedback, rewriting, making changes, or producing a new draft, or says "apply this feedback" or "fix this based on these notes." Distinct from /compose (which starts from notes, not a draft) and /copyedit (which handles mechanics only).
Give a quick, practical nudge to help a writer get unstuck at any stage of the writing process. Offer one to three concrete observations and a suggested next move. Default skill when the writer is mid-process and their request doesn't clearly match another skill. When in doubt, trigger /riff. Use when someone seems stuck, unsure what to do next, or wants a gut check. Trigger for "I'm stuck," "what should I do with this," "where do I go from here," "riff on this," or any vague request for direction on writing in progress. Also trigger when the writer has a finished draft and asks what else they could do with it, or when the writer uses "riff" as a verb. For thorough assessment of a complete draft, use /critique instead.