CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research

Investigate an open question and return grounded, sourced findings

Quality

76%

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 ./skills/research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

The body is an exemplar of lean, token-efficient instruction: a clear goal, a concrete 5-step workflow, a scale ladder for sizing effort, and enforceable rules. The only notable gap is the absence of worked examples (e.g., a sample sourced finding) that would make the output format unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — e.g., 'Replace assumptions with evidence, and say plainly what remains uncertain' and 'Search the repo and its docs first — local evidence outranks recollection' — with no padded explanations of concepts Claude already knows. Every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

The guidance is directive and specific ('Sweep more than one way when the answer could hide: by file, by symbol, by caller, by history'; 'Cite the source: file and line, or the document consulted'), so it is mostly executable for an instruction-only skill. Not a 5 because there are no concrete examples covering common cases (e.g., a sample finding with its citation format or an example of verified-vs-inferred phrasing); not a 3 because nothing is pseudocode or missing key details.

4 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced, and checkpoints exist — step 1's 'precisely enough to know when it is answered' is a completion criterion, and 'keep going until additional passes surface nothing new' is a stopping rule. Not a 5 because these checkpoints are distributed across Goal, Scale, and Rules rather than embedded as explicit validate-and-retry steps in the workflow itself; not a 3 because the sequence is complete with no validation gaps for a read-only skill.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and its sections (Goal, Workflow, Scale, Rules, Output) are well organized, which per the judging guidelines earns a 5 with just well-organized sections. There are no bundle files to verify, and none are needed.

5 / 5

Total

18

/

20

Passed

Description

53%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.

The description is concise and cleanly states what the skill does, with a mostly distinct niche. Its main weaknesses are the complete absence of a 'when to use' trigger clause (capping completeness) and missing the most natural trigger synonyms like 'research' or 'look into'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the answer is not yet known and the next step depends on it' or 'Use when asked to research, look into, or find out something'.

Include natural trigger synonyms users would actually say — 'research', 'look into', 'find out' — alongside 'investigate' to improve keyword coverage.

Enumerate one or two more concrete actions (e.g., 'search the repo by file, symbol, and history; consult official docs for external APIs') to raise specificity from 1-2 actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain ('an open question') and two actions ('Investigate' and 'return grounded, sourced findings'), matching the anchor for naming a domain with 1-2 concrete actions that are not comprehensive. It is not a 4 because 'Investigate' is generic and coverage of what the investigation involves is narrow; not a 2 because the second action ('return grounded, sourced findings') adds concrete specifics.

3 / 5

Completeness

The 'what' is clearly stated (investigate an open question, return grounded sourced findings), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

'Investigate', 'open question', and 'findings' are relevant natural keywords, but the most common user phrasings — 'research', 'look into', 'find out' — are absent, fitting the 'some relevant keywords but missing common variations or synonyms' anchor. It is not a 4 because key synonyms users would actually say are missing.

3 / 5

Distinctiveness Conflict Risk

'Investigate an open question and return grounded, sourced findings' carves a fairly distinct research niche with only minor overlap risk against closely related search or exploration skills, matching 'mostly distinct; minor overlap risk'. Not a 5 because 'investigate' could still collide with general search or code-exploration skills; not a 3 because the sourced-findings framing is distinctly its own.

4 / 5

Total

13

/

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

Yeachan-Heo/oh-my-claudecode

Path

skills/research/SKILL.md

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.