emil-writing-skills
100 / 100 · Low risk
Fine to try.
How to write skill files that actually change what an agent does — encode process not output, pair every rule with its why, be strict instead of vague, cut lines that don't change behavior, keep skills focused, and test by running. Use when creating a new SKILL.md, reviewing or refining an existing skill, packaging taste or conventions into a reusable skill file, or diagnosing why a skill isn't affecting the agent's output. Triggers on: skill, SKILL.md, skill file, write a skill, create a skill…
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/'emil-writing-skills' ] || [ -L ~/.agents/skills/'emil-writing-skills' ]; then echo 'A skill folder named emil-writing-skills already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/freekmurze/dotfiles' "$d" && git -C "$d" checkout --quiet '26bd6ac3c4ef9afd949dc1de12d96fddc2548710' -- 'config/claude/skills/emil-writing-skills' && mkdir -p ~/.agents/skills && cp -R "$d"/'config/claude/skills/emil-writing-skills' ~/.agents/skills/'emil-writing-skills' && 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/'emil-writing-skills' ~/.claude/skills/'emil-writing-skills' (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/freekmurze/dotfiles/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-13 | 26bd6ac | 100 |