CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deep-research

Load for research tasks, architectural investigations, and vendor, library, or technology comparisons.

Quality

71%

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

Quality

Content

90%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 exemplary lean operator guide: copy-paste-ready commands, an explicit validate-and-stop gate, a manual verification checklist, and details correctly pushed down into the bundled script. The only notable gaps are the missing error-recovery loop around validation and a dangling templates/findings.md reference that has no corresponding file in the bundle.

DimensionReasoningScore

Conciseness

The ~50-line body is dense and lean: every rule carries operational substance (output paths, citation and sidecar policy, API-key handling, mode semantics) and nothing explains concepts Claude already knows. Even the flag explanations (--additional-query, --include-domain) document non-obvious tool-specific behavior, so every token earns its place.

5 / 5

Actionability

The Running section gives copy-paste-ready commands covering report (both inline-query and --query-file forms), json, validate, and doctor, with concrete modes and flag semantics; the Validation section repeats the exact validate invocation and describes its output contract ({ok, errors, warnings, mode, synthesis, queryCount}, exit 0). Missing-key remediation is concrete (Customize tab, .env.local, KENDEX_ENV_FILE, op:// reference).

5 / 5

Workflow Clarity

The sequence is clear and gated by an explicit validation checkpoint ("Once the report and its sidecar exist, run validate and stop") plus a manual review checklist (contradicted claims, off-topic sources, unsupported recommendations). It falls short of anchor 5 because no error-recovery loop is stated — what to do when validate reports errors (fix and re-validate vs. re-run research) is left implicit.

4 / 5

Progressive Disclosure

Good structure: the body stays an overview and defers flag declarations and limits to the bundled script by named symbols (modeDefaults, parseArgs, applyMode — all verified present in scripts/deep-research). It misses anchor 5 because the referenced path templates/findings.md does not exist in the bundle (the template is embedded in the script), and agents/planner.md plus ../code-quality/SKILL.md point outside the skill's own files.

4 / 5

Total

18

/

20

Passed

Description

43%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 a pure trigger sentence: it does a reasonable job of saying when to load the skill, with several natural trigger phrases, but it never says what the skill actually does, and the broad term 'research tasks' invites overlap with other research-flavored skills. Adding a one-clause capability statement would lift both completeness and specificity.

Suggestions

Add a 'what' clause stating the capability and deliverable, e.g. "Runs Exa-powered deep research and writes an evidence-backed findings.md report" — completeness scored 2 because only the 'when' half is present.

Include natural trigger synonyms users actually say, such as "compare X vs Y", "evaluate options", or "due diligence", to broaden keyword coverage beyond research/investigations/comparisons.

Pair the broad lead term "research tasks" with the concrete deliverable (evidence-backed findings report) to reduce trigger overlap with generic web-search or research skills.

DimensionReasoningScore

Specificity

The description names the domain ("research tasks, architectural investigations, and vendor, library, or technology comparisons") but contains no capability actions at all — it is purely a load trigger, with no verbs describing what the skill does (the 'what' lives only in the separate summary field). It is above anchor 1 because the trigger categories are concretely named, but below anchor 3 because no concrete actions are listed.

2 / 5

Completeness

Only the 'when' is present ("Load for research tasks, architectural investigations, and vendor, library, or technology comparisons") with no statement of what the skill does — matching anchor 2's "only 'when' is present without 'what'" (cf. "Use when working with documents"). It cannot reach anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

"research tasks", "vendor... comparisons", "library, or technology comparisons", and "architectural investigations" are phrases users would naturally say when they need this skill. It falls short of anchor 5 because common synonyms and variations ("compare X vs Y", "evaluate options", "deep dive", "due diligence") are missing.

4 / 5

Distinctiveness Conflict Risk

The comparison/investigation angle carves a partial niche, but the broad lead term "research tasks" would also match general web-search or research-oriented skills, so overlap with similar skills remains realistic. It is more specific than anchor 2's generic breadth but does not achieve anchor 4's 'mostly distinct, minor overlap risk only with closely related skills'.

3 / 5

Total

11

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

vanillagreencom/kendex

Path

skills/deep-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.