blog-post

Included with Lifetime

$97 forever

This skill should be used when the user asks to "write a blog post", "draft a blog post", "create a blog post", "write an article about", or wants to produce a markdown blog post on any topic. Outputs to ~/claude.nosync/posts/.

Writing & Docs

What this skill does

# Blog Post Drafter

Draft a well-structured blog post in markdown and save it to `~/claude.nosync/posts/`.

## Workflow

### 1. Clarify the Topic

If the user provided a clear topic, proceed. Otherwise, ask:
- What is the topic or title?
- Who is the target audience? (developers, general public, beginners, etc.)
- What tone? (casual, professional, tutorial, opinion)
- Approximate length? (short ~500 words, medium ~1000, long ~2000+)

Default to: developer audience, professional-but-approachable tone, medium length (~1000 words).

### 2. Create Output Directory

Run `mkdir -p ~/claude.nosync/posts` to ensure the output directory exists.

### 3. Generate the Slug

Derive a URL-friendly slug from the topic:
- Lowercase, hyphens instead of spaces
- Remove special characters
- Keep it concise (3-6 words max)

The filename format is: `YYYY-MM-DD-slug.md` using today's date.

### 4. Draft the Blog Post

Write the post with this structure:

```markdown
---
title: "Post Title"
date: YYYY-MM-DD
slug: the-slug
tags: [relevant, tags]
draft: true
---

# Post Title

Introduction paragraph — hook the reader with a clear statement of what the post covers and why it matters.

## Section Headings

Body content organized into logical sections. Each section should:
- Make one clear point
- Use concrete examples or code snippets where relevant
- Flow naturally to the next section

## Conclusion

Summarize key takeaways. End with a call to action or thought-provoking question.
```

#### Writing guidelines

- **Lead with value**: Open with the problem or insight, not background filler.
- **Be concrete**: Use examples, code snippets, or data instead of vague claims.
- **Short paragraphs**: 2-4 sentences max. Break up walls of text.
- **Use subheadings**: Every 200-300 words, add a heading to guide scanning.
- **Active voice**: "React renders components" not "Components are rendered by React".
- **Cut filler words**: Remove "basically", "actually", "in order to", "it should be noted that".
- **Code blocks**: Use fenced code blocks with language hints when including code.

### 5. Save the File

Write the completed post to `~/claude.nosync/posts/YYYY-MM-DD-slug.md`.

### 6. Present Summary

After saving, confirm:
- File path where the post was saved
- Word count
- A brief summary of what was written
- Suggest 2-3 possible improvements or follow-up edits the user might want

Files: 1

Size: 2.6 KB

Complexity: 12/100

Category: Writing & Docs

Source: https://github.com/sejas/ai-code-skills/tree/main/skills/blog-post

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