technical-writing
100 / 100 · Low risk
Fine to try.
Write, edit, review, or audit user-facing documentation for the eve repository. Use for changes under docs/, documentation tied to eve APIs or CLI behavior, docs work based on Slack or support feedback, and requests to make eve docs clearer, more natural, or less AI-patterned while verifying claims against current source, tests, CLI help, public releases, and repository conventions.
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'technical-writing' ] || [ -L ~/.agents/skills/'technical-writing' ]; then echo 'A skill folder named technical-writing already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/vercel/eve' "$d" && git -C "$d" checkout --quiet 'be1addaaa5b7c2b75537b58767a27c3fdb595931' -- '.agents/skills/technical-writing' && mkdir -p ~/.agents/skills && cp -R "$d"/'.agents/skills/technical-writing' ~/.agents/skills/'technical-writing' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'technical-writing' ~/.claude/skills/'technical-writing' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/vercel/eve/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-14 | be1adda | 100 |
| 2026-11-10 | effa1a3 | 100 |
| 2026-11-07 | 35fc078 | 100 |