SkillsAdd

smithery/kasperjunge

technical-blog-post

Write high-quality technical blog posts with strong structure and clarity.

Installation

$ npx skills add smithery/kasperjunge --skill technical-blog-post
View on skills.sh ↗ Website ↗

Summary

  • Write high-quality technical blog posts with strong structure and clarity.
  • Use when asked to write a blog post, technical article, tutorial, or guide about programming, software, APIs, tools, or technical concepts.
  • Triggers include "write a blog post about...", "create a technical article", "help me write about [technical topic]", or requests for tutorials and how-to guides.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from smithery/kasperjunge.

npx skills add smithery/kasperjunge
opportunity-solution-tree 0 contagious-stepps 0 coding-agent-docs 0 boliga-api 0

Browse all from smithery/kasperjunge

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,036 B
  • docs SUMMARY.md 404 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Technical Blog Post

Write blog posts that respect the reader's time and deliver real value.

Structure

  1. Lead with the problem or value - First paragraph answers "why should I read this?"
  2. Use scannable headings - Readers skip around; let them
  3. Code examples: minimal, complete, runnable
  4. End with takeaways - What can the reader do now?

Principles

Clarity Over Cleverness

  • Simple language; define jargon when unavoidable
  • One idea per paragraph
  • One main thesis per post

Respect Reader's Time

  • Get to the point; cut preamble
  • Every sentence earns its place
  • If it can be a list, make it a list
  • Long posts need a TL;DR at the top

Show, Don't Tell

  • Concrete examples over abstract explanations
  • Real-world use cases over theoretical possibilities
  • Include failures and edge cases encountered

Technical Accuracy

  • Test all code before including
  • Specify versions and dependencies
  • Acknowledge limitations and tradeoffs
  • Link to primary sources (docs, specs, papers)

Authenticity

  • Share actual experience, including what didn't work
  • Write with voice, not corporate speak
  • Admit uncertainty when present
  • Opinionated writing is more useful than hedged writing

The "So What?" Test

Every post must answer: Why does this matter? What can the reader do now that they couldn't before?

Anti-Patterns

Avoid:

  • Long introductions before getting to content
  • "In this post, we will..." preamble
  • Unexplained jargon
  • Code snippets that don't run
  • Hedging every statement
  • Missing context (versions, environment, prerequisites)