What is blog.write_tutorial_readme?

A guide for writing practical tutorials that teach engineers how to use one tool or understand one concept.

It is for producing step-by-step engineering tutorials with setup commands, verification steps, and links to documentation.

It provides a structure that covers the purpose, prerequisites, setup, key ideas, and hands-on use without becoming a broad survey.

blog.write_tutorial_readme — Skill for Claude Code by gpsaggese

Install

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.

Any agent

npx skills add gpsaggese/helpers --skill blog.write_tutorial_readme

Clone the repo

git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/blog.write_tutorial_readme/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/blog.write_tutorial_readme)

Your own site

<a href="https://agentmods.dev/skills/gpsaggese/helpers/blog.write_tutorial_readme"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/blog.write_tutorial_readme/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gpsaggese/helpers/blog.write_tutorial_readme"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/blog.write_tutorial_readme.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 699 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00011	$0.00699
Opus 5.5	$0.00004	$0.00280
Sonnet 5.5	$0.00002	$0.00140
Haiku 4.5	$0.00001	$0.00070

Measured yesterday against content hash 14d85425edd2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

blog.write_tutorial_readme scanned grade C with 2 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 yesterday.

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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

> curl -LsSf https://astral.sh/uv/install.sh | sh

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

> curl -LsSf https://astral.sh/uv/install.sh | sh

.claude/skills/blog.write_tutorial_readme/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Goal

Write clear, hands-on tutorials that help engineers quickly learn a new tool, technique, or concept
Tutorials should be practical and immediately applicable, not theoretical surveys

Audience

Target: Software engineers and technical practitioners
Skill level: General to intermediate (some programming knowledge assumed)
Goal: Readers can use the tool or technique effectively after reading

Tutorial Structure

Follow this outline:
1. Introduction (1-2 paragraphs)
  - What is this tool or concept? Why should engineers care?
  - When to use it (not just "always") and which tools solve similar problems
  - Links to official docs: installation, documentation, tutorial
2. Prerequisites (if any)
  - Required knowledge or tools
3. Installation/Setup (if applicable)
  - Clear, copy-paste ready commands
  - Verify the installation with a simple test
4. Core Concepts (1-2 paragraphs)
  - Explain 2-3 key ideas

Guidelines

Length

Target 10-15 minutes of reading time (roughly 1500-2500 words)
Focus on the 80% use case. Avoid covering everything

Template

Use website/docs/blog/posts/draft.blog_template.md as template

Code Examples

Use copy-paste ready code blocks, with bash or language-specific highlighting
Include expected output, so readers know it worked
For shell commands, show the prompt style, e.g.,
- On macOS and Linux using the official installer:
```
> curl -LsSf https://astral.sh/uv/install.sh | sh
```

Platform Coverage

Focus on macOS and Linux

Tone & Voice

Direct and practical ("use this when..." not "one might consider...")
Active voice, short sentences
Assume busy engineers. Do not be overly casual

Visuals

Include diagrams only if they clarify workflow or architecture
Use simple mermaid or graphviz diagrams, or external images, if needed
Do not over-decorate

Formatting

Follow .claude/skills/markdown.rules.md and .claude/skills/text.rules.md

Read the full file on GitHub · 85 lines

Changes

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.

yesterday First seen · 85 lines · 11 tokens per session scan C 14d85425edd2

Subscribe to this mod's changes

blog.write_tutorial_readme is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 699 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-06.

Learning and teaching Writing and docs

blog.write_tutorial_readme next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
blog.write_tutorial_readmegpsaggese/helpers	Skill	158	today	Apache-2.0	C	11	Claude Code
hr-onboardingnexu-io/open-design	Skill	106k	today	Apache-2.0	A	62	Claude Code, Codex
book-mirrorgarrytan/gbrain	Skill	32k	today	MIT	A	138	Claude Code
exam-forecastanthropics/claude-for-legal	Skill	9.9k	today	Apache-2.0	A	73	Claude Code
lean-formalizewanshuiyin/Auto-claude-code-research-in-sleep	Skill	19k	yesterday	MIT	A	81	Claude Code
deck-course-modulenexu-io/html-anything	Skill	9.4k	yesterday	Apache-2.0	A	25	Claude Code, Codex
eli5companion-inc/feynman	Skill	10k	7d ago	MIT	A	63	Claude Code, Codex

blog.write_tutorial_readme