CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, well-organized orchestration skill with concrete routing guidance and an explicit output contract. The main improvement would be de-duplicating the evidence-typing list and folding verification into inline workflow checkpoints.

Suggestions

De-duplicate the 'sourced fact / user-provided evidence / inference / recommendation' taxonomy, which appears in Guardrails, step 4, and Output Format — define it once and reference it.

Move verification checks inline as checkpoints within the workflow steps (e.g., 'before recommending, confirm each claim is labeled by evidence type') rather than only as a trailing section.

Consider a one-line explicit note that the referenced sibling skills (exa-search, deep-research, etc.) are invoked by name rather than bundled, so Claude does not look for local reference files.

DimensionReasoningScore

Conciseness

Lean, imperative, assumes Claude's competence, but the evidence-typing list (sourced fact / user-provided evidence / inference / recommendation) is restated across Guardrails, step 4, and Output Format and could be trimmed.

4 / 5

Actionability

Concrete routing to named sub-skills with explicit escalation conditions and a copy-ready output template; minor gaps only because there are no literal commands (appropriate for an orchestration skill).

4 / 5

Workflow Clarity

Clear 5-step numbered sequence plus a Verification section, but checkpoints live in a separate section rather than as inline validate-then-proceed feedback loops within the steps.

4 / 5

Progressive Disclosure

Well-organized into distinct sections (Skill Stack, When to Use, Guardrails, Workflow, Output Format, Pitfalls, Verification); as a simple under-50-line skill with no bundle files needed, this structure earns full marks.

5 / 5

Total

17

/

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, well-structured description that clearly states both the workflow's purpose and explicit use-when triggers. Minor overlap with the orchestrated sibling skills is the only weakness.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete action types ('fresh facts, comparisons, enrichment, or a recommendation'), giving comprehensive coverage rather than just 1-2 actions.

5 / 5

Completeness

Explicitly answers both 'what' ('Evidence-first current-state research workflow for ECC') and 'when' ('Use when the user wants fresh facts, comparisons, enrichment, or a recommendation...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural terms (facts, comparisons, enrichment, recommendation, current evidence) but a few common user phrases like 'look up' appear only in the body, not the description itself.

4 / 5

Distinctiveness Conflict Risk

Clear niche (evidence-first current-state research) but minor overlap risk with the closely-related sub-skills it orchestrates (deep-research, exa-search).

4 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.