CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

open-access-scout

Use when finding open access journals, checking journal policies, or identifying predatory publishers. Helps researchers locate legitimate open access venues and avoid publication scams.

Quality

70%

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 ./scientific-skills/Evidence Insight/open-access-scout/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 body is dominated by duplicated generic boilerplate rather than the skill's actual domain workflow, and its most concrete-looking code examples do not match the bundled script's real API or file paths, so a user following them hits errors. The single reference is properly linked but thin, and the promising domain-specific sections (journal search, predatory checks) are undermined by non-executable examples.

Suggestions

Fix the code examples to match the actual bundled script: scripts/main.py provides OpenAccessScout.search_open_access(doi, title, authors) and a --doi/--title/--authors/--list-sources CLI — replace find_journals, assess_journal, compare_apc, the `scripts.oa_scout` import, and the `scripts/oa_scout.py --search ... --max-apc` command with real usage, or implement those methods in the script.

Cut the duplicated boilerplate: merge Error Handling with Failure Handling and Output Requirements with Output Contract/Response Template into one short section each, and remove the pasted description from the When to Use bullet — this would remove well over half the body's tokens without losing domain information.

Rework the Workflow into the concrete domain sequence (run the quick check, search for OA versions, review source/license results, apply the predatory warning-signs list, report with assumptions and limits) with the py_compile and fallback checkpoints attached to specific steps instead of abstract meta-steps.

DimensionReasoningScore

Conciseness

Roughly two-thirds of the 189-line body is generic process boilerplate ("Output Requirements", "Error Handling", "Input Validation", "Response Template", "When Not to Use", "Required Inputs", "Output Contract", "Failure Handling", "User Checkpoints", "Quick Validation") with heavy duplication — Error Handling vs Failure Handling and Output Requirements vs Output Contract vs Response Template repeat the same guidance. The "When to Use" bullet also awkwardly pastes the description ("the task needs Use when finding open access journals..."), matching the noticeably-verbose anchor with several padded sections.

2 / 5

Actionability

The Quick Start and Core Capabilities code blocks look copy-paste ready but are fabricated against the actual bundle: scripts/main.py exposes only search_open_access(doi, title, authors), print_results, and a --list-sources/--doi/--title/--authors CLI, not find_journals, search(keywords, filters), assess_journal, or compare_apc. The import path `from scripts.oa_scout import ...` and CLI `python scripts/oa_scout.py --search ... --max-apc 2000` reference a nonexistent file and undefined flags, so the concrete-looking guidance is not executable as written — matching the incomplete-guidance anchor rather than the mostly-executable anchor.

3 / 5

Workflow Clarity

The Workflow section lists a sequence with a fallback step and the Quick Check (py_compile) provides a pre-execution checkpoint, but the five steps are abstract meta-process ("Confirm the user objective...", "Return a structured result...") rather than the concrete domain workflow (search journals, assess publisher, compare APC), and no step ties to an actual runnable command from the bundled script. The sequence is present but checkpoints are implicit and disconnected from real operations; the destructive/batch cap does not apply since this skill is neither.

3 / 5

Progressive Disclosure

The one bundled reference (references/audit-reference.md) is real, one level deep, and clearly signaled in a References section, but it only restates scope and audit commands. Meanwhile a large volume of generic policy content that belongs in a reference (or nowhere) is inlined in SKILL.md, and body references to scripts/oa_scout.py / scripts.oa_scout point to files that do not exist in the bundle, weakening navigation. This sits between the some-structure and good-structure anchors.

3 / 5

Total

11

/

20

Passed

Description

87%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 description that explicitly covers both what the skill does and when to use it, in third person, with concrete domain-specific trigger phrases. The only weaknesses are minor: a few natural synonyms (APC/article processing charges) and capabilities (APC comparison) are missing from the trigger and action coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "finding open access journals, checking journal policies, or identifying predatory publishers" plus "locate legitimate open access venues and avoid publication scams" — which matches the anchor for several specific actions with minor gaps. It is not a 5 because core capabilities shown in the body (e.g., APC comparison, journal search filtering) are absent from the description, leaving minor coverage gaps.

4 / 5

Completeness

Both what and when are explicit: "Helps researchers locate legitimate open access venues and avoid publication scams" states the what, and "Use when finding open access journals, checking journal policies, or identifying predatory publishers" gives concrete when-triggers, matching the anchor for clearly and explicitly answering both. Uses third person voice, so no voice penalty applies.

5 / 5

Trigger Term Quality

Natural phrases a researcher would actually say are present: "open access journals", "journal policies", "predatory publishers", "publication scams", "open access venues". It is not a 5 because common variations are missing (e.g., "article processing charges"/"APC", "where to publish", "journal legitimacy", "DOAJ"), while exceeding anchor 3 since multiple distinct natural trigger phrases are covered.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (open access publishing venue vetting and predatory publisher avoidance) with distinct triggers that no adjacent skill (e.g., PDF extraction, literature search) would claim, matching the clear-niche anchor. It is not below 5 because the trigger terms are specific enough to avoid overlap with generic research-assistant skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/open-access-scout/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.