CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conflict-of-interest-checker

Check for co-authorship and institutional conflicts between authors and suggested reviewers to support peer review integrity. Coauthorship and institutional conflict detection supported.

Quality

59%

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/conflict-of-interest-checker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 is genuinely executable — concrete commands, a parameter table, CSV format, sample output, and explicit error-handling paths — but it is padded with four overlapping generic process sections, and its documented script behavior is stale: the 'known NameError bug' is already fixed while the actual --institution flag goes undocumented, producing misleading guidance.

Suggestions

Update the script documentation to match the bundled code: remove the stale NameError-bug warning and Claude Direct Path workaround for check_institutional_conflict(), and document the existing --institution flag in the Parameters table.

Consolidate the four overlapping generic sections ('Workflow', 'Stress-Case Rules', 'Output Requirements', 'Response Template') into one short checklist, cutting ~40 lines of boilerplate.

Rewrite the Workflow section as the actual operational sequence (validate inputs -> run script with --publications when available -> interpret report -> report assumptions and demo-data fallback) with explicit checkpoints instead of generic meta-steps.

DimensionReasoningScore

Conciseness

The core usage content (commands, parameters, CSV format, example output) is tight, but roughly 40 of 147 lines are generic process scaffolding ('Workflow', 'Stress-Case Rules', 'Output Requirements', 'Response Template') with heavy mutual overlap — several padded sections that Claude does not need spelled out, matching the level-2 anchor.

2 / 5

Actionability

Commands are copy-paste ready, but key details are wrong or missing: the claimed NameError bug in check_institutional_conflict() is stale (the bundled script is fixed and exposes an undocumented --institution flag), so the skill redirects Claude away from a working script path to a manual workaround, and the parameter table omits a real CLI option.

3 / 5

Workflow Clarity

A numbered sequence exists, but the 'Workflow' section is generic meta-process ('Confirm the user objective, required inputs, and non-negotiable constraints') rather than the operational run-check-interpret sequence; real validation checkpoints (compile check, error handling, fallbacks) are spread across sections and left implicit.

3 / 5

Progressive Disclosure

The body is well-sectioned with clear headers, the sole bundle reference (scripts/main.py) is real and correctly linked, and no bulky reference material is inlined; the main gap is boilerplate sections that belong (if anywhere) in a condensed checklist rather than four overlapping blocks.

4 / 5

Total

12

/

20

Passed

Description

53%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 clearly states what the skill does within a well-defined niche, but it lacks any 'when to use' trigger guidance and misses natural user phrasings like "conflict of interest". A redundant second sentence adds padding without adding information.

Suggestions

Replace the redundant second sentence with a 'Use when...' clause, e.g., 'Use when screening suggested reviewers for a journal submission, grant panel, or whenever conflict-of-interest checking between authors and reviewers is requested.'

Add natural trigger synonyms such as 'conflict of interest', 'COI', and 'reviewer recusal' so the description matches phrases users actually say.

Mention the publication-records (CSV) input in the description so users know coauthorship detection depends on shared publication data, not just name lists.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("Check for co-authorship and institutional conflicts between authors and suggested reviewers"), but the second sentence ("Coauthorship and institutional conflict detection supported") merely restates the first rather than adding capability coverage, so it does not reach the 'several specific actions' of level 4.

3 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance — "to support peer review integrity" only weakly implies when to use the skill, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "co-authorship", "institutional conflicts", "peer review", and "reviewers" are present, but common variations users would naturally say — "conflict of interest", "COI", "reviewer recusal/selection" — are missing, matching the 'some relevant keywords but missing synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

A clearly stated peer-review conflict-checking niche that is mostly distinct from other skills, though terms like "conflicts" and "peer review" create minor overlap risk with adjacent manuscript-review and ethics-screening skills.

4 / 5

Total

13

/

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/conflict-of-interest-checker/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.