CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-scholar

Search academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.

Quality

74%

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/oma-scholar/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 dense, well-sectioned body with genuinely actionable commands, exact schema field rules, and explicit validation with error-recovery guidance. Its weaknesses are duplication (commands and fallback logic repeated across sections, routing metadata duplicated from the description), no inline example of the core output artifact, and a References section where most pointed-to files are missing from the bundle.

Suggestions

Consolidate the duplicated command listings ("Canonical command path" vs "Quick Reference") and describe the knows.academy→OpenAlex→Semantic Scholar fallback in one place only.

Include a minimal example `.knows.yaml` sidecar (or a skeleton with the exact top-level keys, statement/evidence/relation shape, and confidence/coverage objects) inline so Generate mode does not depend solely on the external spec file.

Fix or ship the referenced bundle files — `resources/sidecar-spec.md`, `resources/execution-protocol.md`, `resources/checklist.md`, and the other `resources/*.md` paths are cited multiple times but absent from the bundle, breaking navigation.

DimensionReasoningScore

Conciseness

The body avoids explaining known concepts, but it is noticeably repetitive and could be tightened: the same `oma scholar search|resolve|get` commands appear in both "Canonical command path" and "Quick Reference", the provider fallback is described in four places (Transitions, Guardrails, "Provider Fallback", Troubleshooting), and the "Scheduling" block restates routing info already in the description and Modes table. Time-sensitive specifics ("only 2026 papers", v0.9.0, the 47% dangling-ref stat) sit inline rather than in a versioned/deprecated section. This matches "mostly efficient but includes some unnecessary explanation or could be tightened"; too much duplication for a 4.

3 / 5

Actionability

Concrete, executable guidance throughout: exact CLI invocations with flags (`oma scholar lint --fail-on-warning paper.knows.yaml`), raw curl endpoints, exact field names (`statement_type`, `evidence_type`), ID format examples, and an error-message-to-fix troubleshooting table. Not a 5 because the primary Generate mode never shows an example `.knows.yaml` sidecar and defers the artifact format to `resources/sidecar-spec.md`, which is absent from the provided bundle — a real gap for the most common case.

4 / 5

Workflow Clarity

A clear PREPARE→ACQUIRE→REASON→ACT→VERIFY→FINALIZE sequence is present with an explicit validation step ("run lint before sharing", guardrail 13) and feedback loops (failure/recovery section plus an error→fix troubleshooting table with retry guidance). It falls short of a 5 because per-mode numbered execution steps are delegated to `resources/execution-protocol.md`, which is not present in the bundle, leaving the concrete step order for each mode implicit.

4 / 5

Progressive Disclosure

Section structure is good and the References list clearly labels each file with its purpose at one level deep, but scored against the actual bundle, 9 of the 11 referenced paths do not exist (all `resources/*.md`, `cli/commands/scholar/`, `config/scholar-config.yaml`, `../../rules/i18n-guide.md`); only the two `references/_shared/core/` files are present. Navigation to the spec, checklist, and protocol files is broken in the provided bundle, and much of the shared `references/_shared/` content is never referenced — better than minimal structure, but the broken reference paths are more than the minor organization gaps of a 4.

3 / 5

Total

14

/

20

Passed

Description

75%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, concise description in third person that names concrete capabilities and includes an explicit "Use for..." clause. Its main weaknesses are a missing mode (peer review as sidecar) and a when-clause that gives trigger guidance for only two of the skill's several modes.

Suggestions

Extend the trigger clause to mention-based phrases covering all modes, e.g. "Use when the user mentions .knows.yaml, Knows, OpenAlex, DOIs, paper claims/evidence, or asks to generate, validate, peer-review, or compare paper sidecars".

Add the review capability ("generate, validate, review, or compare Knows paper sidecars") so the description covers all six modes.

DimensionReasoningScore

Specificity

"Search academic literature and generate, validate, or compare Knows paper sidecars" lists several concrete actions (search, generate, validate, compare, claim/evidence analysis, literature synthesis), but coverage has minor gaps — the peer-review-as-sidecar mode is absent. Fits the score-4 anchor (several specific actions, minor gaps) better than 5, since a whole mode is unmentioned.

4 / 5

Completeness

The "what" is clear ("Search academic literature and generate, validate, or compare Knows paper sidecars") and an explicit "Use for claim/evidence analysis and literature synthesis" clause provides the "when", so the missing-trigger-clause cap of 3 does not apply. Not a 5 because the when-clause covers only two scenarios and lacks mention-based trigger phrases (e.g., "when the user mentions .knows.yaml, OpenAlex, or asks for a literature search") for the generation/validation/comparison modes.

4 / 5

Trigger Term Quality

Natural terms like "academic literature", "claims", "evidence", "literature synthesis", and the niche markers "Knows" and "sidecars" are present. Common variations users would actually say — "papers", "peer review", "citations", "DOI", "OpenAlex" — are missing, matching "good keyword coverage; a few natural terms missing" rather than the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

"Knows paper sidecars" and "claim/evidence analysis" anchor a clear niche with minimal conflict risk, but the leading clause "Search academic literature" is generic enough to overlap with a general web-search or literature-search skill. Mostly distinct with minor overlap risk against closely related search skills — a 4, not the minimal-conflict 5.

4 / 5

Total

16

/

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

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

first-fluke/oh-my-agent

Path

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