test-skill-quality
Test Skill Quality
Test any skill's instructions by following them literally, documenting every moment they fail to guide the next action, and fixing the root causes.
Trigger boundary
Use this skill when:
- testing whether a skill's instructions are complete and unambiguous
- auditing a skill for instructional quality before publishing
- dogfooding a skill by running its workflow on a real task
- improving a skill after receiving feedback that it's confusing or incomplete
- validating that fixes to a skill's instructions actually resolved the original friction
Do not use this skill for:
- building a new skill from scratch (use
build-skills) - evaluating the quality of a skill's output (use evaluation suites)
- reviewing code changes in a pull request (use
review-pr)
More from yigitkonur/skills-by-yigitkonur
run-research
Use skill if you are answering one technical research question with current web evidence, Reddit practitioner experience, and source-backed synthesis, optionally fanned out across parallel subagents.
42run-agent-browser
Use skill if you are driving the agent-browser CLI for ad hoc browser automation — @ref snapshots, sessions, forms, extraction, screenshots, headed/stealth, or provider runs.
38publish-npm-package
Use skill if you are publishing to npm via GitHub Actions release workflow with trusted publishing, NPM_TOKEN, provenance, semantic-release, changesets, release-please, or fixing npm publish CI.
35init-agent-config
Use skill if you are creating, auditing, or migrating CLAUDE.md, AGENTS.md, or REVIEW.md instruction files, folder-scoped agent guidance, or cross-agent companion entrypoints.
34build-mcp-use-server
Use skill if you are building TypeScript MCP servers with mcp-use/server — server.tool, response helpers, ctx.auth, sessions, transports, widgets, Inspector, deploy.
34build-skills
Use skill if you are creating or substantially revising a Claude skill and need workspace-first evidence, remote comparison, and repo-fit synthesis before writing SKILL.md.
32