breakdown

Explains technology terms through six structured dimensions in Thai markdown artifacts.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/natthasath/natthasath-marketplace --skill breakdown-natthasath
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breakdown
Source: https://github.com/natthasath/natthasath-marketplace/tree/main/plugins/productive/skills/breakdown
Command: npx skills add https://github.com/natthasath/natthasath-marketplace --skill breakdown-natthasath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical terms and tools are often explained superficially, leaving users knowing what something is but not why it exists or when to choose it. This Skill produces deep, structured explanations that answer the questions people actually ask. ## Core Features & Use Cases - Six-Dimension Framework: Every explanation covers TL;DR, Problem, Solution, Use Cases, Compare, and Key Takeaway, each with a stated rationale. - Conceptual Focus: The Solution section stays at the conceptual model level, avoiding implementation details that obscure the big picture. - Real Comparisons: The Compare section targets technologies users genuinely confuse, such as Redis vs Memcached. - Use Case: Type "/breakdown Kafka" to receive a complete Thai-language markdown artifact explaining what Kafka solves, how it works conceptually, and how it differs from alternatives like RabbitMQ. ## Quick Start Invoke the skill with "/breakdown" followed by the name of any technology, tool, or concept you want explained, such as "/breakdown Docker".

Frequently Asked Questions about breakdown

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

FAQPage Schema
How do I get a deep explanation of a technology term?▼

Invoke the skill with /breakdown followed by the term, such as "/breakdown Kubernetes". It returns a markdown artifact covering the problem it solves, its conceptual model, real use cases, and comparisons with similar tools.

What structure does a technology breakdown explanation follow?▼

Every explanation uses six fixed sections: TL;DR, Problem, Solution, Use Cases, Compare, and Key Takeaway. No section is skipped, since each serves a distinct purpose in building genuine understanding.

Does the breakdown skill cover implementation details?▼

No, the Solution section is restricted to conceptual models and high-level workflows. It deliberately avoids implementation details so readers grasp the big picture before diving into specifics.

Can I use breakdown for non-technical concepts?▼

Yes, it accepts any technology, tool, or concept name as input. The same six-dimension framework applies regardless of whether the term is a software tool, an architecture pattern, or a general concept.

What language does the breakdown output use?▼

Output is written in Thai, except for technology names and technical terms that have no standard translation. The result is delivered as a markdown artifact ready to save or reuse.