blog-writer

Generate reader-friendly technical blog drafts in Markdown from project requirements.

5|1|Updated May 9, 2026

Search Tags:#documentation #markdown #blog #writer #technical-blog #toLink-Rag

Ready to run

npx skills add https://github.com/ql-link/LinkRag --skill blog-writer-ql-link

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: blog-writer
Source: https://github.com/ql-link/LinkRag/tree/main/.ai/skills/blog-writer
Command: npx skills add https://github.com/ql-link/LinkRag --skill blog-writer-ql-link

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams translate a user's requirement into a complete, reader-friendly technical blog that stays grounded in the project's real code and documentation, ensuring the article is informative and actionable.

Core Features & Use Cases

Generates a narrative that covers background, requirements, implementation context, design trade-offs, risks, and validation steps, all grounded in the actual LinkRag project.
Produces a Markdown draft placed under .specs/blog/ with a clear structure that a reader can follow from problem to solution.
Adapts to different audiences, balancing accessibility for non-experts with technical detail for engineers.

Quick Start

Provide a blog topic and any related project references to generate a Markdown article.

Frequently Asked Questions about blog-writer

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

FAQPage Schema

How do I write a technical blog from project requirements and code?▼

To write a technical blog from project requirements, provide a blog topic and related project references. The skill generates a Markdown draft covering background, implementation details, and validation grounded in real code.

What is the best way to generate Markdown documentation for a technical blog?▼

Generating Markdown documentation for a technical blog is done by translating user requirements into a structured narrative. This includes design trade-offs and implementation context, outputting the file directly to the .specs/blog/ directory.

Can I create a technical blog that explains design trade-offs and validation steps?▼

Yes, you can create a technical blog that explains design trade-offs and validation steps. The generated narrative balances accessibility for non-experts with technical detail for engineers, grounded in the LinkRag project.

How do I structure a reader-friendly technical blog using Markdown?▼

To structure a reader-friendly technical blog using Markdown, the skill applies clear sections that guide the reader from the problem to the solution. It ensures alignment with project realities by using actual code and documentation.

Does this blog writer work with LinkRag project code and documentation?▼

Yes, this blog writer works with LinkRag project code and documentation. It ensures the generated technical blogs stay grounded in the project's actual codebase, maintaining factual accuracy and actionable context.

What should I provide to generate a technical blog draft?▼

To generate a technical blog draft, you should provide a blog topic and any related project references. The skill then uses this input to create a reader-friendly Markdown article placed under .specs/blog/.