Dogfood Exploratory QA
vercel-labs/agent-browser
Explores a web app with the agent-browser CLI to find bugs and UX problems, then writes a report with screenshots, repro videos and step-by-step reproduction for each issue.
Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug…
Install Docs Feedback Triage
$ npx skills add hashgraph-online/awesome-codex-plugins --skill docs-feedback-triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins docs-feedback-triage --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/docs-feedback-triage .claude/skills/docs-feedback-triage && 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 "docs-feedback-triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/docs-feedback-triage into .claude/skills/docs-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-feedback-triage", 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/docs-feedback-triageType 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 docs-feedback-triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins docs-feedback-triage --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/docs-feedback-triage .agents/skills/docs-feedback-triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docs-feedback-triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/docs-feedback-triage into .agents/skills/docs-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-feedback-triage", 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 docs-feedback-triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins docs-feedback-triage --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/docs-feedback-triage .cursor/skills/docs-feedback-triage && 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 "docs-feedback-triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/docs-feedback-triage into .cursor/skills/docs-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-feedback-triage", 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/docs-feedback-triage--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 docs-feedback-triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins docs-feedback-triage --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/docs-feedback-triage .gemini/skills/docs-feedback-triage && 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 "docs-feedback-triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/docs-feedback-triage into .gemini/skills/docs-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-feedback-triage", 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 docs-feedback-triageInstalls 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 docs-feedback-triage -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/docs-feedback-triage .github/skills/docs-feedback-triage && 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 "docs-feedback-triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/docs-feedback-triage into .github/skills/docs-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-feedback-triage", 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 docs-feedback-triage -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 docs-feedback-triage --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/docs-feedback-triage .opencode/skills/docs-feedback-triage && 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 "docs-feedback-triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/docs-feedback-triage into .opencode/skills/docs-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-feedback-triage", 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
docs-feedback-triage- GitHub stars
- 1.2k
- Token cost
- ~772 tokens
- SKILL.md length
- 295 words
- Files
- 4 (incl. references)
- Skills in repo
- 686
- Repo updated
- First seen
- Licence
- MIT
At a glance
Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug…
- Works in 5 steps: Load guidelines.md to choose the… → Identify feedback source, affected doc,… → Test validity, actionability, and… → …
- Setting up docs feedback channels
- 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
Docs Feedback Triage is an agent skill from hashgraph-online/awesome-codex-plugins. Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug reports, and user follow-up. Use when setting up docs feedback channels, triaging docs issues, responding to frustrated users, prioritizing doc fixes, or converting feedback into actionable documentation work.
Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `guidelines.md`, `references/core/knowledge.md` and `workflows/triage-doc-feedback.md`). Compatibility notes: Codex, Claude Code, and other Agent Skills-compatible clients.
It sits in Testing & QA, covering QA and bug reports. 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
- Setting up docs feedback channels
- Triaging docs issues
- Responding to frustrated users
- Prioritizing doc fixes
Example prompts
- “/docs-feedback-triage”
Requirements
- Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients.
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Load guidelines.md to choose the smallest useful reference set.
- Identify feedback source, affected doc, user impact, response need, and whether the issue is docs-owned.
- Test validity, actionability, and importance before recommending work.
- Use workflows/triage-doc-feedback.md for a full triage pass.
- Close the loop with users or source teams when the feedback changes product, support, or docs work.
What it can do on your machine
Read from SKILL.md and the folder at commit 78497e5. 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
Docs Feedback Triage loads about 772 tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 295 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 78497e5, republished under its MIT licence (© hashgraph-online). 295 words, ~772 tokens.
Download SKILL.mdSave it as
.claude/skills/docs-feedback-triage/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- docs-feedback-triage
- description
- Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug reports, and user follow-up. Use when setting up docs feedback channels, triaging docs issues, responding to frustrated users, prioritizing doc fixes, or converting feedback into actionable documentation work.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
- license
- MIT
- metadata.version
- 0.1.0
- metadata.displayName
- Docs Feedback Triage
- metadata.category
- Writing
- metadata.tags
- developer-docs,technical-writing,documentation,feedback,triage
Docs Feedback Triage
Use this skill to turn developer documentation feedback into valid, actionable, prioritized work. It helps agents avoid treating every comment as equal while preserving user evidence.
This skill is derived from Docs for Developers: An Engineer's Field Guide to Technical Writing, especially Chapter 8, "Gathering and integrating feedback." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's The Product Is Docs: Writing Technical Documentation in a Product Development Group, especially Chapter 5, "Customer Feedback and Community," Chapter 18, "Working with Customer Support," and Chapter 20, "Working with the Field." 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. - Identify feedback source, affected doc, user impact, response need, and whether the issue is docs-owned.
- Test validity, actionability, and importance before recommending work.
- Use
workflows/triage-doc-feedback.mdfor a full triage pass. - Close the loop with users or source teams when the feedback changes product, support, or docs work.
Default Output
When triaging feedback, return:
- Feedback summary - source, affected doc, user type, and reported problem.
- Classification - valid/invalid/needs research, docs/product/support issue, duplicate status.
- Actionability - reproducible, scoped, and fixable information.
- Priority - severity and rationale.
- Recommended action - doc fix, routing, follow-up, or no action.
- Follow-up - user response, owner, and evidence to collect.
Contents
| Need | Start Here |
|---|---|
| Understand feedback channels | references/core/knowledge.md |
| Apply triage rules | references/core/knowledge.md |
| See triage examples | references/core/knowledge.md |
| Triage feedback | workflows/triage-doc-feedback.md |
| Route by task | guidelines.md |
Core Posture
- Feedback is evidence, not a direct order.
- Distinguish docs problems from product, support, pricing, or policy problems.
- Prioritize by user impact and fixability.
- Treat public/community feedback as both support signal and trust-building opportunity.
- Follow up when users took time to report a real issue.
© 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 3 other files (references) in plugins/LVTD-LLC/skills/skills/docs-feedback-triage of hashgraph-online/awesome-codex-plugins.
- SKILL.md
- guidelines.md
- references/core/knowledge.md
- workflows/triage-doc-feedback.md
Open the folder on GitHubat commit 78497e5
Compare with similar skills
Docs Feedback Triage 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 |
|---|---|---|---|---|---|---|
| Docs Feedback Triage this skillhashgraph-online/awesome-codex-plugins | 1.2k | — | ~772 | Automated safety check: Pass | MIT | |
| Dogfood Exploratory QAvercel-labs/agent-browser | 44k | 8 repos | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Codex Plugin QAcode-yeongyu/oh-my-openagent | 70k | 1 repos | ~1.9k | Automated safety check: Pass | Custom licence | |
| DeerFlow Smoke Testbytedance/deer-flow | 83k | — | ~2.5k | Automated safety check: Notes | MIT | |
| CodexBar Live QAsteipete/CodexBar | 22k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Diagnose Playwright Failure as Product Bugappsmithorg/appsmith | 41k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Codex Plugin QA
code-yeongyu/oh-my-openagent
Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.
DeerFlow Smoke Test
bytedance/deer-flow
Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.
CodexBar Live QA
steipete/CodexBar
Runs live QA for the CodexBar app: provider usage matrix checks through its packaged CLI, config validation and menu checks, with 1Password-backed credentials handled safely.
Diagnose Playwright Failure as Product Bug
appsmithorg/appsmith
Investigates a stubbornly failing Playwright test as a possible product bug, using error output, screenshots, traces and server code, and writes a structured bug report.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
More from hashgraph-online/awesome-codex-plugins
All 686 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…
Game Balance Economy
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
Manuscript Engagement Analytics
hashgraph-online/awesome-codex-plugins
Analyze nonfiction manuscripts for reader engagement signals, including heading-level word counts, slow starts, long slogs, weak takeaway titles, value pacing, beta-reader comment dropoff, and…
Related
Categories
Questions about Docs Feedback Triage
What does Docs Feedback Triage do?
Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug…. Docs Feedback Triage is an agent skill from hashgraph-online/awesome-codex-plugins. Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug reports, and user follow-up.
When should I use Docs Feedback Triage?
Docs Feedback Triage fits situations like: setting up docs feedback channels; triaging docs issues; responding to frustrated users; prioritizing doc fixes.
How do I install Docs Feedback Triage in Claude Code?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill docs-feedback-triage -a claude-code`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/docs-feedback-triage in hashgraph-online/awesome-codex-plugins) into .claude/skills/docs-feedback-triage in your project. Claude Code loads it when a task matches its description.
How do I install Docs Feedback Triage in Codex?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill docs-feedback-triage -a codex`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/docs-feedback-triage in hashgraph-online/awesome-codex-plugins) into .agents/skills/docs-feedback-triage in your project. Codex loads it when a task matches its description.
Can I use Docs Feedback Triage 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 docs-feedback-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-feedback-triage, .gemini/skills/docs-feedback-triage, .github/skills/docs-feedback-triage and .opencode/skills/docs-feedback-triage in your project.
What does Docs Feedback Triage need to run?
SKILL.md names no scripts, command-line tools or credentials: Docs Feedback Triage is instructions for the agent only. Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients..
Does Docs Feedback Triage 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 Docs Feedback Triage 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 Docs Feedback Triage use?
Docs Feedback Triage 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 Docs Feedback Triage use?
About 772 tokens (SKILL.md is roughly 3.1k 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 2.1k tokens, read only when the agent opens those files.
What are the alternatives to Docs Feedback Triage?
Skills that share tags, products or a category with Docs Feedback Triage: Dogfood Exploratory QA (vercel-labs/agent-browser, 44k stars), Codex Plugin QA (code-yeongyu/oh-my-openagent, 70k stars), DeerFlow Smoke Test (bytedance/deer-flow, 83k stars) and CodexBar Live QA (steipete/CodexBar, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docs Feedback Triage?
hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,242 GitHub stars. The repository holds 686 skills in this directory. The repository was last updated on October 8, 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.