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

82%

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

The canonical home for this skill is oma-scholar in first-fluke/oh-my-agent

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.

A dense, highly actionable skill body with excellent executable command coverage and a well-sequenced multi-mode workflow with explicit validation and recovery paths. Its main weaknesses are meta-framework padding (SSL primitive table, Scenes scaffolding, duplicated fallback description) that inflates token cost, and an over-long body that inlines spec detail while referencing bundle files that are not actually shipped.

Suggestions

Remove or compress the framework meta sections ("Actions | SSL primitive | Evidence" table, "Scenes" scaffolding, "Intent signature", "Control-flow features") into a short mode-dispatch description, cutting roughly 40 lines without losing executable guidance.

Deduplicate the OpenAlex/Semantic Scholar fallback story: keep the detailed "Provider Fallback" section and reduce the Transitions/Dependencies mentions to one-line pointers.

Ship or trim the references: either include the referenced "resources/*.md" and "../_shared/*" files in the bundle, or cut the 18-item guardrails down to the load-bearing ones and defer exact enum/format rules to "resources/sidecar-spec.md".

DimensionReasoningScore

Conciseness

Mostly operational, but padded with framework meta-description that does not instruct: the "Actions | SSL primitive" table (SELECT/READ/INFER), the Scenes scaffolding (PREPARE/ACQUIRE/REASON/ACT/VERIFY/FINALIZE), "Intent signature", and "Control-flow features". The OpenAlex fallback is also described twice (Transitions and the Provider Fallback section). Below anchor 4 because these sections are trimmable without losing guidance; above anchor 2 because the bulk is concrete commands and rules, not concept explanation Claude already knows.

3 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: "oma scholar search \"diffusion super resolution\"", "oma scholar get --section statements \"knows:generated/reconvla/1.0.0\"", "oma scholar lint --fail-on-warning paper.knows.yaml", raw curl endpoints, and a troubleshooting table keyed to exact error strings with concrete fixes ("value: '22' -> value: 22").

5 / 5

Workflow Clarity

Entry -> Scenes -> Transitions -> Failure and recovery -> Exit is clearly sequenced with explicit validation checkpoints (VERIFY scene, "run lint before sharing", guardrail 13) and feedback loops for error recovery (retry or OpenAlex fallback on API timeout, fix-indentation loop on YAML parse failure, error-to-fix troubleshooting table). No destructive or batch operations lack validation.

5 / 5

Progressive Disclosure

A dedicated References section lists one-level-deep, well-signaled files ("resources/sidecar-spec.md", "resources/api-endpoints.md", etc.) and heavy spec detail is nominally deferred. Below anchor 5 because the ~275-line body still inlines content that belongs in those files (the 18-item guardrails largely duplicate "resources/sidecar-spec.md"), and none of the referenced files ("resources/*.md", "../_shared/*", "../../rules/i18n-guide.md") are present in the shipped bundle, so reference targets cannot be verified. Above anchor 3 because splitting intent and navigation are otherwise clear.

4 / 5

Total

17

/

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 third-person description with explicit what and when clauses and mostly natural trigger terms. It is held below the top anchors by unmentioned modes (analyze/review/fetch), missing synonyms and the ".knows.yaml" extension, and slight overlap risk on the generic phrase "Search academic literature".

DimensionReasoningScore

Specificity

"Search academic literature and generate, validate, or compare Knows paper sidecars" lists several concrete actions (search, generate, validate, compare) plus "claim/evidence analysis and literature synthesis". Not 5 because the body's analyze/review/fetch/remote modes are unmentioned; not 3 because coverage goes well beyond 1-2 actions.

4 / 5

Completeness

Explicit what ("generate, validate, or compare Knows paper sidecars") and explicit when ("Use for claim/evidence analysis and literature synthesis"). The when-clause names use cases but lacks concrete trigger phrasing ("when the user mentions..."), matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Natural phrases users would say are present: "academic literature", "paper sidecars", "claims", "evidence", "literature synthesis". Missing the breadth of anchor 5 (no synonyms like "research papers" and no file extension ".knows.yaml"), but clearly above anchor 3's partial keyword coverage.

4 / 5

Distinctiveness Conflict Risk

"Knows paper sidecars" and "claim/evidence analysis" establish a clear niche with distinct triggers, but "Search academic literature" carries minor overlap risk with a general search skill, fitting anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

16

/

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

first-fluke/oh-my-agent

Path

.agents/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.