CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

population-gap-detector

Detects overlooked, underrepresented, weakly resolved, or poorly validated populations and subgroups within a biomedical research area so users can identify more precise and meaningful study populations. Always use this skill when the real question is not just what is under-studied, but which populations, strata, or subgroups are missing, thinly represented, superficially analyzed, pooled without resolution, or insufficiently validated in the current evidence base. Focus on meaningful subgroup gaps rather than generic calls for diversity.

Quality

80%

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 ./awesome-med-research-skills/Evidence Insight/population-gap-detector/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 content has excellent workflow structure — a clearly sequenced 8-step procedure, per-step reference integration, validation checkpoints, and a mandatory output format with a self-check risk review. Its main weakness is redundancy: the procedure, prohibitions, and quality criteria are each stated two to four times across overlapping sections, inflating token cost without adding guidance value.

Suggestions

Delete the "Core Function" section (it duplicates Decision Logic Steps 1-8 nearly verbatim) and merge "Sample Triggers" into the Input Validation examples.

Consolidate "This skill should not", "What This Skill Should Not Do", and the overlapping Hard Rules into a single list of prohibitions, and fold "Quality Standard" into it or drop it.

Add a short worked example (a few lines showing how one subgroup axis moves through Steps 3-7 to a ranked gap) to make the judgment-based steps like 'plausibly relevant' more concrete.

DimensionReasoningScore

Conciseness

The ~320-line body contains several padded, duplicative sections: "Core Function" items 1-8 restate "Decision Logic" Steps 1-8 almost verbatim; "Sample Triggers" repeats the Input Validation examples; and the prohibitions appear three times across "This skill should not", the 15 Hard Rules, and "What This Skill Should Not Do", with "Quality Standard" restating them again. This matches anchor 2 (noticeably verbose; several unnecessary or padded sections), not anchor 3, since the redundancy goes beyond occasional tightening.

2 / 5

Actionability

Concrete, specific instruction guidance throughout: 12 named population axes (Step 2), a 7-level coverage status scale (Step 3), 7 named gap types (Step 4), a ready-to-use out-of-scope redirect template, and a defined 10-section output structure A-J. For an instruction-only skill this is mostly executable guidance with a minor gap — no worked example of a finished report — matching anchor 4 rather than anchor 5.

4 / 5

Workflow Clarity

Steps 1-8 are clearly sequenced, each mapped to its reference module, with explicit checkpoints and recovery paths: the out-of-scope redirect-and-stop response, "Do not begin subgroup-gap detection before the topic unit is clear", the incomplete-output rule ("treated as incomplete" if a section skips its module), the 15-rule Hard Rules checklist, and the Section I Risk Review. This matches anchor 5 (clear sequence, explicit validation, feedback loops, checklist) better than anchor 4, which presumes missing checkpoints.

5 / 5

Progressive Disclosure

All 7 referenced files (population-axis-framework.md through output-section-guidance.md) exist in references/, are exactly one level deep, and each is explicitly signaled with its purpose and target output section (e.g., "references/subgroup-gap-typology.md → use when classifying the specific type of subgroup gap in Section D"). The body is an overview of procedure and output format with details correctly split into the bundle, matching anchor 5.

5 / 5

Total

16

/

20

Passed

Description

82%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 strong: explicit what-and-when structure, good natural trigger phrases, and clear differentiation from adjacent research-gap and diversity skills. Its main weakness is that it compresses the skill into a single "detects" action, underselling the audit/classify/rank/translate workflow that defines the skill's actual value.

Suggestions

Enumerate the core actions the skill performs (e.g., "audits subgroup coverage, classifies gap types, ranks the most defensible population gap") to raise specificity beyond a single 'detects' verb.

Add one or two natural user phrasings such as 'who is missing' or 'which patient groups are overlooked' to broaden trigger coverage.

Consider naming the output the user gets (a ranked next-step study population) so the 'what' states the deliverable, not just the activity.

DimensionReasoningScore

Specificity

"Detects overlooked, underrepresented, weakly resolved, or poorly validated populations and subgroups within a biomedical research area" names the domain and one concrete action in third person, but detection is the only concrete verb — the audit, classify, rank, and translate actions the skill actually performs are absent. This fits anchor 3 (domain plus 1-2 concrete actions), not anchor 4, which requires several listed specific actions.

3 / 5

Completeness

The "what" is explicit ("Detects overlooked, underrepresented, weakly resolved, or poorly validated populations and subgroups within a biomedical research area") and the "when" is an explicit "Always use this skill when" clause with concrete trigger content about missing, thinly represented, pooled, or insufficiently validated subgroups. Both are clearly answered with concrete trigger phrasing, matching anchor 5; anchor 4 would require a less explicit 'when'.

5 / 5

Trigger Term Quality

Natural phrases users would say are well covered: "which populations, strata, or subgroups are missing", "under-studied", "thinly represented", "superficially analyzed", "pooled without resolution", plus synonyms like underrepresented/overlooked. A few common variations (e.g., "health disparities", "who is missing") are missing, matching anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Focus on meaningful subgroup gaps rather than generic calls for diversity" and "not just what is under-studied" explicitly carve the niche apart from general research-gap and diversity skills, giving it distinct triggers and minimal conflict risk, matching anchor 5.

5 / 5

Total

17

/

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

awesome-med-research-skills/Evidence Insight/population-gap-detector/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.