technical-writing

Analyze Korean technical documents for structural and linguistic issues.

25|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/toongri/oh-my-toong-playground --skill technical-writing-toongri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-writing
Source: https://github.com/toongri/oh-my-toong-playground/tree/main/skills/technical-writing
Command: npx skills add https://github.com/toongri/oh-my-toong-playground --skill technical-writing-toongri

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides disciplined Korean technical writing reviews so structural inconsistencies and sentence-level clarity issues are caught before publication.

Core Features & Use Cases

  • Sequential type classification: Validates the document type using principle-based prompts, only diving deeper after confirming the declared intent.
  • Architecture inspection: Checks headings, overview, and layout with references to architecture guidelines, ensuring flow and predictability.
  • Sentence refinement: Applies sentence-level principles to eliminate vague wording, improve naturalness, and cite rules with before/after examples.

Quick Start

Ask for a three-phase Korean technical writing review covering type classification, architecture, and sentence quality with per-area approval after each draft.

Frequently Asked Questions about technical-writing

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

FAQPage Schema
How do I review Korean technical documents for structural and linguistic issues?

To review Korean technical documents, you apply a sequential inspection process covering type classification, information architecture, and sentence quality to identify structural inconsistencies and linguistic clarity issues before publication.

What is the best way to check information architecture in Korean documentation?

The best way to check information architecture in Korean documentation is to inspect headings, overviews, and layout against principle-based guidelines, ensuring document flow and predictability before moving to sentence-level checks.

How do I refine Korean technical writing to eliminate vague wording?

To refine Korean technical writing and eliminate vague wording, apply sentence-level principles to improve naturalness and cite rules with specific before and after examples for each recommendation.

Can I validate document type intent before diving into sentence quality checks?

Yes, you can validate document type intent by applying principle-based prompts for type classification first, only diving deeper into architecture and sentence inspections after confirming the declared intent.

Do I need to approve recommendations after each technical writing review phase?

Yes, you need to provide per-area approval after each draft during the sequential technical writing review, ensuring you validate type classification, architecture, and sentence quality recommendations step by step.