CtrlK
BlogDocsLog inGet started
Tessl Logo

survival-analysis-km

Kaplan-Meier survival analysis with log-rank tests, Cox regression, and publication-ready survival curves for clinical and biological research.

77

Quality

72%

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/Data analysis/survival-analysis-km/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description excels at specificity and distinctiveness by naming precise statistical methods (Kaplan-Meier, Cox regression, log-rank tests) that create a clear niche. However, it lacks an explicit 'Use when...' clause which caps completeness, and could benefit from additional natural trigger terms that users might employ when requesting survival analysis.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when analyzing time-to-event data, survival outcomes, patient follow-up, or censored observations'

Include additional natural keywords users might say: 'time-to-event', 'hazard ratio', 'survival data', 'censored data', 'mortality analysis'

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Kaplan-Meier survival analysis', 'log-rank tests', 'Cox regression', and 'publication-ready survival curves'. These are precise statistical methods, not vague language.

3 / 3

Completeness

Clearly answers 'what' with specific statistical methods and outputs, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through domain context ('clinical and biological research').

2 / 3

Trigger Term Quality

Includes domain-specific terms like 'Kaplan-Meier', 'survival analysis', 'Cox regression', 'log-rank tests' that experts would use, but missing common variations users might say like 'time-to-event', 'hazard ratio', 'survival data', or 'censored data'.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive with specific statistical methodology (Kaplan-Meier, Cox regression, log-rank) that clearly separates it from general statistics or other analysis skills. Unlikely to conflict with other skills.

3 / 3

Total

10

/

12

Passed

Implementation

77%

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

This is a well-structured survival analysis skill with strong actionability and workflow clarity. The executable examples, parameter tables, and fallback handling are excellent. However, the content could be more concise by removing redundant installation instructions and consolidating the response template guidance, and could benefit from splitting detailed reference material into separate files.

Suggestions

Remove redundant lifelines installation mentions (appears in Quick Check, Note, Fallback Template, and Prerequisites) - consolidate to Prerequisites section only

Consider moving the detailed Response Template and Output Requirements sections to a separate REFERENCE.md file, keeping only a brief mention in the main skill

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy (lifelines installation mentioned multiple times, response template structure is verbose). The statistical methods section is appropriately concise, but the workflow and output requirements sections could be tightened.

2 / 3

Actionability

Provides fully executable bash commands, clear parameter tables, concrete CSV input format examples, and specific output file descriptions. The usage example is copy-paste ready with realistic parameter names.

3 / 3

Workflow Clarity

Clear 6-step workflow with explicit validation checkpoints, conditional logic for missing group columns, and a well-defined fallback template for error scenarios. High-risk scenarios requiring review are explicitly enumerated.

3 / 3

Progressive Disclosure

Content is well-organized with clear sections, but everything is in a single file. The skill references scripts/main.py and requirements.txt but doesn't link to separate documentation for advanced features or detailed API reference that could reduce the main file length.

2 / 3

Total

10

/

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.