CtrlK
BlogDocsLog inGet started
Tessl Logo

scholar-evaluation

Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/scientific-thinking-scholar-evaluation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, lean rubric with a clear review workflow and reusable output template, assuming Claude's competence throughout. Its only weakness is the lack of a worked example illustrating how to apply the 1–5 scale to a real artifact.

Suggestions

Add one short worked example (e.g., a sample dimension row with a filled score, evidence, and revision priority) to make the 1–5 scale unambiguous.

Clarify how N/A dimensions should be reflected in the overall score.

Consider a one-line note on how to handle disagreement between dimension scores when computing the overall confidence.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence — it lists evaluation questions and a scoring rubric without explaining what a literature review or citation is, so every token earns its place.

3 / 3

Actionability

The rubric questions and output template are concrete and reusable, but as an instruction-only skill it gives no worked example of an evaluated artifact, leaving the exact application of the 1–5 scale somewhat abstract.

2 / 3

Workflow Clarity

The 'Review Process' section gives a clear six-step sequence, and the distinction between scoring dimensions and separating critical blockers from revisions acts as an explicit validation checkpoint before output.

3 / 3

Progressive Disclosure

A single self-contained file with well-organized sections (When to Use, Evaluation Scope, Rubric, Review Process, Output Template, Pitfalls); no external references are needed, which fits a simple skill well.

3 / 3

Total

11

/

12

Passed

Description

67%

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 specific and distinct but omits an explicit 'Use when...' trigger clause, leaving the activation condition implied rather than stated. Adding a natural trigger phrase would raise both completeness and trigger_term_quality.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrasings (e.g., 'Use when reviewing a research paper, thesis, or proposal, or when checking whether claims are supported by cited evidence').

Add common trigger terms users actually say, such as 'peer review', 'review my paper', and 'check my citations'.

Keep the concrete action list but trim redundancy so the description stays concise.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback' — describing the specific evaluation activities.

3 / 3

Completeness

Answers 'what' concretely but lacks an explicit 'Use when...' trigger clause, so the 'when' guidance is only implied by the listed artifact types, which caps completeness at 2.

2 / 3

Trigger Term Quality

Includes some natural terms ('research paper', 'proposal', 'literature review', 'methods sections') but is missing common user phrasings like 'peer review', 'review my paper', or 'check my citations'.

2 / 3

Distinctiveness Conflict Risk

The scholarly-work niche is clearly bounded and distinct from general writing or coding skills, with triggers unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.