Technical Blog Post
Use when writing a technical blog post from raw project data like research notes, session logs, Reddit/LinkedIn drafts, code, hex dumps, or screenshots. Also use when Sam says "write a blog post about [project]" or "turn this into a post".
Install
/plugin marketplace add sam-dumont/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sam-dumont/claude-skills --skill technical-blog-postgit clone --depth 1 https://github.com/sam-dumont/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/technical-blog-post/skills/technical-blog-post ~/.claude/skills/technical-blog-postPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Technical Blog Post from Raw Data ## Overview A process skill for turning raw project material into a structured technical blog post. Complements `sams-voice` (which handles tone and language): this skill handles structure and workflow. **REQUIRED:** Always invoke `sams-voice` skill alongside this one. Voice = how it sounds. This skill = how it's organized. ## When to Use - Sam asks to write a blog post about a project - Raw source material exists (research notes, session logs, drafts, code) - The post is technical: "I built/decoded/reverse-engineered/automated X" ## When NOT to Use - Opinion pieces or commentary (no raw data to process) - Short announcements (no structure needed) - Non-technical content ## Process ### Phase 1: Gather Find and read all source material in the project repo. Look for: | Source Type | Where to Find | What It Contains | |-------------|---------------|------------------| | README | Root | Project summary, usage, results | | Research notes | `RESEARCH_NOTES.md`, `docs/` | Chronological narrative of discoveries | | Format specs | `*_SPEC.md`, `*_FORMAT.md` | Technical details, struct layouts | | Session logs | `SESSION_LOG.md` | Claude Code session summaries | | Drafts | `.nocommit/`, `docs/drafts/` | Reddit, LinkedIn, or blog drafts | | Code | `src/`, `*.py`, `*.go` | Implementation details | | Tests | `tests/`, `*_test.*` | Validation approach, edge cases | | Binary data | `*.hex`, hex dumps in notes | Raw data examples |
Details
- Skill name
technical-blog-post- Repository
- sam-dumont/claude-skills
- Path
plugins/technical-blog-post/skills/technical-blog-post/SKILL.md- License
- MIT
- Repo updated
- 3 November 2026
FAQ
What does the Technical Blog Post skill do?
Use when writing a technical blog post from raw project data like research notes, session logs, Reddit/LinkedIn drafts, code, hex dumps, or screenshots. Also use when Sam says "write a blog post about [project]" or "turn this into a post".
How do I install the Technical Blog Post skill?
Claude Code plugin: /plugin marketplace add sam-dumont/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Technical Blog Post popular?
It lives in sam-dumont/claude-skills, which has 38 GitHub stars and 4 forks.
Related skills
Advanced Code Quality
38sam-dumont/claude-skills
Use when going beyond basic linting to enforce advanced Python code quality gates. Triggers on: cognitive complexity, code duplication detection, architectural enforcement, import boundaries, dependency hygiene, test quality beyond coverage, mutation testing, docstring coverage, type coverage, AI-generated code detection, AI slop detection, complexipy, jscpd, import-linter, deptry, diff-cover, mutmut, interrogate, sloppylint, refurb, pylint design checks, wily, radon maintainability, pytestarch, griffe, "bulletproof Python", "tighten quality gates", "advanced quality checks", "beyond ruff and
Code Quality
38sam-dumont/claude-skills
Automatically triggered when setting up Python code quality tooling, configuring linters, adding type checking, improving code standards, running code quality checks, setting up pre-commit hooks, or auditing Python code for quality issues. Applies when discussing: ruff setup, mypy configuration, code formatting, linting rules, cyclomatic complexity, dead code detection, file length limits, pre-commit hooks, Makefile targets for quality, uv-based workflows, pyproject.toml configuration, or "check my code quality". Also triggers on: "set up linting", "add type checking", "configure ruff", "forma
Code Security
38sam-dumont/claude-skills
Automatically triggered when running security scans, auditing code for vulnerabilities, checking dependencies for CVEs, reviewing code for security issues, or hardening Python applications. Applies when discussing: security audit, vulnerability scan, bandit, pip-audit, dependency vulnerabilities, OWASP, injection, path traversal, secrets detection, insecure deserialization, auth bypass, or "is this code secure?". Also triggers on: "run security checks", "find vulnerabilities", "security review", "check for CVEs", "audit dependencies", "security lint", "pen test this code", "harden this applica
Writing Evergreen Comments
43obra/clank
Write comments explaining WHAT and WHY, never temporal context or history
Naturalize Ukrainian
36dariia-m/my_claude_skills
Edit Ukrainian texts to sound natural without loss of meaning. Specialized for three problem types: (1) texts translated into Ukrainian (human, DeepL, Google Translate) that carry English or Russian syntax and calques; (2) texts written by AI directly in Ukrainian; (3) texts written by AI in English and then translated into Ukrainian - the worst case, combining AI cliches with translationese. Trigger whenever the user asks to edit, polish, naturalize, or de-AI a Ukrainian text, says a text "звучить як переклад", "звучить штучно", "звучить не по-людськи", asks to "відредагуй", "зроби природніши
Writing Plans
43obra/clank
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.