ateles: Skill for Claude Code

.claude/skills/write-blog-post/SKILL.md

write-blog-post is a skill for Claude Code from markmhendrickson/ateles. It costs 51 tokens per session (1,561 once invoked), scanned A, original, MIT.

A blog-writing skill for creating posts that follow a website's style guides, file locations, image rules, and publishing workflow.

In plain words
What is it for?
It is for drafting or finalizing website blog posts, including their content, hero images, key takeaways, and sharing copy.
Why use it?
It helps produce blog drafts that fit the repository's required structure and editorial process.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is markmhendrickson/ateles's own configuration. It tells Claude Code how to work on ateles itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ateles configures →

Reuse

Borrowing it

Nothing to install: this file belongs to markmhendrickson/ateles. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/markmhendrickson/ateles/main/.claude/skills/write-blog-post/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/markmhendrickson/ateles

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.

agentmods badge for write-blog-post

README.md
[![agentmods](https://agentmods.dev/badge/skills/markmhendrickson/ateles/write-blog-post/github.svg)](https://agentmods.dev/skills/markmhendrickson/ateles/write-blog-post)
Your own site
<a href="https://agentmods.dev/skills/markmhendrickson/ateles/write-blog-post"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/write-blog-post/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.

agentmods 80×15 button for write-blog-post

Your own site · 80×15
<a href="https://agentmods.dev/skills/markmhendrickson/ateles/write-blog-post"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/write-blog-post.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,561 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.01561
Opus 5 $0.00026 $0.00781
Sonnet 5 $0.00010 $0.00312
Haiku 4.5 $0.00005 $0.00156

Measured 5d ago against content hash db09dd990085, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

write-blog-post 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 5d 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.

.claude/skills/write-blog-post/SKILL.md · 96 lines

How it starts

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

Write Blog Post

Create or finalize blog posts for the markmhendrickson website following content style rules, draft location, hero image style, and completion requirements. All steps are mandatory; do not treat a post as complete without them.

When to Use

Use this skill when:

  • User says "draft post", "create post", "write post", or similar
  • User asks for a new blog post or essay for the markmhendrickson site
  • User explicitly invokes /write-blog-post

Required Documents (load first)

  1. Content style: docs/content_style_enforcement_rules.mdc — Anti-AI patterns, title/excerpt/body rules, build-in-public requirements, post completion (key takeaways, hero images, share tweet)
  2. Draft location: docs/blog_posts_draft_location_rules.mdc — Where to create posts and manifest entry
  3. Posts structure and hero images: execution/website/markmhendrickson/react-app/src/content/posts/README.md — Hero Image Style Guide, asset checklist, cache workflow
  4. Build-in-public (if applicable): strategy/operations/blog-build-in-public-directives.md — First-person, no CTAs, "How I'm approaching the build"

Workflow

Step 1: Content and location

  1. Create or edit post content (markdown body, title, excerpt).
  2. Location: Content file in execution/website/markmhendrickson/react-app/src/content/posts/{slug}.md (or drafts/{slug}.md for drafts).
  3. Manifest: Ensure entry in execution/website/markmhendrickson/react-app/src/content/posts/posts.json with slug, title, excerpt, published (false for drafts), category, readTime, tags, createdDate, updatedDate. Do not create drafts in reports/ or reports/drafts/.
  4. Apply content style to all properties (title, excerpt, body):
    • Sentence case for title and headers; no dashes (—, –, -) in title or excerpt; no semicolons in excerpt.
    • Anti-AI patterns (no "Furthermore", "leverage", "empower", em dashes, soft questions, motivational language).
    • Body starts with content (executive synthesis or first section); do not repeat title in body.
    • Do not mention ateles (use "my agentic stack", "my setup").
    • Excerpt distinct from executive synthesis bullets; all bullet points end with periods.
    • For build-in-public posts: first-person, "How I'm approaching the build" instead of "Getting started", per blog-build-in-public-directives.md.

Read the full file on GitHub · 96 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.

  1. 5d ago First seen · 96 lines · 51 tokens per session scan A db09dd990085

Subscribe to this mod's changes

write-blog-post is a skill published in the GitHub repository markmhendrickson/ateles (6 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,561 once invoked, about $0.0003 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-09-03.