skills.rest
kwanpham2195
kwanpham2195COMMUNITY
Explore all skills by this author →
GitHub

write-tbp

Write technical blog posts about project features and implementation details.

2|Updated Sep 14, 2026
Search Tags:#technical writing#drafting#writing workflow#blog post#codebase research#developer content
One-click install
npx skills add https://github.com/kwanpham2195/agent-stuff --skill write-tbp-kwanpham2195
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-tbp
Source: https://github.com/kwanpham2195/agent-stuff/tree/main/skills/write-tbp
Command: npx skills add https://github.com/kwanpham2195/agent-stuff --skill write-tbp-kwanpham2195

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning deep implementation knowledge buried in a codebase into a readable technical blog post is hard: you must research the code, find an interesting angle, and structure the narrative. This Skill provides a repeatable workflow that takes a topic from research to a polished draft. ## Core Features & Use Cases - Structured research: Uses an Explore subagent to gather implementation files, type definitions, tests, and design rationale into a research document. - Angle identification: Guides you to find the problem, the surprising insight, and the key idea before writing. - Drafting and self-evaluation: Produces an 800-1500 word draft following a problem-insight-implementation structure, then checks it against a quality checklist. - Use Case: You just shipped a cache-invalidation feature. Point the Skill at the topic, and it researches the codebase, writes a draft explaining the problem and solution, and saves it to assets/cache-invalidation/draft.md for your review. ## Quick Start Write a technical blog post about how the query-planning feature works in this project.

Frequently Asked Questions about write-tbp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a technical blog post about my code?▼

Start by researching the codebase to gather implementation details, then identify the problem being solved and the key insight. This Skill automates that flow: it runs an Explore subagent for research, helps find the angle, and produces a structured draft.

How to structure a technical blog post about implementation details?▼

Frame the problem first, then show the key insight, walk through the implementation with code examples, and wrap up with tradeoffs and links to files. The Skill targets 800-1500 words following this structure.

Where does the blog post draft get saved?▼

Drafts are saved in the target project workspace under assets/<topic>/draft.md, with research notes in assets/<topic>/research.md. Files are not written to the installed skill directory, and you move the draft once satisfied.

What if my topic has no interesting angle for a blog post?▼

The Skill explicitly checks for an angle before writing: what problem it solves, what is surprising, and what the key insight is. If none can be found, the topic may not be suitable for a technical blog post.

Does the Skill publish the blog post automatically?▼

No. The Skill only produces a draft in the workspace and presents it for your review. You decide when it is ready and move it to the appropriate publishing location yourself.

Related Skills

Explore More Content & Communication Skills→
stabilefrisurstabilefrisur

receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

Community
Advanced
brolagbrolag
11

workflow-content

Structure and generate platform-ready drafts for social posts, newsletters, and blogs.

Community
Intermediate
ollieb89ollieb89

every-style-editor

Edit and standardize copy against the Every Style Guide rules.

Community
Advanced
exiaoexiao
37

demo-video

Record browser interactions and encode frames into MP4, GIF, or WebM videos.

Community
Intermediate