CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-ops

Evidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.

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

Quality

Content

75%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, token-efficient orchestration skill: clear sequencing, concrete routing between sibling skills, an explicit output template, and a verification checklist, with no padding or filler. It falls just short of top marks on conciseness (a taxonomy repeated four times), actionability (two under-specified steps), and workflow (no recovery loop when verification fails).

Suggestions

State the sourced-fact / user-provided / inference / recommendation taxonomy once (e.g. in Guardrails or the Output Format) and reference it from the other sections instead of repeating it in four places.

Add a feedback loop to Verification: what to do when a check fails (e.g. 'if a claim is unlabeled, re-tag it before delivering; if a freshness-sensitive answer lacks a date, re-run the search lane').

Make step 1 and step 5 operationally concrete — e.g. specify how supplied material is triaged (bullet rewrite rules) and what recommending a 'monitoring or workflow layer' concretely means (name the tool or skill to hand off to).

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven with zero padding and no explanations of concepts Claude already knows; the main trim opportunity is redundancy — the sourced-fact / user-provided / inference / recommendation taxonomy appears four times (Guardrails, Workflow step 4, Output Format, Pitfalls). That is a minor, not noticeable, redundancy, so anchor 4 fits better than 3 or 5.

4 / 5

Actionability

As an instruction-only skill, no code is required, and the guidance is mostly executable: concrete skill routing ('use `exa-search` for fast discovery', 'escalate to `deep-research` when synthesis or multiple sources matter'), a four-lane classification menu, and a copy-paste-ready output format template. Minor gaps keep it below anchor 5: 'Normalize any supplied material' and step 5's 'recommend a monitoring or workflow layer' give no operational detail on how to do so.

4 / 5

Workflow Clarity

The five-step workflow is clearly sequenced (normalize input, classify, take the lightest path, report with evidence boundaries, decide on monitoring) and ends with an explicit Verification checklist ('important claims are labeled by evidence type', 'freshness-sensitive outputs include dates', 'the final recommendation matches the actual research mode used'). Not anchor 5 because there is no feedback loop for what to do when a verification check fails, and the research operations are non-destructive so no cap applies.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so all guidance lives in a single SKILL.md with clean, well-labeled sections (Skill Stack, When to Use, Guardrails, Workflow, Output Format, Pitfalls, Verification) and no monolith problem. The under-50-lines simple-skill exception for a 5 does not apply (body is ~103 lines), and nothing yet warrants splitting, so anchor 4 (good structure, appropriately placed content) is the best fit.

4 / 5

Total

16

/

20

Passed

Description

66%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 solid description with a clear, explicit 'Use when...' clause and natural trigger terms, undermined by an abstract 'what' — the capability is described as a 'workflow' rather than concrete actions — and by unaddressed overlap with the neighboring research skills it orchestrates. It is clearly above the vague 'does stuff' tier but below the exemplary concrete-action descriptions.

Suggestions

Replace the abstract 'research workflow' with concrete operative verbs, e.g. 'Runs current-web searches, compares options, and enriches people/companies with public evidence' so the 'what' side names actions rather than an abstraction.

Add the natural trigger phrases already used in the body ('look up', 'what's the latest', 'compare options') to the description to widen trigger-term coverage.

State the skill's orchestrator role in the description (e.g. 'routes between deep-research, market-research, and lead-intelligence') to reduce conflict risk with those skills at trigger time.

DimensionReasoningScore

Specificity

The description names the domain clearly ("current-state research workflow") and lists deliverable types ("fresh facts, comparisons, enrichment, or a recommendation"), but the core capability is the abstract noun "workflow" rather than concrete actions. It fits anchor 3 (domain plus 1-2 concrete actions, not comprehensive) — not anchor 4 because no specific operative verbs like 'extracts', 'compares', or 'enriches' are given, and not anchor 2 because the domain is precisely named with several outcome types enumerated.

3 / 5

Completeness

Both parts are present: the what ("Evidence-first current-state research workflow for ECC") and an explicit when ("Use when the user wants fresh facts, comparisons, enrichment, or a recommendation...") with concrete trigger objects. It is not anchor 5 because the 'what' side is vague — 'workflow' does not state what is actually done — while the 'when' side is strong; anchor 4 (both present, one could be more explicit) is the best fit.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "research", "comparisons", "enrichment", "recommendation", "fresh facts" are phrases users would naturally say. Missing common variations such as "look up", "what's the latest", or "who should I talk to" (which appear in the body but not the description), so it falls short of the comprehensive-synonyms anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Research" is broad territory with high overlap risk against general research/search skills (the body itself names deep-research, market-research, exa-search as neighbors). Scoping signals exist ("for ECC", "evidence-first", "current public evidence") but the description does not distinguish this orchestrator from the underlying research skills, so anchor 3 (somewhat specific, could overlap with similar skills) fits better than 4.

3 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

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