Agent skill · Testing & QA

ln-511-test-researcher

Researches real-world problems, competitor solutions, and customer complaints before test planning. Posts findings as Linear comment for ln-512 and ln-513.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill ln-511-test-researcher-levnikolaevich-claude-code-skills --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/analysis/ln-511-test-researcher-levnikolaevich-claude-code-skills/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Test Researcher Researches real-world problems and edge cases before test planning to ensure tests cover actual user pain points, not just AC. ## Purpose & Scope - Research common problems for the feature domain using Web Search, MCP Ref, Context7. - Analyze how competitors solve the same problem. - Find customer complaints and pain points from forums, StackOverflow, Reddit. - Post structured findings as Linear comment for downstream skills (ln-512, ln-513). - No test creation or status changes. ## When to Use This skill should be used when: - **Invoked by ln-510-test-planner** at start of test planning pipeline - Story has non-trivial functionality (external APIs, file formats, authentication) - Need to discover edge cases beyond AC **Skip research when:** - Story is trivial (simple CRUD, no external dependencies) - Research comment already exists on Story - User explicitly requests to skip ## Workflow ### Phase 1: Discovery Auto-discover Team ID from `docs/tasks/kanban_board.md`. **Input:** Story ID from orchestrator (ln-510) ### Phase 2: Extract Feature Domain 1) Fetch Story from Linear 2) Parse Story goal and AC to identify: - What technology/API/format is involved? - What is

What's inside
Steps it walks through
  1. Purpose & Scope
  2. When to Use
  3. Workflow
  4. Phase 1: Discovery
  5. Phase 2: Extract Feature Domain
  6. Phase 3: Research Common Problems
  7. Phase 4: Research Competitor Solutions
  8. Phase 5: Research Customer Complaints
  9. Phase 6: Compile and Post Findings
  10. Critical Rules
  11. Definition of Done
  12. Reference Files
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the ln-511-test-researcher skill do?

Researches real-world problems, competitor solutions, and customer complaints before test planning. Posts findings as Linear comment for ln-512 and ln-513.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill ln-511-test-researcher-levnikolaevich-claude-code-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going