CtrlK
BlogDocsLog inGet started
Tessl Logo

research

Delegate noisy investigation to one or more subagents so the orchestrator's context stays clean, then work from the distilled answer. Use this skill whenever answering a question would require reading many files, long logs, large diffs, or wide codebase surveys — i.e. when producing the answer generates far more noise than the answer itself. Use it for "how does X work", "where is Y used", "what's the root cause of Z", "summarize this PR/log" style questions, and reach for it liberally before reading a pile of files inline.

66

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a clear workflow and a refinement feedback loop. The main weakness is conciseness, as the rationale section explains concepts Claude already knows.

Suggestions

Trim the "Why this matters" section and the colleague-archive analogy; Claude already understands context-window economics, so the payoff can be stated in one line.

Add an explicit validation checkpoint for the returned answer (e.g., verify cited paths/symbols exist before acting on them) to strengthen the workflow.

Tighten the briefing checklist into a compact list so the actionable core scans faster.

DimensionReasoningScore

Conciseness

Mostly efficient, but the "Why this matters" section restates the context-window value Claude already knows and the colleague-archive analogy adds padding that could be trimmed.

3 / 5

Actionability

Gives concrete guidance — "Always spawn research subagents as local agents, never remote", specific model names, a briefing checklist, and a 3-part output format — with only minor gaps.

4 / 5

Workflow Clarity

Clear sequenced flow (when → spawn → model → parallel → brief → signal → after) with a feedback loop ("If a report comes back bloated, send a focused follow-up"), missing only explicit validation checkpoints.

4 / 5

Progressive Disclosure

A single self-contained file with well-organized section headers and no broken or nested references; slightly over the simple-skill line and lacks any progressive file structure.

4 / 5

Total

15

/

20

Passed

Description

91%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 that clearly states what the skill does and when to use it, with rich natural trigger phrases. Slight overlap risk with adjacent research/delegation skills keeps distinctiveness just below the top anchor.

DimensionReasoningScore

Specificity

Names concrete actions — "Delegate noisy investigation to one or more subagents" and "work from the distilled answer" — covering delegation and distillation, with minor gaps in breadth relative to the score-5 anchor.

4 / 5

Completeness

Explicitly answers both what ("Delegate noisy investigation... work from the distilled answer") and when ("Use this skill whenever... Use it for..."), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrasings such as "how does X work", "where is Y used", "what's the root cause of Z", and "summarize this PR/log", plus synonyms like long logs, large diffs, and wide codebase surveys.

5 / 5

Distinctiveness Conflict Risk

Clear niche of context hygiene via subagent delegation with distinct triggers, but minor overlap risk with general subagent-delegation or deep-research skills.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
warpdotdev/common-skills
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.