write-an-article

Convert resolved support conversations into help-center drafts and status communications.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/akiotanaka847/qaio-desktop --skill write-an-article
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-an-article
Source: https://github.com/akiotanaka847/qaio-desktop/tree/main/store/agents/support/.agents/skills/write-an-article
Command: npx skills add https://github.com/akiotanaka847/qaio-desktop --skill write-an-article

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents support teams from repeatedly rewriting answers and leaving help-center content outdated by converting real resolved conversations and known issues into consistent, grounded drafts.

Core Features & Use Cases

  • Ticket-to-article drafting: Convert a resolved ticket thread into a help-center article that captures the reusable solution and matches your support voice.
  • Known-issue status pages: Draft customer-facing incident/bug documentation with clear impact, workaround, and current status.
  • Shipped-notes personalization: Generate “you asked, we shipped” messages for each customer who requested a feature, referencing the exact request.
  • Stale-article refresh workflow: Detect references to what changed, propose updates, and flag items for review instead of overwriting blindly.

Quick Start

Tell the skill which type you want (from-ticket, known-issue, broadcast-shipped, or refresh-stale) and provide the required inputs so it can read your support context, pull the needed sources, and produce the draft outputs in the appropriate paths.

Frequently Asked Questions about write-an-article

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

FAQPage Schema
How do I turn resolved support tickets into help center articles?

To turn resolved tickets into help center articles, the Skill reads resolved ticket threads and converts reusable solutions into publish-ready drafts. It captures the specific resolution and matches your support voice for direct publishing.

What is the best way to document known issues for a customer-facing status page?

The best way to document known issues is generating customer-facing incident drafts with clear impact statements, workarounds, and current status. The Skill branches into a known-issue mode to produce these specific documentation files for your status updates.

How do I generate personalized shipped feature notifications for customers who requested them?

You generate personalized shipped notifications by using the broadcast-shipped mode, which creates targeted messages for each customer who requested a feature. These drafts reference the exact original customer request to close the feedback loop.

Can I detect and refresh stale help center content automatically?

You can refresh stale help center content by running the refresh-stale mode, which detects references to what changed and proposes updates. It flags items for manual review instead of blindly overwriting existing documentation.

Do I need specific integrations connected to draft articles from support tickets?

Yes, you need connected integrations and required metadata validated before drafting articles. The Skill checks for these connections to pull necessary support context and sources, ensuring generated drafts are grounded in real ticket data.