Install
$ agentstack add skill-aref-vc-syntax-style-skill-syntax-style-skill ✓ 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
Syntax Style
Sentence-level craft, distilled from Virginia Tufte's Artful Sentences: Syntax as Style (Graphics Press, 2006). The book's thesis: the arrangement of words is not decoration on top of meaning, it is part of the meaning. A sentence's shape does work. This skill turns that into a small set of moves you can apply on demand.
When to use this
Apply it whenever you are producing or revising prose and the sentences matter: essays, posts, landing copy, emails that need to land, talk scripts, documentation that should read well. It works at two levels: the single sentence, and the flow between sentences in a paragraph.
It is not a grammar checker and not a voice generator. It assumes the content and the voice are decided; it shapes how the words are arranged.
The one model to hold in your head
Most artful sentences are a base clause plus free modifiers attached at the front, the middle, or the end. The same model produces a two-word sentence and a sixty-word one.
base clause: The engine failed.
+ end modifiers (right): The engine failed, a dull cough and then silence, the boat already drifting toward the rocks.
+ front modifier (left): Two miles from shore, the engine failed.
+ mid-branch modifier: The engine, sputtering once, failed.
Right-branching, where modifiers accumulate after a complete base clause, is the workhorse and the book's signature move. The artful version of a flat passage is often longer, not shorter. Two failure modes sit on either side: all base and no modifier is monotone (and chopping a passage into short sentences is just a different monotone), while length built from nested "which/that" clauses instead of free modifiers is fog. See principles.md.
How to apply it
Editing existing prose — run the pass in checklist.md. Read for rhythm first, then fix one thing at a time. Do not rewrite everything; change the sentences that are doing no work.
Drafting new prose — write the plain version first, then look at structures.md and reach for the move that matches what each key sentence is trying to do. Punch wants a short sentence. Equivalence wants parallelism. A definition wants an appositive.
Killing AI-flatness — kill-list.md names the patterns that make prose sound machine-generated and gives the structural fix for each. The fix is always "reach for a specific move", not "add more words".
The reference files
principles.md— the core theses. Read this first; it is the why.structures.md— the 14 syntactic moves as a goal → structure table, each with how to build it and a worked example.kill-list.md— flat and AI-sounding patterns, each paired with the move that fixes it.checklist.md— the revision pass: sentence level, then paragraph cohesion.before-after.md— twelve plain → crafted pairs across the structures.cheatsheet.html— one-page printable reference.
Three rules that override the rest
- Repetition is a tool, not an error. Deliberate repetition builds rhythm and insistence ("a second is a second is a second"). Do not flatten it. The target is monotony, which is accidental sameness, not repetition, which is chosen.
- Variation cuts both ways. The common failure is sentences all the same length and opening. But a page of clipped short sentences is just as monotonous as a page of long ones. Vary length in both directions, and let one genuinely long sentence sit next to one genuinely short one.
- Shorter is not automatically better. When a long sentence fails, the usual cause is bound-modifier glut, not length. The fix is to rebuild it on a clean base clause with free modifiers, not to chop it into fragments. The triad is one option among many; prefer the pair and antithesis, and reach for three only when three is the real number.
All examples in this skill are written for the skill. The book quotes roughly a thousand sentences from working writers; none are reproduced here. The techniques are attributed to the book; the example sentences are not from it.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: aref-vc
- Source: aref-vc/syntax-style-skill
- 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.