hos-humanize-docs

Repairs maintained documents through iterative cold-read loops and eight testable clarity criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Authors cannot see where their own documents stall a first-time reader, because rereading supplies missing context from memory. This Skill replaces author review with a cold read by a fresh agent, classifies each stall against eight mechanical criteria, and repairs the document in a bounded loop until findings fall below a threshold. ## Core Features & Use Cases - Cold-read repair loop: A new agent each round reports where it stalled, findings are classified by severity (critical, major, minor, out-of-scope), and only in-scope defects are fixed, looping until the threshold is met or the round cap is reached. - Multi-language correspondence: Language versions of one document are repaired in parallel per language, then compared for claims, heading structure, figures, and term mapping, with structural changes applied to the whole family at once. - Voice preservation: A style probe extracts the document's register, formatting habits, and vocabulary before editing, and a seam test verifies new passages are indistinguishable from existing ones. - Use Case: A repository's Japanese quick-start guide reads like a translation and has drifted from its English counterpart. Run the skill on the file with lang:all to repair both versions, align their claims and structure, and verify each with a final cold read. ## Quick Start Ask the agent to run /hos-humanize-docs on a document path such as docs/quick-start.ja.md, optionally adding lang:all, rounds:5, strict, or dry to control the repair.

Frequently Asked Questions about hos-humanize-docs

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

FAQPage Schema
How do I fix a document that is hard to follow?

Invoke /hos-humanize-docs with the document path as the target. A fresh agent cold-reads the file, reports where it stalled, and each stall is classified against eight criteria before fixes are applied, looping until findings fall below a threshold.

How do I keep translated documentation versions consistent?

Run the skill with lang:all so every language version is written. After per-language repair, a correspondence stage compares claims, heading structure, figures, and term mapping across versions and applies structural changes to the whole family at once.

Can I preview document issues without modifying files?

Yes, pass the dry flag to run one cold-read round with classification only, writing nothing. The report lists each stall with its severity class and the criterion it violates.

What documents should not be repaired with this skill?

Do not use it for rewriting content for a non-technical reader, creating documents that do not exist yet, or filling in missing facts owned by other documents. It also excludes SKILL.md files, which are written for agents rather than human readers.

Why does the repair loop stop before all issues are fixed?

The loop stops when the round cap is reached or when a round fails to reduce the in-scope finding count, since that indicates fixes are introducing new defects. Reaching the cap is reported explicitly with every finding still standing.