Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Lion-1209/coderio --skill lion-writing-skillsgit clone --depth 1 https://github.com/Lion-1209/coderioWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/lion-1209/coderio/lion-writing-skills)<a href="https://agentmods.dev/skills/lion-1209/coderio/lion-writing-skills"><img src="https://agentmods.dev/badge/skills/lion-1209/coderio/lion-writing-skills/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lion-1209/coderio/lion-writing-skills"><img src="https://agentmods.dev/badge/skills/lion-1209/coderio/lion-writing-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00018 | $0.01695 |
| Opus 5 | $0.00009 | $0.00847 |
| Sonnet 5 | $0.00004 | $0.00339 |
| Haiku 4.5 | $0.00002 | $0.00169 |
Grade A, and why
lion-writing-skills scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- lion-writing-skills — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lion Writing Skills
概述
Lion-Skills 的"造 skill 流水线"：按本仓库规范，把一个重复的工作流沉淀成可复制、经验证的 skill。
核心原则：skill 是给未来 Claude 读的"操作手册"——它的价值不在于你写了什么，而在于未来的 Claude 在触发它时，能照着做出正确的事。
何时使用
- 用户想新增一个 skill（"帮我加个 X 的 skill"）
- 用户想修改/优化现有 skill
- 用户想检查某个 skill 写得是否符合规范
- 想把对话里反复出现的工作流沉淀成 skill
不该做成 skill 的情况：一次性的、项目特定的约定（放 CLAUDE.md）、能用简单校验自动化的（写成校验脚本而不是文档）。
只是审查/优化现有 skill 时：直接对照下文相关规则做合规判断即可，不必每次重走第 1 步"值不值得做"四问——那是新增 skill 的决策；现有 skill 要不要继续存在，是另一个问题。
核心内容
第 1 步：判断值不值得做
回答四个问题（都"是"才值得做）：
- 高频吗？（反复出现，不是一次性的）
- 跨项目吗？（不止一个代码库用得到）
- 有判断空间吗？（需要决策/经验，不是机械操作——机械操作写成脚本）
- 未来 Claude 不读这个 skill，会做错或做差吗？
任何一个答"否"，就别做成独立 skill：项目特定的约定放 CLAUDE.md，能机械自动化的写成校验脚本，一次性的直接在对话里处理。
第 2 步：复制模板，填 frontmatter
新 skill 建在 skills/<name>/SKILL.md（同名目录，里面放 SKILL.md，可选再放 evals/ 存验证用例）。复制 template/SKILL.md 过去，填两个字段：
name：全小写、连字符，用 skill 的核心动作或概念命名（如commit-message、error-handling、onboarding-unknown-codebase）。不要下划线或驼峰（commit_message、CommitMessage都错）description：只写"何时触发"，第三人称，中文，用三段式——①触发场景（"当用户……时使用"）+ ②典型信号（把用户实际会说的原话尽量列全）+ ③涉及关键词（中文说法 + 常见英文术语）。这样覆盖面广、不易漏触发。上限 1024 字符
关键：description 绝不能写工作流（"先做 A 再做 B"）。原因——测试发现 Claude 会偷懒只读 description 跳过正文。把流程留给正文。
第 3 步：写正文
按这个骨架：概述 / 何时使用 / 核心内容 / 常见错误（参考 template/SKILL.md）。
写作约定：
- 解释 why，少用全大写 MUST（讲道理比下命令管用）
- 一个优秀例子 > 多语言版本；例子尽量覆盖该 skill 最核心的 2–3 类场景，而非只示范单类
- 正文 < 500 行；超了拆
references/ - 中文为主，工具名/术语保留英文
第 4 步：轻量验证
前置：先确认目标 SKILL.md 在手（文件路径或正文）。用户只说"帮我验证"却没给内容时，先向用户要；skill 还在草稿态没落盘时，把全文直接贴进 subagent 的 prompt 即可，效果等同落盘。
写 2–3 个真实测试 prompt，用 subagent 带着新 skill 跑，看产出对不对。这一步最容易被跳过，但也最能发现问题，别省。
怎么算"真实" prompt：要像真实用户会说的、带具体细节——好的如"我把组件状态从 useState 换成 useReducer，还修了个内存泄漏，写个 commit message"；坏的如"测一下你的能力"（太抽象，既测不出触发、也测不出指引力）。
范式：派一个 general-purpose subagent（让它只读 skill、把产出放进报告，不要改动仓库——除非任务就是要它落地文件），prompt 写「读取 skills/<name>/SKILL.md，然后按其指引处理这个需求：<测试 prompt>。完成后报告：你走了哪些步骤、产出什么、哪里卡壳」。多个 prompt 可以并行派。
通过标准：subagent 的产出 (a) 解决了用户问题，且 (b) 遵循 skill 的设计意图。把该 skill 正文里"该走的流程""该遵循的约定"抽成几条可勾选项来核（如 description 没写工作流、正文解释了 why、例子覆盖核心场景）。跑偏长这样：该走五步的跳过了验证、该三段式的 description 写成了能力清单、该按维度系统的退化成逐条枚举——出现这些就改正文重跑。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 86 lines · 18 tokens per session scan A 7c036c454ee0
lion-writing-skills is a skill published in the GitHub repository Lion-1209/coderio (9 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 1,695 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction using playwright-cli. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, extract information from web pages, mock network requests, manage browser…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop-shell.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.