CtrlK
BlogDocsLog inGet started
Tessl Logo

research-assistant

How to conduct good research and write exploitable reports, whatever the format of the sources and of the final report

51

Quality

55%

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

Fix and improve this skill with Tessl

tessl review fix ./research-assistant/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 well-structured, actionable instructional guidance for conducting and writing up research, with strong source-tracing specificity. It is held back by philosophical padding and an implicit rather than explicit workflow with validation checkpoints.

Suggestions

Trim philosophical filler ('nothing exists in a vacuum', the 'vast amounts of knowledge' preamble) to tighten token efficiency.

Make the workflow sequence explicit with numbered phases and concrete checkpoints (e.g., 'after each source, record confidence + citation before moving on').

Consider moving the reference-formatting examples and stable-reference guidance into a short companion reference file to keep the overview lean.

DimensionReasoningScore

Conciseness

Mostly efficient actionable guidance, but padded with philosophical asides Claude doesn't need ('nothing exists in a vacuum', 'You have been trained with vast amounts of knowledge, that's good, you should exploit that').

3 / 5

Actionability

Provides concrete, specific guidance appropriate to an instruction-only skill: an explicit 'Always Include' list (confidence levels, source types) and concrete reference-format examples, with only minor abstract phrasing.

4 / 5

Workflow Clarity

Sections form a loose thematic sequence (assumptions -> search -> write-as-you-go -> cite -> note unreachable) but checkpoints are implicit rather than explicit; no destructive/batch cap applies.

3 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no external references needed for a cohesive methodology skill; slightly over the 50-line simple-skill threshold and a few inline examples could be split out.

4 / 5

Total

14

/

20

Passed

Description

50%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 clearly states the skill's purpose but is missing any 'when to use' trigger guidance, which caps completeness, and its keywords are generic enough to risk overlap with other research skills.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases such as 'research a topic', 'write a report', or 'investigate and summarize sources'.

Include natural synonyms and variations (e.g., 'literature review', 'deep dive', 'briefing', 'memo') to improve trigger-term coverage.

Tighten the scope to reduce overlap, e.g. specify the kind of reports or source formats that distinguish this from generic research skills.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('conduct good research', 'write exploitable reports') plus a scope qualifier, but the actions are high-level rather than comprehensive and 'exploitable' is jargon.

3 / 5

Completeness

Has a clear 'what' (conduct research, write reports) but no 'Use when...' clause or equivalent trigger guidance, so per the cap it cannot exceed 3.

3 / 5

Trigger Term Quality

Contains some relevant natural keywords ('research', 'reports', 'sources') but misses common variations, synonyms, and specific trigger phrases users would say.

3 / 5

Distinctiveness Conflict Risk

'Research and report writing' is a recognizable niche but 'research' is broad and overlaps with other research-oriented skills, so overlap risk remains.

3 / 5

Total

12

/

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
YPares/agent-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.