agentsclimarketplace
Sign in

Technical blog writer

Skill aizech/bernhard-zechmann-skills/skills/productivity/technical-blog-writer

Write technical blog posts about real engineering challenges. Use when the user wants technical content, blog posts, tutorials, or explanations for mixed audiences including non-technical readers.From its SKILL.md

Install
npx -y skills add aizech/bernhard-zechmann-skills --skill technical-blog-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.6 KB, 291 tokens by cl100k_base, as published. Nobody here has run it

Technical Blog Writer

Write expert-level technical posts that are accessible to non-developers.

Process

  1. Research: find current, authoritative sources and real-world examples.
  2. Outline: structure the article around a clear problem-solution flow.
  3. Draft: follow this structure:
    • The problem
    • Why it matters
    • The solution
    • How it works
    • Tradeoffs and considerations
    • Key takeaways
    • FAQs (3-5 questions)
  4. Refine: check clarity, accuracy, flow, and examples.

Writing rules

  • Use plain English. Explain jargon when first introduced.
  • Include code only when it clarifies.
  • Use active voice and short paragraphs.
  • Vary sentence rhythm.
  • Include concrete examples, not generic claims.
  • Write from experience using "we" and "our" naturally.
  • Acknowledge limitations and tradeoffs.

Anti-patterns

  • Repetitive "we've" constructions
  • Perfect formulaic transitions
  • Overly technical explanations without context
  • Generic content without examples

Quality checklist

  • Problem is clearly stated
  • Solution is easy to understand
  • Technical terms are explained
  • Examples are concrete
  • Tone is authentic
  • Tradeoffs are discussed
  • FAQs add value without duplicating the main content

What ships with it: 4 files

15.6 KB alongside SKILL.md, 1 of them executable

assets/

evals/

references/

scripts/

Keep looking

Skills are one crate of 326,452. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.