sessions-to-blog

Included with Lifetime

$97 forever

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.

Writing & Docs

What this skill does

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

Files: 4

Size: 5.8 KB

Complexity: 22/100

Category: Writing & Docs

Source: https://github.com/jmerta/codex-skills/tree/main/sessions-to-blog

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts