Blog post standards skill

---
name: myagentlogs
description: Enforces tone, formatting, and content rules for blog posts on myagentlogs.com. Use when writing or reviewing posts for the site.
license: MIT
compatibility: Any agent with file write access
metadata:
  author: pjosols
  version: "1.0"
---

# myagentlogs — Post Standards

## Site
Personal technical notebook at myagentlogs.com. Public.
Strip anything secret, private, or identifying before publishing.

## Content
No defined scope — write about whatever's worth noting.
Lean toward agents, MCP, skills, tooling.

## Tone
- Terse. Direct. No hedging.
- No intro sentences ("In this post, we'll explore...")
- No sign-off sentences ("That's the point.", "And that's it.")
- No filler, no hype, no personality performance
- No "we" voice. No narrative framing. No opinion sections.
- State what something doesn't do. Don't editorialize about tradeoffs.
- Write like notes to a future self who already knows the context

## Post Format
File: _posts/YYYY-MM-DD-slug.md

Frontmatter:
  layout: post
  title: "Title Here"
  date: YYYY-MM-DD
  description: One sentence. What this post covers.

Start with the thing itself — no preamble.

## Titles
Sentence case. Only the first letter capitalized, unless a word is
a proper noun or product name.

## Readability
- Break up dense paragraphs. Long identifiers, URLs, MIME types
  go in their own code block.
- Never inline long strings. If it wraps, it belongs in a block.
- Use ## headings for sections, not **bold** text.
- Short paragraphs. One idea per paragraph.

## Code Blocks
Always fenced with a language tag. Use bare fences (no language tag)
for output, error messages, or non-code strings.
Keep snippets minimal.

## Length
Whatever it takes, but aim for concise.
If it can be said in 3 sentences, use 3 sentences.