CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scholar-evaluation

Provides qualitative-first, evidence-traceable developmental review of scholarly works and audit low-stakes research-assessment rubrics with optional local quality controls. Never use for ranking people or consequential decisions.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

81%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 skill body is a strongly engineered operational document: exact commands, a checkpointed eight-step workflow with validation and fail-closed controls, and a well-organized one-level-deep bundle. Its main weakness is token efficiency — provenance and citation prose inlined in SKILL.md could move to reference files.

Suggestions

Move the ScholarEval bibliographic status section and the 'Citing Scientific Agent Skills' boilerplate into references/source_ledger.md (or a dedicated references file), leaving one-line pointers in SKILL.md.

Trim the metric-policy paragraph's nine-item recording checklist to a short rule plus a pointer into references/responsible_assessment.md, keeping the policy detail out of the main body.

Consolidate time-sensitive dates (arXiv revision, ledger refresh) into the source ledger so SKILL.md carries only the reference, reducing stale-prone tokens in the always-loaded file.

DimensionReasoningScore

Conciseness

The body is dense and operational with no filler explanations of concepts Claude already knows, but it carries non-operational prose that could be tightened: the ScholarEval bibliographic status section, the skill-library citation boilerplate, and several absolute dates (arXiv revision dates, ledger refresh dates) that belong in reference files. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than anchor 4's 'minor instances', since these sections are a noticeable chunk rather than isolated instances.

3 / 5

Actionability

Six copy-paste-ready bash commands with exact paths, flags, and template arguments; an exact status vocabulary (`rated`/`missing`/`not_applicable`); exact allowed data classifications; and concrete per-step recording requirements fully cover the common cases, matching the 'fully executable, copy-paste ready' anchor.

5 / 5

Workflow Clarity

The eight-step workflow is clearly sequenced with explicit validation gates (validate_rubric, check_traceability, check_process), stop conditions ("Stop on a prohibited decision context or unnecessary private data"), conditional recovery paths ("If the work changes materially, issue a new evaluation linked to the prior revision"), and a fail-closed human-review checklist — matching the anchor for explicit validation steps, feedback loops, and checklists.

5 / 5

Progressive Disclosure

Every referenced file exists in the bundle, all references are one level deep, and the 'Bundled resources' section gives a well-signaled index with one-line descriptions of each file. It falls short of anchor 5 because some detail that could live in references is inlined in SKILL.md (the ScholarEval bibliographic record, the metric-policy recording checklist) and evaluation_framework.md itself points onward to source_ledger.md — minor organization gaps consistent with anchor 4.

4 / 5

Total

17

/

20

Passed

Description

53%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 clearly states what the skill does and draws a sharp safety boundary, but it lacks any positive trigger guidance and misses the natural vocabulary (paper, draft, manuscript) users would employ. It is distinct within its niche yet only moderately actionable as a trigger surface.

Suggestions

Add a positive 'Use when...' clause (e.g., 'Use when reviewing a paper, draft, protocol, literature synthesis, or research idea, or when auditing a low-stakes assessment rubric') so the 'when' is explicit rather than only implied by exclusions.

Include natural user phrasings as trigger terms — 'paper', 'draft', 'manuscript', 'peer review feedback', 'evaluate my research idea' — alongside the current formal vocabulary.

Name one or two more concrete actions (e.g., 'rate criteria against anchored rubrics and check evidence traceability') to sharpen capability specificity beyond the two abstract actions currently listed.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — "developmental review of scholarly works" and "audit low-stakes research-assessment rubrics" — matching the anchor for 1-2 concrete actions without comprehensive coverage; the actions stay abstract compared to anchor 4's multi-action lists, and "optional local quality controls" is not a concrete action.

3 / 5

Completeness

The 'what' is clear (qualitative-first, evidence-traceable developmental review plus rubric auditing), but there is no positive 'Use when...' clause — only the negative exclusion "Never use for ranking people or consequential decisions" weakly implies triggers, which caps completeness at 3 per the judging guideline.

3 / 5

Trigger Term Quality

Relevant keywords are present ("scholarly works", "review", "rubrics", "research-assessment"), but common natural variations users would actually say — "paper", "draft", "manuscript", "peer review", "evaluate" — are missing, fitting the 'some relevant keywords but missing common variations' anchor rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

The niche — developmental, evidence-traceable review of scholarly works plus low-stakes rubric auditing with explicit exclusions — is mostly distinct with minimal conflict risk, but natural phrases like "review my paper" could overlap with generic writing-review or peer-review skills since the description claims no distinct positive triggers, keeping it below anchor 5.

4 / 5

Total

13

/

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

K-Dense-AI/scientific-agent-skills

Path

skills/scholar-evaluation/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.