CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

journal-impact-factor-trend

Show journal impact factor and quartile trends over 5 years.

Quality

63%

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 ./scientific-skills/Evidence Insight/journal-impact-factor-trend/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 has a genuinely executable core — verified commands, an accurate parameter table, real bundle files, and explicit error-handling/fallback guidance — but it is buried under generic template scaffolding that triples the token cost without adding task-specific value. The workflow and structure are passable but abstract and repetitive rather than integrated.

Suggestions

Delete the template boilerplate sections (Key Features, Dependencies, Implementation Details, Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Response Template) and the circular 'See ## X above' cross-references; keep Usage, Parameters, Output, Workflow, Error Handling, and References.

Remove the hard-coded 'cd "20260318/scientific-skills/Evidence Insight/journal-impact-factor-trend"' path and the 'Edit the in-file CONFIG block' step, which does not match the script's argparse interface; consolidate the repeated py_compile/--help commands into one validation block.

Integrate validation into the Workflow as concrete checkpoints (compile check before execution, verify the generated trend table after running) instead of abstract process steps, especially for the batch --journal-list path.

DimensionReasoningScore

Conciseness

The ~190-line body is roughly 70% template boilerplate: 'Key Features' restates the description, the compile/--help commands appear three times (Quick Check, Audit-Ready Commands, Example Usage), and sections like Risk Assessment, Security Checklist, Evaluation Criteria, and Lifecycle Status ('Next Review Date: 2026-03-06', now a past date) add no task-specific value. It matches 'several unnecessary padded sections' rather than the concept-explanation padding of anchor 1, and exceeds the 'some trimming' of anchor 3.

2 / 5

Actionability

Commands are concrete and match the actual script interface ('python -m py_compile scripts/main.py', 'python scripts/main.py --journal "Nature Medicine"'), with a complete parameter table verified against main.py's argparse flags. Falls short of anchor 5 due to the hard-coded non-portable path 'cd "20260318/scientific-skills/Evidence Insight/journal-impact-factor-trend"' and the inaccurate step 'Edit the in-file CONFIG block' (the script uses argparse, not a CONFIG block).

4 / 5

Workflow Clarity

The 5-step Workflow is generic process boilerplate ('Confirm the user objective...', 'Validate that the request matches the documented scope') with checkpoints (compile check, fallback path) scattered in other sections rather than sequenced; there is no output-verification step. The batch-oriented --journal-list operation with no output validation also caps this dimension at 3.

3 / 5

Progressive Disclosure

Bundle structure is sound: references/audit-reference.md exists, is one level deep, and is clearly signaled in a References section, and scripts/main.py is the executable surface. However, the body inlines ~10 boilerplate sections and confuses navigation with circular pointers ('See ## Prerequisites above', 'See ## Usage above', 'See ## Workflow above') — organization gaps exceed the 'minor' of anchor 4, placing it between anchors 3 and 4.

3 / 5

Total

12

/

20

Passed

Description

61%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 is concise, specific, and clearly rooted in a well-defined domain with natural trigger terms. Its main deficiency is the absence of any 'when to use' guidance, which both caps completeness and weakens its distinctiveness against related skills.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks about a journal's impact factor history, quartile changes, or whether a journal is rising or declining.'

Include common synonyms such as JCR, Journal Citation Reports, or journal ranking so the description matches how users actually phrase these requests.

State the key output — a 5-year trend table with rising/stable/declining classification — to broaden action coverage beyond the single verb 'show'.

DimensionReasoningScore

Specificity

'Show journal impact factor and quartile trends over 5 years' names the domain and two concrete metrics (impact factor, quartile) with a bounded time window, matching 'names domain and 1-2 concrete actions, but not comprehensive'. It is not anchor 4 because there is only one action verb — the body's richer outcomes (trend table, rising/declining classification) are not stated in the description.

3 / 5

Completeness

The description clearly answers 'what' (show IF and quartile trends over 5 years) but contains no 'Use when...' or equivalent trigger clause, which the judging guidelines cap at 3. This exactly matches anchor 3 ('clear what but when is missing'), not 4 which requires both.

3 / 5

Trigger Term Quality

Terms 'journal', 'impact factor', 'quartile', and 'trends' are precisely what a user would naturally say, matching 'good keyword coverage; a few natural terms missing'. It falls short of anchor 5 because common synonyms and variations such as 'JCR', 'Journal Citation Reports', 'journal ranking', and 'IF' are absent, and short of nothing below 4 since coverage goes beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The impact-factor/quartile-trend niche is specific and unlikely to misfire against unrelated skills, matching 'mostly distinct; minor overlap risk with closely related skills'. It is not anchor 5 because without trigger guidance it could overlap with sibling bibliometric or journal-selection skills in the same package.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/journal-impact-factor-trend/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.