CtrlK
BlogDocsLog inGet started
Tessl Logo

prp-codebase-question

Research codebase questions using parallel agents - documents what exists, not what should change. Use when the user asks how the codebase works, where something lives, or invokes /prp-codebase-question.

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/prp-codebase-question/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

A thorough, actionable multi-phase research workflow with strong checkpoints and templates. It is held back by monolithic inline content (no progressive disclosure) and an absent agent-failure validation loop for its batch parallel operations.

Suggestions

Extract the research-document markdown template and the PRP store resolver script into references/ or scripts/ and link to them, reducing the monolithic body.

Add a validation/feedback step after Phase 3 for handling agent failures or low-quality returns (retry, re-prompt, or mark gaps) so the batch spawn has a recovery loop.

Trim the redundant 'Critical Reminders' and 'Success Criteria' sections, which restate the per-phase checkpoints and DO/DON'T guidance.

DimensionReasoningScore

Conciseness

The body is mostly efficient procedural content, but 'Critical Reminders' and 'Success Criteria' restate the phase guidance and DO/DON'T lists are repeated, so it could be tightened.

2 / 3

Actionability

Provides copy-paste-ready agent prompt templates, executable bash (the PRP store resolver, git/gh commands), concrete filename patterns, and a full research-document markdown template.

3 / 3

Workflow Clarity

Six clearly sequenced phases each have explicit checkpoint checklists, but parallel agent spawning is a batch operation with no failure/validation handling (e.g., what to do if an agent errors or returns poor results), which caps it at 2.

2 / 3

Progressive Disclosure

Well-organized into phases, but the file is a ~380-line monolith with full document templates and the bash resolver inline and no references/scripts/assets split, so content that could be separate stays inline.

2 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

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

A strong, third-person description with explicit 'Use when' triggers and a distinct documentarian niche. It is slightly light on enumerating multiple discrete actions, which keeps specificity at 2 rather than 3.

DimensionReasoningScore

Specificity

Names the domain ('codebase questions') and a composite action ('Research ... using parallel agents', 'documents what exists') but does not enumerate multiple distinct concrete actions, so it is comprehensive-ish rather than a list of specifics.

2 / 3

Completeness

Clearly states what it does ('Research codebase questions using parallel agents - documents what exists, not what should change') and an explicit 'Use when ...' trigger clause, answering both what and when.

3 / 3

Trigger Term Quality

Includes natural user phrasings ('how the codebase works', 'where something lives') plus the explicit slash-command invocation, giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The 'documents what exists, not what should change' framing plus a named slash command carves a clear, narrow niche unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Wirasm/prp
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.