Install
$ agentstack add skill-msimchowitz-writing-skills-writing-cadence ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Writing Cadence
Shape rhythm around meaning and emphasis. Preserve every supported claim, qualification, citation, and recognizable voice signal. Sentence variety is a result of clear relationships, not a target sequence of short and long lines.
Read [cadence-principles.md](references/cadence-principles.md) when the task requires a full cadence edit or an explanation of the underlying principles.
Diagnose The Passage
Read at paragraph scale before changing individual sentences. Mark:
- runs of three or more sentences of roughly ten words or fewer;
- several neighboring sentences with similar lengths;
- repeated openings, especially "This," "The," "It," "We," or the same
dependent-clause frame;
- repeated subject-verb-complement skeletons;
- abstract process nouns such as "review," "analysis," or "evaluation" that
hide the actor or imply an event the source never established;
- long sentences that contain more than one main inference;
- long gaps between a grammatical subject and its verb;
- endings that place routine setup after the important result; and
- paragraphs whose final sentence merely restates the topic, shifts to
housekeeping, or adds a vague conclusion; and
- paragraph breaks that conceal the same rhythm on both sides.
Treat these as diagnostics. A run may be deliberate, and a technical passage may need repeated syntax for a fixed taxonomy or proof. Compare the pattern with the writer's sample and the genre before revising it.
Scan Repeated Contrast Frames
Mark every contrast built from a reusable difference template, including:
- "not X but Y" and "not only X but also Y";
- "This is not X. It is Y.";
- "X, not Y" used as a sentence-ending correction;
- "treats X as Y, not Z";
- "treats X like Y rather than Z";
- "rather than merely X, Y";
- repeated "unlike X, Y" openings; and
- several neighboring sentences built around "while," "whereas," or "in
contrast."
Keep a contrast when the distinction limits a scientific claim or separates two mechanisms. Revise repeated templates by stating the positive claim, naming the governing comparison once, or distributing the distinction across different sentence structures. Do not erase a meaningful negative result.
Rebuild Rhythm From Relationships
- Identify the point that deserves emphasis in each sentence and paragraph.
- Link backward near the opening with the subject, condition, or established
context that the reader already knows.
- Keep the subject near its verb unless an intervening phrase is truly
secondary.
- Name the actor when an abstract process hides who acts. If no review,
analysis, or evaluation occurred, state the actual contrast between properties directly.
- Place the important new result near syntactic closure when that ordering
matches the logic.
- Join short neighboring sentences when one supplies the other's cause,
condition, contrast, or consequence.
- Split a long sentence when it makes two independent claims, changes
subjects repeatedly, or postpones the governing verb.
- Vary openings only when the new opening changes emphasis or improves the
link to the previous sentence.
- Reserve a very short sentence for a conclusion that merits the pause.
Do not alternate lengths mechanically, add fragments for texture, or move a modifier merely to avoid repetition. These changes produce visible variety without improving the reading experience.
Let Paragraphs End Where The Reasoning Arrives
Identify the paragraph's intellectual destination before revising its last sentence. A supported consequence, a condition that limits the claim, an unresolved tension, or a concrete fact can provide natural closure. A transition may also end quietly when the next paragraph supplies the consequence.
Do not append a summary, slogan, generic implication, or sentence about the document merely because the paragraph seems to need a conclusion. If the penultimate sentence already completes the thought, cut the weaker ending. If the important point appears earlier, reorder the paragraph instead of writing a more emphatic final line. Audit abstracts, section openings, and section closings separately because readers assign those positions additional weight.
Read At Speaking Pace
Read the revision aloud or at a deliberate speaking pace. Check where a reader naturally pauses, which words receive stress, and whether syntactic closure lands on the intended information. Rework any passage that:
- requires the same breath pattern several times in a row;
- gives equal emphasis to claims of unequal importance;
- makes the reader wait too long for the main verb;
- ends several sentences with the same grammatical shape; or
- repeatedly closes paragraphs with a miniature summary or slogan; or
- sounds varied on a sentence-length count but monotonous aloud.
Compare the revision with the source once more. Restore any technical distinction, uncertainty, or personal cadence lost during restructuring.
Invocation Boundary
When another skill invokes this one, return only the revised prose or cadence findings requested by the caller. Do not invoke Humanizer, general-writing, better-usage, or academic-voice from this skill; Humanizer owns the integration so the shared writing pipeline does not cycle.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: msimchowitz
- Source: msimchowitz/writing-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.