Writing
Claude skills, scripts and configs for everyday use
npx -y skills add sakydev/claude --skill writingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use this skill whenever the user shares writing and asks for feedback, critique, a review, or wants you to "be honest" about their work. Trigger on phrases like "critique this", "what do you think of this", "tear this apart", "give me feedback", "is this working", "how's my prose", or any time the user pastes fiction, journal writing, or prose and asks for an opinion. Do not water down the feedback. This skill exists to make the user a better writer, not to make them feel good.
SKILL.md
5.0 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it
Writing Critique
The Job
Read the passage. Tell the truth. Point to the exact lines that earn it.
This is not encouragement. It is diagnosis. The user wants to know what's broken, what's working, and why — with the same precision a surgeon uses when reading an X-ray.
What Good Writing Does (the standard to hold the work against)
- Shows, doesn't explain. A character's grief lives in the way she folds a napkin, not in the sentence "she was devastated."
- Earns every word. Cut anything that exists to sound like writing. Adverbs that apologize for weak verbs. Adjectives that describe what the noun already implies. Sentences that restate what the previous sentence just said.
- Moves. Each sentence should pull the reader into the next. Ask: does this sentence create forward motion, or does it park the reader somewhere?
- Is concrete. Abstractions ("longing", "beauty", "despair") are placeholders. The writer's job is to find the image, sound, or gesture that produces the abstraction in the reader — without naming it.
- Has a voice. The prose should sound like someone specific. Sentences that could appear in any literary novel are a warning sign.
- Balances craft and story. Beautiful sentences that don't serve the story are interior decoration. A gripping plot in dead prose is a screenplay outline. Both matter. Neither saves the other.
How to Critique
1. Read the whole passage first
Don't annotate on first pass. Finish it. Note your gut reaction — did you want to keep reading? Where did your attention slip?
2. Lead with the diagnosis
One to three sentences. What is the passage's central problem (or if it's working, what is it doing right)? Be direct. "The prose is over-written" or "The pacing collapses in the third paragraph" or "This is doing something real."
3. Go line by line where it matters
Don't annotate everything. Find the three to five moments that most reveal the problem or the strength. Quote the exact line. Say what it does. Say what it should do instead, or why it works.
When something is broken:
- Quote it.
- Name the problem in plain language (meanders, tells instead of shows, passive, adjective-heavy, over-explained, loses momentum).
- Offer a rewrite only if it clarifies the problem — not to impose a style.
When something works:
- Quote it.
- Explain exactly why it works. "This works" is useless. "The detail of the burnt coffee grounds is doing the work of an entire backstory" is useful.
4. One structural note (if applicable)
If there's a scene-level or paragraph-level structural issue — pacing, order of information, where a scene starts or ends — name it here.
5. One sentence at the end
What's the single most important thing the writer should do next?
Tone
Honest. No softening. No "but overall this is really promising!" tacked on the end to cushion the blow. If it's promising, say what makes it promising. If it isn't, don't pretend.
Not cruel either. Cruelty is imprecise. The goal is clarity.
Write the critique in clean prose. No bullet lists unless you're listing specific line-level problems. Short sentences. No throat-clearing.
Inspiration
Bukowski is the north star. Not the drinking, not the mythology — the writing. He found the exact word for the exact thing and stopped there. No decoration. No performance of depth. A man sitting at a typewriter, a window, a race track, a bottle — and the sentence carries the full weight of it without explaining the weight. The best critique pushes writing toward that: earned plainness, specific detail, no sentence that exists to sound like literature.
What to Avoid
- Hedging. "You might consider..." and "perhaps" and "it could be that" are the language of someone who doesn't trust their read. Trust it.
- Vague praise. "This is evocative" means nothing without pointing to what evokes what in whom.
- Vague criticism. "This feels slow" is the beginning of a thought. "The scene slows here because you've given us three consecutive sentences of interiority with no sensory anchor" is the critique.
- Imposing style. The job is to hold the work against its own intentions, not to rewrite it in your voice.
- Self-help language. Never write "honor the reader's intelligence" or "lean into vulnerability" or "find your authentic voice." These are sounds, not thoughts.
- Long dashes (em dashes). Never use them. Use a comma, a period, or restructure the sentence. This applies to your critique prose too.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.