knowledge-article

Writes technical knowledge articles as tagged Markdown or HTML files using a fixed problem-cause-solution format.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/DIO0550/d-market-knowledge --skill knowledge-article-dio0550
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-article
Source: https://github.com/DIO0550/d-market-knowledge/tree/main/plugins/knowledge-vault/skills/knowledge-article
Command: npx skills add https://github.com/DIO0550/d-market-knowledge --skill knowledge-article-dio0550

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Technical learnings and troubleshooting insights are often lost because they are never written down in a consistent, searchable form. This Skill turns a single problem or insight into a structured knowledge article with frontmatter (title/tags) and a fixed "problem → cause → solution" structure, so it can be found later via tag-based cross-searching. ## Core Features & Use Cases - Fixed article format: Every article follows the same structure (TL;DR → problem → cause → solution → summary → references) with mandatory title and tags for later retrieval. - Markdown by default, HTML on request: Outputs a .md file by default, and a styled standalone .html article only when the user explicitly asks for HTML. - One topic per article: Enforces small, focused articles with minimal reproduction code, environment details, and Japanese-language writing. - Use Case: After debugging a React rendering issue, ask the Skill to write it up; it produces a tagged Markdown article capturing the symptoms, root cause, and the working fix for future reuse. ## Quick Start Write a knowledge article in Markdown about the bug we just fixed, with tags for the framework and topic.

Frequently Asked Questions about knowledge-article

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

FAQPage Schema
How do I write a technical knowledge article with a consistent format?

Provide one problem or insight and the Skill writes a single article using a fixed structure: TL;DR, problem, cause, solution, summary, and references. It adds frontmatter with a title and tags so the article stays searchable later.

How do I document a bug fix as a reusable knowledge note?

Describe what happened, the environment, and the fix; the Skill formats it into a tagged article with minimal reproduction code. Keeping one topic per article and including environment versions makes the note reusable for future incidents.

Can I output a knowledge article as HTML instead of Markdown?

Yes, but only when you explicitly ask for HTML. Markdown is the default output; the HTML version uses a styled standalone template with the same structure and keeps tags in a meta keywords element.

Why are tags required in every knowledge article?

Tags are the only handle for cross-searching articles later, so the Skill never omits them. It encourages adding multiple tags covering technology names and topics to maximize discoverability.

What are the limitations of this article format?

It is designed for one topic per article, so broad or multi-part writeups must be split into separate files. It also writes in Japanese and favors rough-but-recorded notes over polished long-form documentation.