CtrlK
BlogDocsLog inGet started
Tessl Logo

postdoc-fellowship-matcher

Match postdoc applicants to eligible fellowships based on nationality and research area

44

Quality

31%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./scientific-skills/Academic Writing/postdoc-fellowship-matcher/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

40%

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 identifies a clear, distinctive niche (postdoc fellowship matching) but suffers from missing explicit trigger guidance and limited action specificity. It tells Claude what the skill does at a high level but not when to use it, which is critical for skill selection among many options.

Suggestions

Add a 'Use when...' clause with trigger terms like 'fellowship eligibility', 'postdoc funding', 'which fellowships can I apply for', 'postdoctoral opportunities'

Expand trigger terms to include variations: 'postdoctoral', 'grants', 'funding', 'eligibility requirements', 'citizenship requirements'

Specify additional concrete actions beyond 'match' such as 'filters by eligibility criteria', 'lists qualifying programs', 'checks nationality requirements'

DimensionReasoningScore

Specificity

Names the domain (postdoc applicants, fellowships) and the core action (match), but only mentions two criteria (nationality, research area) without detailing what 'matching' entails or additional capabilities.

2 / 3

Completeness

Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.

1 / 3

Trigger Term Quality

Includes relevant terms like 'postdoc', 'applicants', 'fellowships', 'nationality', 'research area' that users might say, but missing common variations like 'postdoctoral', 'funding opportunities', 'grants', 'eligibility'.

2 / 3

Distinctiveness Conflict Risk

Very specific niche combining postdoc applicants, fellowships, nationality, and research area matching - unlikely to conflict with other skills due to this unique combination.

3 / 3

Total

8

/

12

Passed

Implementation

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a placeholder with extensive boilerplate but minimal actionable content. It describes what a fellowship matcher should do but provides no implementation, matching criteria, fellowship eligibility rules, or workflow guidance. Claude cannot execute this skill without substantial additional information about how to actually match applicants to fellowships.

Suggestions

Add concrete fellowship eligibility criteria (nationality requirements, years-post-PhD limits, field restrictions) for each fellowship in the database

Provide the actual matching logic or algorithm, either as executable Python code or clear decision rules

Remove or drastically reduce boilerplate sections (risk assessment, security checklist, lifecycle status, evaluation criteria) that don't help Claude perform the task

Add example input/output showing what a successful match looks like with specific fellowship requirements

DimensionReasoningScore

Conciseness

The skill includes substantial boilerplate (risk assessment tables, security checklists, evaluation criteria, lifecycle status) that adds little value for Claude's task execution. The core matching functionality could be conveyed in far fewer tokens.

2 / 3

Actionability

The skill provides only a CLI invocation example but no actual implementation, matching logic, or executable code. The fellowship database is just a list of names with no filtering criteria, eligibility rules, or data structure.

1 / 3

Workflow Clarity

There is no workflow described - just a single command invocation. No steps for how matching works, no validation of results, no guidance on what to do with output or how to verify correctness of matches.

1 / 3

Progressive Disclosure

Content is organized into sections, but the structure is poor - boilerplate sections (risk assessment, security checklist, lifecycle) dominate while actual skill content is minimal. No references to detailed fellowship criteria or matching logic documentation.

2 / 3

Total

6

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
aipoch/medical-research-skills
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.