CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deep-research

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

Quality

75%

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 ./.agents/skills/deep-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 exemplary lean operational skill: executable commands, concrete flag semantics, explicit validation with a review checklist, and no wasted tokens. Its two real weaknesses are the absent validate-failure feedback loop and a broken progressive-disclosure chain — the findings template it defers to is not in the bundle, leaving the output format underspecified.

Suggestions

Ship templates/findings.md in the bundle (or inline the exact required section list) so the Findings format section does not depend on a file that is not present.

Add one line for the failure path, e.g., "If validate reports errors, fix the findings/sidecar and re-run validate before stopping," to close the error-recovery loop.

Verify agents/planner.md and the ../code-quality/SKILL.md link resolve from the installed skill location, or inline the one-sentence rule they carry.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence throughout — no padding, no explanation of what Exa or research is, and every rule carries skill-specific information the model could not infer (e.g., "Provider payloads go in the sidecar JSON (findings.raw.json beside the report by default), never inline"). This matches 'Lean and efficient; every token earns its place'; the only near-miss is the small auto-generated kendex marker comment block, which is not enough to drop to 4's 'minor instances of over-explanation'.

5 / 5

Actionability

The Running and Validation sections give five copy-paste-ready commands (report with --mode/--output, --query-file, json, validate, doctor), the EXA_API_KEY bullet specifies exactly where to set it including the op:// fallback, and flag semantics are concrete ("--include-domain github.com admits every repo on it and excludes everything else"). This matches 'Fully executable; copy-paste ready code or commands'; the only unspecified invocation is the Pi web_research path, which is a harness-delegated case rather than a gap in the skill's own commands.

5 / 5

Workflow Clarity

The sequence is explicit — run the report in a chosen mode, write findings to the caller's path, then "run validate and stop" — with a concrete validation checkpoint (exit 0 semantics, what validate checks) and a human-review checklist ("Claims the cited sources contradict... Off-topic sources that share an acronym"). It falls short of 5 because there is no explicit error-recovery loop: the body never says what to do when validate reports errors, unlike the anchor-5 pattern 'If errors: fix and re-validate'.

4 / 5

Progressive Disclosure

The overview-to-detail split is good in principle — flag declarations and limits are correctly pushed into scripts/deep-research (verified present, including modeDefaults/parseArgs/applyMode) — but scored against the actual bundle, two referenced paths dangle: templates/findings.md ("carries exactly the sections validate requires") does not exist in the bundle, and agents/planner.md is likewise unverifiable. Since the Findings format section is thin precisely because it defers to a missing file, navigation breaks where it matters most, fitting 'references present but not clearly signaled / could be better organized' better than 4's 'minor organization gaps'.

3 / 5

Total

17

/

20

Passed

Description

57%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 has decent natural trigger coverage for research and comparison requests, but it reads as a load-condition list rather than a capability statement: it never says what the skill produces or how. Tightening it to name the concrete deliverable and adding a 'Use when...' style clause with a few more synonyms would lift it substantially.

Suggestions

State the concrete outcome, e.g., "Runs Exa-backed research and writes a cited findings report (findings.md) with a raw-source sidecar" so the 'what' is explicit rather than implied.

Add an explicit trigger clause with natural synonyms, e.g., "Use when the user asks to research, look into, evaluate, or compare vendors, libraries, or technologies."

Narrow the generic leading phrase "research tasks" (which conflicts with any web-search skill) toward the comparison/investigation niche the skill actually serves.

DimensionReasoningScore

Specificity

"research tasks, architectural investigations, and vendor, library, or technology comparisons" names the domain and a couple of task types, but never states concrete actions or deliverables (e.g., producing a cited findings report). It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than 4, which expects several specific listed actions.

3 / 5

Completeness

The 'when' is explicit ("Load for research tasks, architectural investigations, and vendor, library, or technology comparisons") but the 'what' is weak — the description never says what the skill actually does (runs Exa-backed research and writes a cited findings report with a raw sidecar). This sits between anchor 3 (one half clear, the other missing/weak) and anchor 4, closer to 3 because the 'what' is the vague half.

3 / 5

Trigger Term Quality

Natural phrases like "research", "investigations", and "vendor, library, or technology comparisons" map well to what users would say ("research X", "compare React vs Vue"), giving good keyword coverage. It falls short of 5 because common synonyms like "look into", "evaluate", or "background/due diligence" are absent.

4 / 5

Distinctiveness Conflict Risk

"vendor, library, or technology comparisons" carves a distinct niche, but the leading phrase "research tasks" is broad and would overlap with any general web-search or research skill. It fits 'Somewhat specific but could still overlap with similar skills' rather than 4's 'mostly distinct'.

3 / 5

Total

13

/

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

.agents/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.