Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
Agent skill
Developer Docs Technical Research
by hashgraph-online in hashgraph-online/awesome-codex-plugins
Research product and feature facts for developer documentation by mapping source-of-truth owners, validating behavior hands-on, interviewing SMEs, and turning uncertainty into doc-ready notes.
Install Developer Docs Technical Research
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-technical-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-technical-research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research .claude/skills/developer-docs-technical-research && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "developer-docs-technical-research" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research into .claude/skills/developer-docs-technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-technical-research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-technical-researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-technical-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-technical-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research .agents/skills/developer-docs-technical-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "developer-docs-technical-research" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research into .agents/skills/developer-docs-technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-technical-research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-technical-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-technical-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research .cursor/skills/developer-docs-technical-research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "developer-docs-technical-research" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research into .cursor/skills/developer-docs-technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-technical-research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hashgraph-online/awesome-codex-plugins.git --path plugins/LVTD-LLC/skills/skills/developer-docs-technical-research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-technical-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-technical-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research .gemini/skills/developer-docs-technical-research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "developer-docs-technical-research" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research into .gemini/skills/developer-docs-technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-technical-research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-technical-researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-technical-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research .github/skills/developer-docs-technical-research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "developer-docs-technical-research" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research into .github/skills/developer-docs-technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-technical-research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-technical-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-technical-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research .opencode/skills/developer-docs-technical-research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "developer-docs-technical-research" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-technical-research into .opencode/skills/developer-docs-technical-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-technical-research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
developer-docs-technical-research- GitHub stars
- 1.2k
- Token cost
- ~841 tokens
- SKILL.md length
- 325 words
- Files
- 5 (incl. references)
- Skills in repo
- 736
- Repo updated
- First seen
- Licence
- MIT
At a glance
Research product and feature facts for developer documentation by mapping source-of-truth owners, validating behavior hands-on, interviewing SMEs, and turning uncertainty into doc-ready notes.
- Works in 6 steps: Load guidelines.md to choose the… → State the documentation question,… → Build a source map from code, product… → …
- Feature specs are incomplete
- SKILL.md covers Quick Start, Default Output, Contents and Core Posture
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Developer Docs Technical Research is an agent skill from hashgraph-online/awesome-codex-plugins. Research product and feature facts for developer documentation by mapping source-of-truth owners, validating behavior hands-on, interviewing SMEs, and turning uncertainty into doc-ready notes. Use when feature specs are incomplete, implementation details need user-facing meaning, SMEs disagree, or docs require evidence before planning, drafting, release notes, API docs, tutorials, scenarios, or troubleshooting content.
Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `guidelines.md`, `references/core/knowledge.md` and `workflows/interview-doc-sources.md`). Compatibility notes: Codex, Claude Code, and other Agent Skills-compatible clients.
It sits in Development, covering Technical documentation, PRD writing and Changelog and release notes. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is MIT.
When your agent uses it
- Feature specs are incomplete
- Implementation details need user-facing meaning
- Docs require evidence before planning
- Troubleshooting content
Example prompts
- “/developer-docs-technical-research”
Requirements
- Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients.
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Load guidelines.md to choose the smallest useful reference set.
- State the documentation question, audience, feature, release context, and risk.
- Build a source map from code, product surfaces, specs, tickets, SMEs, QA, support, and existing docs.
- Use workflows/research-feature-docs.md when feature behavior or user consequences are unclear.
- Use workflows/interview-doc-sources.md when the main work is extracting facts from SMEs.
- Return verified facts, assumptions, contradictions, source owners, and open questions.
What it can do on your machine
Read from SKILL.md and the folder at commit 16b4156. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
link.springer.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Codex, Claude Code, and other Agent Skills-compatible clients.
From compatibility in the SKILL.md frontmatter.
Context cost
Developer Docs Technical Research loads about 841 tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 114 tokens; SKILL.md has 325 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hashgraph-online/awesome-codex-plugins at commit 16b4156, republished under its MIT licence (© hashgraph-online). 325 words, ~841 tokens.
Download SKILL.mdSave it as
.claude/skills/developer-docs-technical-research/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- developer-docs-technical-research
- description
- Research product and feature facts for developer documentation by mapping source-of-truth owners, validating behavior hands-on, interviewing SMEs, and turning uncertainty into doc-ready notes. Use when feature specs are incomplete, implementation details need user-facing meaning, SMEs disagree, or docs require evidence before planning, drafting, release notes, API docs, tutorials, scenarios, or troubleshooting content.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
- license
- MIT
- metadata.version
- 0.1.0
- metadata.displayName
- Developer Docs Technical Research
- metadata.category
- Writing
- metadata.tags
- developer-docs,technical-writing,documentation,research,sme-interviews
Developer Docs Technical Research
Use this skill to investigate product behavior before planning or writing developer documentation. It turns specs, code, prototypes, tickets, SMEs, and hands-on tests into traceable research notes.
This skill is derived from paraphrased guidance in Christopher Gales and the Splunk Documentation Team's The Product Is Docs: Writing Technical Documentation in a Product Development Group, especially Chapter 13, "Research for Technical Writers," Chapter 16, "Technical Verification," Chapter 19, "Working with Engineers," and Chapter 22, "Working with Product Management." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6
Quick Start
- Load
guidelines.mdto choose the smallest useful reference set. - State the documentation question, audience, feature, release context, and risk.
- Build a source map from code, product surfaces, specs, tickets, SMEs, QA, support, and existing docs.
- Use
workflows/research-feature-docs.mdwhen feature behavior or user consequences are unclear. - Use
workflows/interview-doc-sources.mdwhen the main work is extracting facts from SMEs. - Return verified facts, assumptions, contradictions, source owners, and open questions.
Default Output
When completing a documentation research pass, return:
- Research brief - doc question, audience, scope, and decision needed.
- Verified facts - behavior, limits, defaults, prerequisites, permissions, errors, and examples with source.
- User consequences - what readers can do, decide, risk, or misunderstand.
- Source map - authoritative owner or artifact for each important fact.
- Contradictions and gaps - unresolved disagreements, missing access, or untested behavior.
- Recommended docs action - plan, draft, defer, file product issue, or request review.
Contents
| Need | Start Here |
|---|---|
| Understand technical research concepts | references/core/knowledge.md |
| Build a feature research plan | workflows/research-feature-docs.md |
| Interview engineers, PMs, QA, support, or field teams | workflows/interview-doc-sources.md |
| Route by task or symptom | guidelines.md |
Core Posture
- Research user-facing consequences, not only implementation.
- Verify directly when the product, API, CLI, UI, or environment is available.
- Treat named owners and durable artifacts as the source of truth.
- Keep uncertainty visible until it is resolved.
- File product or UX defects when documentation would be forced to explain avoidable confusion.
© hashgraph-online, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in plugins/LVTD-LLC/skills/skills/developer-docs-technical-research of hashgraph-online/awesome-codex-plugins.
- SKILL.md
- guidelines.md
- references/core/knowledge.md
- workflows/interview-doc-sources.md
- workflows/research-feature-docs.md
Open the folder on GitHubat commit 16b4156
Compare with similar skills
Developer Docs Technical Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Developer Docs Technical Research this skillhashgraph-online/awesome-codex-plugins | 1.2k | — | ~841 | Automated safety check: Pass | MIT | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Ccb GitHubSeemSeam/claude_codex_bridge | 3.5k | — | ~4.9k | Automated safety check: Pass | Custom licence | |
| Golang Documentationunxed/f4 | 240 | 3 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Simple Englishropensci/ckanr | 104 | 3 repos | ~2k | Automated safety check: Pass | MIT | |
| Opik Documentation Patternscomet-ml/opik | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Ccb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
Golang Documentation
unxed/f4
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt.
Simple English
ropensci/ckanr
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before…
Opik Documentation Patterns
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
Release
jrswab/axe
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
More from hashgraph-online/awesome-codex-plugins
All 736 skills in this repoAnime Reaction Gif
hashgraph-online/awesome-codex-plugins
Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.
Calibredb
hashgraph-online/awesome-codex-plugins
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).
Rust API Test Harness
hashgraph-online/awesome-codex-plugins
A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…
Art
hashgraph-online/awesome-codex-plugins
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…
Calle
hashgraph-online/awesome-codex-plugins
Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.
Game Balance Economy
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
Related
Categories
Questions about Developer Docs Technical Research
What does Developer Docs Technical Research do?
Research product and feature facts for developer documentation by mapping source-of-truth owners, validating behavior hands-on, interviewing SMEs, and turning uncertainty into doc-ready notes. Developer Docs Technical Research is an agent skill from hashgraph-online/awesome-codex-plugins. Research product and feature facts for developer documentation by mapping source-of-truth owners, validating behavior hands-on, interviewing SMEs, and turning uncertainty into doc-ready notes.
When should I use Developer Docs Technical Research?
Developer Docs Technical Research fits situations like: feature specs are incomplete; implementation details need user-facing meaning; docs require evidence before planning; troubleshooting content.
How do I install Developer Docs Technical Research in Claude Code?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-technical-research -a claude-code`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/developer-docs-technical-research in hashgraph-online/awesome-codex-plugins) into .claude/skills/developer-docs-technical-research in your project. Claude Code loads it when a task matches its description.
How do I install Developer Docs Technical Research in Codex?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-technical-research -a codex`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/developer-docs-technical-research in hashgraph-online/awesome-codex-plugins) into .agents/skills/developer-docs-technical-research in your project. Codex loads it when a task matches its description.
Can I use Developer Docs Technical Research in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-technical-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developer-docs-technical-research, .gemini/skills/developer-docs-technical-research, .github/skills/developer-docs-technical-research and .opencode/skills/developer-docs-technical-research in your project.
What does Developer Docs Technical Research need to run?
SKILL.md names no scripts, command-line tools or credentials: Developer Docs Technical Research is instructions for the agent only. Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients..
Does Developer Docs Technical Research access the network?
SKILL.md names 1 domain. As links in the text: link.springer.com. This is read from the text; nothing was executed.
Is Developer Docs Technical Research safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Developer Docs Technical Research use?
Developer Docs Technical Research is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Developer Docs Technical Research use?
About 841 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Developer Docs Technical Research?
Skills that share tags, products or a category with Developer Docs Technical Research: Simple English (moeru-ai/airi, 50k stars), Ccb GitHub (SeemSeam/claude_codex_bridge, 3.5k stars), Golang Documentation (unxed/f4, 240 stars) and Simple English (ropensci/ckanr, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Developer Docs Technical Research?
hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,232 GitHub stars. The repository holds 736 skills in this directory. The repository was last updated on October 6, 2026.
Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.