sessions-to-blog
Generate MDX blog posts or recaps from session logs in `sessions/articles`. Use when the user asks to turn daily session notes into publishable blog posts, define writing style or linking rules for those posts, or produce MDX drafts that follow the project's standards and file location.
When & Why to Use This Skill
The sessions-to-blog Claude skill automates the transformation of raw session logs into high-quality, publishable MDX blog posts. It ensures a consistent brand voice, adheres to project-specific MDX standards, and manages complex internal linking, making it an essential tool for developers and content creators looking to streamline their technical documentation and blogging workflows.
Use Cases
- Developer Log Transformation: Automatically convert daily technical session notes and logs into structured MDX devlogs for public or internal engineering blogs.
- Project Progress Recaps: Generate weekly project summaries or 'What's New' posts by synthesizing multiple session logs while maintaining consistent style and cross-referencing.
- Technical Documentation Updates: Turn raw artifact descriptions and decision logs into formatted MDX documentation drafts that follow pre-defined project style guides and linking rules.
| name | sessions-to-blog |
|---|---|
| description | Generate MDX blog posts or recaps from session logs in `sessions/articles`. Use when the user asks to turn daily session notes into publishable blog posts, define writing style or linking rules for those posts, or produce MDX drafts that follow the project's standards and file location. |
Sessions To Blog
Overview
Create publishable MDX blog posts from sessions/articles session logs with consistent voice, structure, and internal links, aligned to project standards.
Workflow
Resolve project standards and output location
- Find the project's MDX article standards and output location (check repo docs, AGENTS, README, or content guidelines).
- If standards or location are not found, ask the user before drafting.
Clarify scope and output
- Ask for date range, audience, and desired length if not provided.
- Use the language of the user's prompts in the logs; confirm if mixed or unclear.
Gather source entries
- Read the relevant
sessions/articles/YYYY-MM-DD.mdblocks for the selected dates. - Extract: intent, actions, artifacts, decisions, progress, open questions, and any file paths.
- Read the relevant
Plan the post
- Build a short outline using the template in
references/examples.md. - Select 3 to 7 key highlights; prioritize user intent and outcomes.
- Build a short outline using the template in
Draft in the defined style
- Follow
references/style-and-structure.md. - Keep facts grounded in the logs; mark uncertainty explicitly.
- Follow
Apply internal linking rules
- Follow
references/linking-rules.mdfor links to source logs, files, and related posts.
- Follow
QA pass
- Check for missing sources, broken links, and inconsistent tense.
- Ensure the post is readable without the raw logs.
References
references/style-and-structure.mdfor voice, tone, structure, and language rules.references/linking-rules.mdfor internal links and citation conventions.references/examples.mdfor input and output examples and a lightweight template.