Good Writing
Write clear, human-sounding prose and generously cite sources with links.
Install
$ agentstack add skill-yassimba-loom-good-writing ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-yassimba-loom-good-writing) 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
Good Writing
Use this skill when writing or editing anything humans will read: website copy, docs, emails, case studies, proposals, blog posts, Slack announcements, etc.
Rules
- Sound like a person, not a brochure. Use contractions, active voice, and short sentences.
- Cut AI filler. Avoid: delve, landscape, tapestry, robust, seamless, cutting-edge, transformative, pioneering, leverage, in today's world, it's important to note, ultimately, moreover, furthermore.
- One idea per sentence. If a sentence has more than one comma, split it.
- Be specific. Say what happened, not what "represents a paradigm shift."
- No em dashes. Use periods, commas, or parentheses.
- Generously cite sources. When you mention a fact, standard, tool, article, repo, or prior decision, link to it.
- Prefer primary sources: official docs, the actual file in the repo, the PR, the issue, the design doc.
- Use absolute
/workspace/...paths when citing files inside the container. - Use full URLs for external sources.
- Place links inline or in a "Sources" section — whichever reads better.
- Defer to the project's voice. If the repo has a style guide or brand notes, follow those first.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Yassimba
- Source: Yassimba/loom
- License: Apache-2.0
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.