CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

preclinical-pkpd-analyst

Use preclinical pkpd analyst for data analysis workflows that need structured execution, explicit assumptions, and clear output boundaries.

Quality

54%

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/Data Analysis/preclinical-pkpd-analyst/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 contains a serviceable workflow, error-handling, and response-template core, but is buried under generic template boilerplate and undermined by inaccurate references (missing requirements.txt, nonexistent CONFIG block, dated example path, forward self-references). The actual analysis procedure — input format, CLI flags, and how to interpret output — is never concretely documented.

Suggestions

Document the real script usage: input CSV format (time,concentration columns), the --data and --demo flags, and expected output parameters; remove the 'in-file CONFIG block' instruction, which does not match scripts/main.py.

Cut the boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) and merge the duplicated Quick Check / Audit-Ready Commands blocks; they repeat the same two commands and add token cost without operational value.

Fix broken references: the missing requirements.txt (either add it or drop the dependency declarations), the non-reproducible '20260318/scientific-skills/...' example path, and the forward-pointing 'See ## Prerequisites/Workflow above' lines that appear before those sections.

DimensionReasoningScore

Conciseness

The body is noticeably padded: boilerplate sections (Risk Assessment table, Security Checklist, Evaluation Criteria, Lifecycle Status with a 'Next Review Date' of 2026-03-06) add nothing Claude needs, the same py_compile/--help commands are repeated across 'Quick Check' and 'Audit-Ready Commands', and 'When to Use' restates the frontmatter description verbatim twice. This matches anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections'); not 1 because genuine operational content (Parameters, Returns, Workflow, Error Handling) is also present.

2 / 5

Actionability

Some concrete commands exist and the referenced script is real ('python -m py_compile scripts/main.py', 'python scripts/main.py --help'), but the key execution details are missing: the input file format (CSV with time,concentration columns), the actual CLI flags (--data, --demo), and the 'Example Usage' path ('20260318/scientific-skills/...') is not reproducible. The instruction to 'Edit the in-file CONFIG block' points to a block that does not exist in scripts/main.py. This matches anchor 3 ('some concrete guidance but incomplete; missing key details'); not 4 because a user could not run a real analysis from the body alone.

3 / 5

Workflow Clarity

The Workflow section lists a clear 5-step sequence with scope validation ('stop early if the task would require unsupported assumptions') and a fallback path ('If execution fails or inputs are incomplete, switch to the fallback path'), plus a pre-execution parse check. However, there is no validation of computed results, the steps are process-general rather than PK-specific, and the section cross-references ('See ## Workflow above', 'See ## Prerequisites above') appear before the sections they cite. This matches anchor 3 ('sequence present but checkpoints missing or implicit'); not 4 because the verification gaps and broken references undermine the checkpoints.

3 / 5

Progressive Disclosure

Structure exists with clear section headers and a real, correctly referenced script (scripts/main.py), but organization is loose: 'requirements.txt' is cited as declaring dependencies yet does not exist in the bundle, self-references point the wrong direction, and a large amount of boilerplate (risk tables, checklists, lifecycle metadata) is inlined that belongs in separate governance files or nowhere. This matches anchor 3 ('some structure but could be better organized; references present but not clearly signaled'); not 2 because the core script reference is real and navigation is possible.

3 / 5

Total

11

/

20

Passed

Description

45%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 circular and generic: it defines the skill by its own name and by process qualities (structured execution, explicit assumptions, output boundaries) rather than by what it actually does — noncompartmental PK parameter calculation. Trigger terms miss the natural vocabulary of the domain (pharmacokinetics, AUC, concentration-time data).

Suggestions

Replace the circular opening with concrete actions, e.g. 'Calculate noncompartmental PK parameters (AUC, Cmax, Tmax, t1/2, clearance, volume) from preclinical concentration-time data via scripts/main.py.'

Add natural trigger phrases a researcher would actually say: 'Use when analyzing pharmacokinetic / concentration-time data, running noncompartmental analysis (NCA), or selecting doses for IND-enabling studies.'

Drop the generic 'data analysis workflows that need structured execution, explicit assumptions, and clear output boundaries' trigger, which matches nearly any data-analysis skill and creates conflict risk.

DimensionReasoningScore

Specificity

The description names the domain ("preclinical pkpd analyst", "data analysis workflows") but describes no concrete PK actions — "structured execution, explicit assumptions, and clear output boundaries" are generic process qualities, not capabilities like calculating AUC or half-life. It matches anchor 2 ('names the domain but actions are minimal or generic'); it is not 3 because there is no concrete action stated, and not 1 because the domain is at least named.

2 / 5

Completeness

A 'when'-equivalent clause exists ("for data analysis workflows that need structured execution, explicit assumptions, and clear output boundaries"), so the missing-'Use when' cap of 3 applies, but the 'what' is circular — the skill is explained only in terms of its own name, never what it computes. It sits between anchor 2 (vague what, weak when) and anchor 3 (clear what, weak when); it earns 3 only because the trigger clause is explicit, and cannot reach 4 because the 'what' never states a concrete capability.

3 / 5

Trigger Term Quality

Some relevant keywords are present ("preclinical", "pkpd", "data analysis") that a PK researcher might use, but common natural variations are missing: "pharmacokinetics", "concentration-time data", "AUC", "noncompartmental analysis", "dose selection". This matches anchor 3 ('some relevant keywords but missing common variations or synonyms'); not 4 because users would rarely phrase a need as 'workflows that need structured execution, explicit assumptions, and clear output boundaries'.

3 / 5

Distinctiveness Conflict Risk

The 'preclinical pkpd' domain is fairly niche, but the trigger conditions ('data analysis workflows that need structured execution... clear output boundaries') would match virtually any structured data-analysis skill, creating overlap risk with generic analysis skills. This matches anchor 3 ('somewhat specific but could still overlap with similar skills'); not 4 because the behavioral triggers are generic process language rather than domain-specific cues.

3 / 5

Total

11

/

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/Data Analysis/preclinical-pkpd-analyst/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.