Install
$ agentstack add skill-msimchowitz-writing-skills-better-usage ✓ 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
Better Usage
Choose words that express the relation the sentence actually asserts. A sentence can be grammatical and still sound wrong because its subject cannot perform the named action, its object or complement does not fit the relation expressed by the verb, or an important intermediate has been omitted.
For a full semantic-usage pass, read [compatibility-examples.md](references/compatibility-examples.md). Treat the examples as a curated diagnostic set, not a substitution dictionary.
Recover The Intended Relation
- Identify the grammatical subject, main verb, and object or complement.
- Paraphrase the intended relation without reusing the suspect verb.
- Ask whether the subject can literally perform that action in this domain
and whether the verb can take that object or complement with the intended meaning.
- Distinguish an accidental mismatch from accepted technical shorthand or a
deliberate metaphor that clarifies the idea.
- Preserve the claim, uncertainty, and domain terminology while repairing the
relation.
- Check whether the sentence implies a review, analysis, or evaluation that
the source never established.
Do not stop after finding a more specific verb. A new verb can remain semantically loose.
Name A Missing Intermediate
When the subject and verb do not connect directly, identify the omitted link. Useful questions include:
- What entity actually acts?
- What property, extent, interpretation, or consequence changes?
- Under which conditions does the relation hold?
- Who performs the inference or needs the information?
For example, a claim does not stop, and saying that conditions "limit the claim" still leaves the affected dimension unnamed. Write "the conditions limit the extent of the claim" or state that "the claim applies only under these conditions." If the intended question concerns implications rather than validity, ask where the consequences of the theorem end.
Insert an intermediate only when it names a real part of the relation. Do not pile up abstract nouns merely to make the sentence sound exact.
Respect Conventional Agency
Keep established scholarly shorthand when it is clear in context. A theorem may state or imply a result, evidence may support a claim, a figure may show a measurement, and an algorithm may choose an action. These verbs have stable technical meanings.
Recast the sentence when the shorthand hides a distinction that matters. For example, "the evidence explains the effect" may collapse two relations: the evidence supports an explanation, while the authors or analysis provide it.
Check The Repair
- Confirm that the revised subject can perform the verb.
- Confirm that the object or complement fits the relation expressed by the
verb.
- Confirm that any intermediate noun identifies a necessary relation rather
than adding nominal clutter.
- Recheck epistemic force. Do not turn support into proof or correlation into
explanation.
- Remove an implied review or evaluation when the source states only a
contrast between properties.
- Compare with the source to ensure that the repair adds no fact, mechanism,
condition, or conclusion.
- Do not add procedural detail, sequence, or emphasis merely to replace a
metaphor. A semantic repair does not license unsupported texture such as "step by step."
Invocation Boundary
When another writing skill invokes this skill, return only the revised prose or the requested usage findings. Do not invoke Humanizer, general-writing, or the writing-cadence or academic-voice skills; the calling skill owns the larger prose pipeline.
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.