Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
langgenius avatar

Dify Docs Reader Test

  • 3 installs
  • 174 repo stars
  • Updated August 4, 2026
  • langgenius/dify-docs

Helps with testing & qa tasks.

About

dify-docs-reader-test is a Claude Code skill for testing & qa. It helps solo builders move faster with AI-assisted development.

  • dify-docs-reader-test
  • Testing & QA
  • AI-coding skill

Dify Docs Reader Test by the numbers

  • 3 all-time installs (skills.sh)
  • Ranked #1,648 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/langgenius/dify-docs --skill dify-docs-reader-test

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs3
repo stars174
Last updatedAugust 4, 2026
Repositorylanggenius/dify-docs

What it does

Helps with testing & qa tasks.

Files

SKILL.mdMarkdownGitHub ↗

Reader Experience Test

Purpose

Verify documentation from the reader's perspective. A clean-context agent reads the finished document as the target persona, with no access to source material, codebase, or prior conversation.

How to Invoke

Dispatch a subagent with exactly two inputs: 1. The document content (the page just written or updated) 2. The reader persona description (from the writing skill being used)

Do NOT provide: source material, codebase access, prior conversation, or any context the reader wouldn't have.

What the Test Agent Checks

  • Can I accomplish the task described without prior knowledge?
  • Are there steps that assume context not provided on this page?
  • Are there terms used without explanation (and not in the glossary)?
  • Is the information I need actually here, or do I have to guess?
  • Do the code examples make sense on their own?
  • After reading, do I know what to do next?

What the Test Agent Does NOT Do

  • Style or formatting review (that is the writer's job)
  • Fact-check against the codebase (that is the writer's job)
  • Rewrite anything—only report what was confusing

Output Format

Structured feedback:

  • Got stuck at: [section/step where understanding broke down]
  • Didn't understand: [terms, concepts, or references that were unclear]
  • Missing context: [assumptions the document makes that weren't established]
  • Verdict: Clear / Minor gaps / Needs revision

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.