CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

meta-research

Use when a wrong answer is expensive: strategy research, comparing several products or markets, validating a hypothesis with outside data. Fans out searches and sub-agents, triangulates each claim across 3+ sources and saves every source with quotes. Quick facts: answer directly.

Quality

79%

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

Quality

Content

60%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 operational methodology: clear phase sequence with named validation checkpoints, concrete output artifacts, and a useful anti-patterns checklist. Its weaknesses are redundant positioning prose, and unspecified execution details — the self-critique questions, scoring mechanics, and the channel/block catalog — that keep phases 5 and 6 from being actionable as written.

Suggestions

Cut the 'How it differs from a quick research router' section and keep only its concrete differentiator list (falsifiable hypotheses, parallel fan-out, per-source files, refresh_targets.md); the slow-vs-rigorous positioning is already made in the intro and the description.

Enumerate the 4 self-critique questions and define the Credibility/Recency/Bias scoring scale (or bundle them in a reference file) so the adversarial pass and triangulation phases are executable without invention.

Add a compact template for sources/NN.md (metadata fields, quote format, score line) so Phase 4's per-source output is unambiguous across runs.

DimensionReasoningScore

Conciseness

The pipeline, mechanisms, output tree, and anti-patterns are dense and operational, but the positioning ('heavy, methodical end of research', low-risk router contrast) is stated three times — in the intro, the two-paragraph 'How it differs from a quick research router' section, and 'When to use' — which is more than minor trimmable material. Not 2 because nothing explains concepts Claude already knows and there is no filler padding.

3 / 5

Actionability

Concrete rules exist (≥3 differently-typed sources, sources/NN_slug.md naming, Credibility/Recency/Bias dimensions, the output tree), but key execution details are missing: the '4 self-critique questions' are referenced twice without ever being enumerated, the scoring mechanics are unspecified, and the search channels and report blocks live in an external upstream repo rather than the bundle. Not 4 because these gaps exceed 'minor' — the adversarial and scoring phases cannot be executed as written.

3 / 5

Workflow Clarity

The 9-phase table gives a clear sequence with explicit validation checkpoints (Phase 5 triangulation, Phase 6 adversarial pass, Phase 6.5 citation check), a re-evaluation loop in Phase 4, depth gating, and stop-criteria in plan.md. Not 5 because the checkpoints are one-line descriptions without fix/retry mechanics — e.g. 'Lightweight citation check before closing' says nothing about what to check or what happens on failure.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview with one clearly signaled, load-on-demand reference (references/full-catalog.md, verified to exist) — good structure with appropriate placement. Not 5 because that reference's actual content (channels, blocks, phases.yaml) is deferred again to an external GitHub repo, a chained-reference pattern for the sourcing surface.

4 / 5

Total

14

/

20

Passed

Description

88%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 description: third-person, concrete about both capabilities and triggers, with an explicit 'Use when' clause and a routing negative that separates it from quick lookups. The only gaps are a few missing natural synonyms and residual overlap risk with generic research requests.

DimensionReasoningScore

Specificity

Multiple concrete third-person actions are named — 'Fans out searches and sub-agents, triangulates each claim across 3+ sources and saves every source with quotes' — covering the skill's core operations comprehensively, matching the anchor-5 example's density of specific actions rather than the minor-gaps anchor 4.

5 / 5

Completeness

Both questions are explicitly answered: 'Use when a wrong answer is expensive: strategy research, comparing several products or markets, validating a hypothesis with outside data' gives concrete when-triggers, and the fan-out/triangulation/persistence sentence gives the what, plus the routing negative 'Quick facts: answer directly'.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('strategy research', 'comparing several products or markets', 'validating a hypothesis with outside data'), but common variations like 'deep research', 'due diligence', or 'fact-check' are missing, placing it just below the comprehensive-synonym anchor 5.

4 / 5

Distinctiveness Conflict Risk

The 'wrong answer is expensive' framing and the quick-facts contrast carve a distinct high-rigor niche, but a generic 'research this topic' request could still overlap with a lighter research skill — mostly distinct with minor overlap risk, not the minimal-conflict anchor 5.

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

alirezarezvani/claude-skills

Path

research/meta-research/skills/meta-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.