hos-explain

Rewrite technical AI-generated explanations into plain language with Mermaid diagrams for non-technical readers.

32|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/openreachtech/hora-skills-ort-support --skill hos-explain-openreachtech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hos-explain
Source: https://github.com/openreachtech/hora-skills-ort-support/tree/main/kit/skills/hos-explain
Command: npx skills add https://github.com/openreachtech/hora-skills-ort-support --skill hos-explain-openreachtech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated explanations, reports, and proposals are often too long and jargon-heavy for non-engineers to understand. This Skill rebuilds those messages into plain language a junior-high-school student can read in one pass, without adding or changing any analysis. ## Core Features & Use Cases - Fixed four-part output: Every rewrite follows the same structure — a one-sentence conclusion, 1–2 diagrams, at most 3 bullet points, and a small glossary of unavoidable terms. - Diagram-driven explanation: Chooses from flowcharts, block diagrams, comparison tables, bar lengths, and timelines (Mermaid preferred) based on the shape of the content, with at most 5 elements per diagram. - Jargon substitution rules: Replaces technical terms with everyday words plus an analogy, keeping the original term in parentheses on first use. - Use Case: After an AI produces a long migration failure analysis full of terms like "unique constraint" and "two-phase migration", use this Skill to turn it into a short plain-language summary with a flowchart that a project manager or client can understand immediately. ## Quick Start Rewrite the previous AI explanation about the database migration failure into plain language with a diagram that a non-engineer can understand.

Frequently Asked Questions about hos-explain

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

FAQPage Schema
How do I make an AI explanation understandable for non-technical people?

Rebuild the message instead of shortening it: extract only facts that change the reader's decision, lead with a one-sentence conclusion, add a diagram, and limit supporting points to three bullets. Replace jargon with everyday words and keep the original term in parentheses once.

What diagram should I use to explain a technical process simply?

Choose by content shape: flowcharts for procedures, block diagrams for relationships, comparison tables for choices, bar lengths for proportions, and timelines for events over time. Mermaid is the preferred format, with at most 5 elements and one message per diagram.

Does simplifying an AI answer change its conclusions or add new analysis?

No. This Skill only rewrites an existing message and never adds new analysis, conclusions, or facts. If the original is wrong, the plain version stays wrong in the same way; fixing content is a separate task.

When should I not use plain-language rewriting for a document?

Do not use it for end-user product manuals, which belong to a dedicated user-manual skill, or when the original message does not answer the reader's question. It also never softens bad news — failed tests stay reported as failed.

How long should sentences be in a plain-language explanation?

Keep one idea per sentence, about 40 characters in Japanese or 15 words in English. Use active voice, prefer verbs over abstract nouns, and give numbers a tangible feel, such as comparing 0.3 seconds to a blink.