home / skills / jmerta / codex-skills / sessions-to-blog

sessions-to-blog skill

safe

This skill converts daily session logs into publishable MDX blog posts by applying project standards, structure, and internal links.

npx playbooks add skill jmerta/codex-skills --skill sessions-to-blog

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

2.0 KB

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

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

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

3. Gather source entries
   - Read the relevant `sessions/articles/YYYY-MM-DD.md` blocks for the selected dates.
   - Extract: intent, actions, artifacts, decisions, progress, open questions, and any file paths.

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

5. Draft in the defined style
   - Follow `references/style-and-structure.md`.
   - Keep facts grounded in the logs; mark uncertainty explicitly.

6. Apply internal linking rules
   - Follow `references/linking-rules.md` for links to source logs, files, and related posts.

7. 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.md` for voice, tone, structure, and language rules.
- `references/linking-rules.md` for internal links and citation conventions.
- `references/examples.md` for input and output examples and a lightweight template.

Overview

This skill turns session logs from sessions/articles into publishable MDX blog posts or recaps that match project standards. It produces structured MDX drafts, applies internal linking rules, and keeps voice and facts consistent with the logs. The output is ready to drop into the project's content location or to iterate with the author.

How this skill works

The skill locates the project's MDX conventions and output folder, or asks the user if those are missing. It reads chosen sessions/articles/YYYY-MM-DD.md entries, extracts intent, actions, artifacts, decisions, progress, and open questions, then creates an outline and drafts an MDX file following style and linking references. Finally it runs a QA pass for sources, links, and tense consistency before returning the draft.

When to use it

Convert daily or weekly session notes into a publishable post or recap
Create an MDX draft that follows the project’s style and linking rules
Summarize progress and decisions for stakeholders or a team blog
Produce a canonical post that cites session logs and related artifacts
Generate a starting draft for editing and publication

Best practices

Confirm the date range, target audience, and desired length before drafting
Point to the project’s style and linking references or allow me to locate them
Prefer 3–7 highlights to keep posts focused and readable
Flag uncertain facts clearly so reviewers can confirm source details
Review and approve internal links and file path citations during final QA

Example use cases

Turn a week of session logs into a technical progress update with links to PRs and files
Create a user-facing recap that explains decisions and next steps after a sprint
Draft a how-it-went post summarizing experiments, outcomes, and artifacts linked to sessions
Produce MDX-ready content for the blog folder using project-specific link formats

FAQ

What if project standards or output location are missing?

I will ask you to confirm the preferred MDX style and the output folder before drafting. If you prefer, I can suggest default structure and link formats.

How do you handle uncertain or missing facts in logs?

I keep facts grounded in the logs and explicitly mark anything I’m unsure about so reviewers can verify before publication.