CtrlK
BlogDocsLog inGet started
Tessl Logo

research

Explore a codebase and research external patterns before planning a new feature. Spawns parallel subagents for codebase investigation and web research, then synthesizes findings into a compact artifact (~200 lines) for user review. Use when starting a non-trivial feature, investigating unfamiliar code, or evaluating libraries and architectural approaches.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

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

A well-structured, actionable skill body with clear workflow sequencing and good progressive disclosure through real reference files. Conciseness and actionability are strong but have minor room for tightening and making the dispatch examples fully executable.

Suggestions

Trim rationale restatements like '**Why research first?**' and 'prevents thrashing and discovers constraints early' since the Purpose section already conveys the motivation.

Show the Task dispatch calls in their full executable form (with subagent_type and run_in_background parameters) rather than the abbreviated `Task(Explore): "..."` signatures.

Collapse the redundant depth-signals table or fold the 'Quick' rows into prose to reduce token weight on the less-common depth choices.

DimensionReasoningScore

Conciseness

Largely efficient with tight tables and a focused workflow, but a few sections restate the rationale (e.g. '**Why research first?**', 'prevents thrashing and discovers constraints early') that could be trimmed.

4 / 5

Actionability

Provides concrete dispatch examples, named subagent types, exact output paths, and a referenced template — but the Task tool calls are shown as pseudocode signatures rather than fully executable calls.

4 / 5

Workflow Clarity

A clear 6-step sequence with explicit checkpoints — a REQUIRED user-review step, 'do NOT dispatch a follow-up agent' guardrail, and anti-patterns — giving robust feedback loops; no destructive/batch operation cap applies.

5 / 5

Progressive Disclosure

Well-organized overview with clearly signaled, one-level-deep references to real bundle files (references/agent-prompts.md, references/template.md), keeping the body lean while offloading detail.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

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, specific description with a clear what/when structure and concrete trigger phrases. Trigger-term coverage is slightly below comprehensive but the distinctiveness and completeness are excellent.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Explore a codebase', 'research external patterns', 'Spawns parallel subagents', 'synthesizes findings into a compact artifact (~200 lines)' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly states both what it does (parallel subagents synthesizing a ~200-line artifact) and when to use it via a clear 'Use when...' clause with concrete trigger scenarios.

5 / 5

Trigger Term Quality

Natural triggers like 'starting a non-trivial feature', 'investigating unfamiliar code', and 'evaluating libraries and architectural approaches' read as things a user would actually say, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The RPI Research-phase niche and 'use at the start of non-trivial features' framing carve a clear, distinct trigger space with minimal overlap against generic exploration skills.

5 / 5

Total

19

/

20

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
ericjohnolson/tessl-test
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.