CtrlK
BlogDocsLog inGet started
Tessl Logo

test-plan

Generates a comprehensive testing plan based on the current branch changes or a specific PR. Use when creating QA checklists, test plans, or verifying PR readiness.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable instruction skill: concrete commands, a complete output template, a clear sequenced workflow with verification, and clean single-file organization. No bundle files are present, and none are needed.

DimensionReasoningScore

Conciseness

Lean and project-specific throughout — decision rules (e.g. 'SSG for static+SEO, ISR for periodic+SEO'), checklists, and a copy-paste template — with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

Provides executable commands ('git diff production...HEAD', 'gh pr diff {PR_NUMBER}', 'yarn lint/test/build') and a complete output-format template with checkboxes and tables ready to use.

3 / 3

Workflow Clarity

Steps are clearly sequenced (get diff → read COMMON_MISTAKES.md → analyze → generate) and the Pre-Merge Checks section supplies an explicit verification checkpoint; no destructive/batch operation requires a validate-retry loop.

3 / 3

Progressive Disclosure

Self-contained body organized into clear sections (Arguments, Steps, Testing Criteria, Output Format, Guidelines, Final Output) with only a one-level external doc reference and no nested/deep references.

3 / 3

Total

12

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, explicit 'Use when' trigger, and natural trigger terms. Its only weakness is specificity — it names one action with input variations rather than enumerating multiple distinct capabilities.

DimensionReasoningScore

Specificity

Quotes a single concrete action — 'Generates a comprehensive testing plan based on the current branch changes or a specific PR' — with input variations, rather than the multiple distinct actions the anchor-3 example lists.

2 / 3

Completeness

Explicitly answers both what ('Generates a comprehensive testing plan...') and when ('Use when creating QA checklists, test plans, or verifying PR readiness'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms users would say — 'QA checklists, test plans, or verifying PR readiness' — covering common phrasings for the need.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (branch/PR testing plans) with distinct triggers, unlikely to fire for an unrelated skill.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
quran/quran.com-frontend-next
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.