cleanup-writing

Étoiles3

Forks1

Mis à jour21 mars 2026 à 20:55

Edit and improve writing by restructuring sections, clarifying prose, and tightening flow. Use when the user wants to edit, revise, polish, proofread, or improve a draft; says "clean up my writing", "make this clearer", "this sounds awkward", "tighten this up", "make it more concise", "does this flow well?", or asks for help with an email, README, blog post, PR description, technical doc, or any piece of prose.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

yldgio

yldgio/vibe-grimoire

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Rédacteurs techniquesArts, design, divertissement, sports et médias·SOC 27-3042

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name

cleanup-writing

description

Cleanup Writing

Edit and improve a piece of writing section by section — fixing information order, improving clarity, and tightening prose — then deliver the full revised document.

Process

1. Structure the document

Divide the writing into sections based on its headings. If no headings are present, propose a logical division based on content and flow.

Before confirming the structure, check the information ordering: readers need concept A before concept B can land, so no section should assume knowledge that hasn't been introduced yet. Think of this as a dependency chain — earlier sections must establish everything that later sections rely on. Reorder or flag any sections that violate this.

2. Confirm the plan

Present the proposed section breakdown and order to the user. If the user disagrees, revise the structure before rewriting anything — rewriting in the wrong structure wastes effort.

3. Rewrite each section

For each section in order:

Rewrite to improve clarity, coherence, and flow
Keep paragraphs short — no more than 240 characters each. Short paragraphs reduce cognitive load, force one idea per paragraph, and keep readers moving forward; long paragraphs bury the point
Cut filler words, passive voice, and redundant phrases
Preserve the author's voice — edit, don't replace

4. Deliver the revised document

Output the complete revised document in full. Do not output only the changed sections — the user needs to see how the whole piece reads together as a continuous flow.

After delivering, ask: "Would you like me to adjust the tone, tighten any section further, or rethink the structure?"

Plus depuis ce dépôt

même dépôt

implement-spec

yldgio/vibe-grimoire

Autonomously implement a specification produced by the specify skill. Reads the spec document, builds a task queue in the session database, implements tasks in parallel where dependencies allow, runs deterministic checks, spawns adversarial verification (different model), and iterates until all evaluation criteria pass or convergence is reached. Use when the user has a spec document (from the specify skill or a similar structured spec) and wants it implemented with guaranteed quality verification. Trigger phrases: "implement this spec", "build this", "execute the spec", "implement-spec", "start implementation", "make it happen", or when the user points to a ./specs/*.md file and asks to build it. Also use when the user has just finished using specify and says "now build it", "go", or "implement".

2026-07-153

specify

yldgio/vibe-grimoire

Guide the user through a structured specification process: define the goal, specify exactly what to build (and what NOT to build), and establish measurable evaluation criteria — all before implementation begins. Produces a living spec document. Use when the user has a goal or feature idea and wants to define the spec, says "specify this", "what's the spec", "define the specification", "how do I achieve this goal", "break this down", "what do I need to build", "write a spec", "define requirements", wants to create a specification with verification criteria, or has just finished using the-goal and wants to turn the goal into a precise, implementable specification. Also use when the user wants to define evaluation criteria before coding, or mentions "adversarial verification", "quality criteria", or "acceptance criteria".

2026-07-153

copilot-extension

yldgio/vibe-grimoire

Author, validate, and debug GitHub Copilot CLI extensions that add tools, commands, hooks, or session-event behavior. Use when creating or reviewing a Copilot CLI extension, wiring `joinSession`, deciding between project, user, or session scope, troubleshooting extension loading, or adding a custom Copilot CLI tool or slash command. Also use when the user wants a custom Copilot CLI extension scaffold or asks how extensions work.

2026-07-093

cowork-plugin-builder

yldgio/vibe-grimoire

Interview the user step-by-step to gather every detail needed to build a Microsoft 365 Copilot Cowork plugin package (manifest.json + skills + optional MCP connectors), then produce a complete, self-contained build prompt the user can review or hand off for execution. Use when the user asks to "create a cowork plugin", "build a copilot plugin", "make a M365 copilot agent package", "package my skills as a plugin", "create a copilot agent with MCP", "build a plugin for copilot cowork", or "wizard me through a cowork plugin". Do NOT use for: creating a single personal skill (use the `skills` skill instead), installing an existing plugin, troubleshooting plugin uploads that already exist, or general M365 admin questions.

2026-06-223

the-goal

yldgio/vibe-grimoire

Extract and clarify the real goal behind a feature, change, or idea through a focused interview. Inspired by Goldratt's *The Goal*. Use this skill whenever the user has a vague idea, a new feature request, or a change they want to make but the underlying goal is unclear, implicit, or too broad. Also use when the user says things like "I want to build X" without articulating why, or when scope creep is a risk and the real constraint needs to be identified first. This skill does not plan or solve — it only finds the goal.

2026-06-183

playbook-design

yldgio/vibe-grimoire

Interview the developer about their workflow goals and produce a valid Playbook YAML file saved to ./playbooks/<name>.yml. A Playbook is a machine-executable workflow graph: Phases (logical groupings) containing Tasks (atomic executable units with inputs, outputs, dependencies, and success criteria). Trigger this skill when the user wants to design, create, edit, or author a repeatable multi-step agentic workflow. Covers the full interview → validate → save flow, including updating existing playbooks.

2026-06-033

name

cleanup-writing

description

Cleanup Writing

Edit and improve a piece of writing section by section — fixing information order, improving clarity, and tightening prose — then deliver the full revised document.

Process

1. Structure the document

Divide the writing into sections based on its headings. If no headings are present, propose a logical division based on content and flow.

2. Confirm the plan

Present the proposed section breakdown and order to the user. If the user disagrees, revise the structure before rewriting anything — rewriting in the wrong structure wastes effort.

3. Rewrite each section

For each section in order:

Rewrite to improve clarity, coherence, and flow
Keep paragraphs short — no more than 240 characters each. Short paragraphs reduce cognitive load, force one idea per paragraph, and keep readers moving forward; long paragraphs bury the point
Cut filler words, passive voice, and redundant phrases
Preserve the author's voice — edit, don't replace

4. Deliver the revised document

Output the complete revised document in full. Do not output only the changed sections — the user needs to see how the whole piece reads together as a continuous flow.

After delivering, ask: "Would you like me to adjust the tone, tighten any section further, or rethink the structure?"