Open Reach Tech
Official@openreachtech
Open Reach Tech maintains conventions for GitHub issue/PR/release drafting, npm publish auditing, documentation repair, and E2E-driven user manual generation.
Agent Skills by Open Reach Tech
Showing 10 vetted skills indexed across 1 GitHub repositories.
openreachtechhos-humanize-docs
Repairs maintained documents through iterative cold-read loops and eight testable clarity criteria.
openreachtechhos-skillify
Mine conversation transcripts to distill durable conventions into new or updated skills.
openreachtechhos-documentation-audit
Detect contradictions between maintained documents and installed convention skills with quoted evidence.
openreachtechhos-gh-release-note
Write and publish GitHub release notes with structured sections and dependency tables.
openreachtechhos-gh-pull-request
Write and open GitHub pull requests with structured Why, How, and Note sections using gh CLI.
openreachtechhos-gh-issue
Write and file GitHub issues, sub-issues, and hub issues using the gh CLI.
openreachtechhos-user-manual
Generate end-user HTML operation manuals by driving a live E2E environment and capturing screenshots.
openreachtechhos-explain
Rewrite technical AI-generated explanations into plain language with Mermaid diagrams for non-technical readers.
openreachtechhos-npm-publish-audit
Audits npm package tarballs before publishing by inspecting packed file inventories and entry points.
openreachtechaudit
Validates skill folder names, SKILL.md frontmatter, and catalog consistency under kit/skills/.
Frequently Asked Questions About Open Reach Tech
FAQPage SchemaWhat tasks can I accomplish with Open Reach Tech's skills?▼
You can draft and file GitHub issues, pull requests, and release notes; audit npm package tarballs before publishing; repair documents that first-time readers stall on; audit documents against conventions; rewrite technical explanations into plain language with diagrams; and generate screenshot-based HTML user manuals from a live E2E environment.
Who are these skills designed for?▼
They target maintainers of this organization's repositories who write issues, pull requests, and release notes, plus engineers preparing npm packages for publication and teams maintaining documentation. The explain skill serves anyone sharing AI-generated conclusions with non-technical readers at a junior-high-school comprehension level.
How do the GitHub drafting skills work in practice?▼
The pull request skill composes a title with the linked issue's type emoji and Why/How/Note body sections, shows the full text for approval, then opens it via gh pr create --draft. If gh is missing or logged out, it hands over the text alone. Issues and release notes follow the same approve-then-send pattern.
What prerequisites do the user manual and build skills require?▼
The user-manual skill requires an already-built local E2E environment with a test user login; building that environment is a separate convention's job. The build skill expects skill folders named hos-* placed one level deep under kit/skills/, which it validates and copies unchanged into dist/skills/.
How does the documentation repair process work?▼
The humanize-docs skill runs a cold read by an agent with no prior knowledge, records where it stalled, classifies each stall against written criteria, and fixes the document, looping until findings fall inside a threshold. Structure, voice, and the intended reader are preserved throughout.