CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

postdoc-fellowship-matcher

Filter and match postdoctoral fellowship opportunities based on applicant nationality, years since PhD, and research field from a curated database.

Quality

79%

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/Other/postdoc-fellowship-matcher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 highly actionable and well-structured, with executable commands that match the real bundle files, a validated workflow with error-recovery guidance, and clean one-level-deep progressive disclosure. The only real weakness is redundancy — the same rules for missing inputs, scope refusal, and output structure are restated across multiple sections.

Suggestions

Consolidate the missing-input rule into one place (e.g. Error Handling) and reference it from the Workflow instead of repeating it in Workflow step 5 and Input Validation.

Merge the out-of-scope guidance from When to Use, Scope Boundaries, and Input Validation into a single 'Scope and Refusals' section with the verbatim refusal message.

Unify Stress-Case Rules and Response Template into one output structure definition, keeping the compressed/simple-case allowance.

DimensionReasoningScore

Conciseness

The body uses efficient tables and commands with no padding about concepts Claude already knows, but instruction content is duplicated: missing-input handling appears nearly verbatim in Workflow step 5, Error Handling, and Input Validation; out-of-scope refusal is covered in When to Use, Workflow step 2, Scope Boundaries, and Input Validation; and output structure is defined twice (Stress-Case Rules vs. Response Template). This fits anchor 3 ('mostly efficient but could be tightened') better than anchor 2, since the redundancy is repetition of genuinely needed rules rather than filler explanation.

3 / 5

Actionability

Everything is copy-paste executable: 'python -m py_compile scripts/main.py' and 'python scripts/main.py --help' quick checks, two realistic invocations with flags matching the actual script, a parameter table, an alias-normalization table, and a verbatim out-of-scope response. This matches anchor 5 — specific examples covering the common cases.

5 / 5

Workflow Clarity

The 5-step workflow has explicit validation checkpoints (confirm applicant criteria, validate the request is in-scope, request only missing fields), and Error Handling adds a script-failure feedback path (report failure point, manual fallback) plus the Quick Check pre-flight. This is a read-only filtering skill so the destructive/batch cap does not apply, and the Stress-Case Rules/Response Template act as checklists, matching anchor 5.

5 / 5

Progressive Disclosure

SKILL.md is a lean overview with a one-line fellowship summary pointing to references/fellowships.md, which exists and is exactly one level deep and clearly signaled; the operational logic lives in scripts/main.py, which also exists. Content is appropriately split with easy navigation, matching anchor 5; anchor 4 would require organization gaps that are not present.

5 / 5

Total

18

/

20

Passed

Description

65%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 specific and unambiguous about what the skill does, with a distinctive niche and third-person voice. Its main gaps are the missing 'Use when...' trigger clause and sparse synonym coverage for common user phrasings like 'postdoc' or 'funding'.

Suggestions

Append a trigger clause, e.g. 'Use when a postdoc applicant asks to find, filter, or compare fellowship eligibility based on their profile.'

Add natural synonyms users would say — 'postdoc', 'funding', 'grant', 'fellowship eligibility' — to broaden trigger coverage.

Enumerate one or two more concrete actions (e.g. 'rank matches by eligibility and return deadlines') to move specificity beyond a single filter/match operation.

DimensionReasoningScore

Specificity

"Filter and match postdoctoral fellowship opportunities based on applicant nationality, years since PhD, and research field" names the domain and criteria, but 'filter' and 'match' are near-synonymous actions rather than a list of several distinct concrete operations. It fits anchor 3 (domain plus 1-2 concrete actions, not comprehensive) better than anchor 4, which expects several specific distinct actions.

3 / 5

Completeness

The 'what' is clearly stated (filtering/matching fellowships from a curated database by applicant criteria), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Anchor 4 requires both 'what' and 'when' to be present, which is not met.

3 / 5

Trigger Term Quality

Natural phrases like "postdoctoral fellowship opportunities", "years since PhD", "nationality", and "research field" give good keyword coverage a user would plausibly say. It falls short of anchor 5 only because common variations such as "postdoc", "funding", "grants", and "eligibility" are absent.

4 / 5

Distinctiveness Conflict Risk

Postdoc fellowship matching keyed on nationality, years-since-PhD, and research field is a clear niche with distinct criteria, so overlap with other skills is minimal. It is more specific than the anchor-4 example ('mostly distinct; minor overlap risk'), matching anchor 5.

5 / 5

Total

15

/

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/Other/postdoc-fellowship-matcher/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.