table-1-generator-advanced

Generate publication-ready baseline characteristics tables (Table 1) for clinical research papers with automatic variable type detection, appropriate statistics (mean±SD, median[IQR, n(%)), group comparisons (t-test, chi-square), and APA formatting.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Data Analysis/table-1-generator-advanced/SKILL.md

Quality

Content

60%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 is actionable and the workflow is clearly sequenced with a checkpoint, but a large share of the document is meta-boilerplate that inflates token cost without aiding the task. Trimming those sections would materially improve conciseness.

Suggestions

Remove or collapse the meta-boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template) that do not advance Table 1 generation.

Drop the time-sensitive 'Next Review Date: 2026-03-06' from Lifecycle Status, or move it to a deprecated/maintenance section, as it penalizes conciseness.

Add a small validate→fix→retry loop (e.g., re-run py_compile after edits) to raise workflow clarity for the batch statistical computation.

Dimension	Reasoning	Score
Conciseness	The operational sections (Workflow, Usage, Parameters) are lean, but the body is padded with substantial meta-boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status with a time-sensitive 'Next Review Date: 2026-03-06', Output Requirements, Response Template) that does not help Claude generate Table 1.	2 / 5
Actionability	Provides concrete executable commands ('python scripts/main.py --data patients.csv --group treatment --output table1.csv') and a full parameters table, with only minor gaps such as no example using --vars or a sample output.	4 / 5
Workflow Clarity	The six-step Workflow is clearly sequenced with explicit Input/Output per step and a ⛔ checkpoint for borderline normality, but it lacks a full validate→fix→retry feedback loop for script execution itself.	4 / 5
Progressive Disclosure	Well-organized into clear sections with a real referenced bundle file (scripts/main.py) at one level deep and no nested references; minor gaps are the inlined meta sections that could be trimmed or separated.	4 / 5
	Total	14 / 20 Passed

Description

75%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 specific and well-targeted to a distinct clinical-research niche, but it omits an explicit 'Use when...' trigger clause, capping its completeness. Adding trigger guidance would raise the overall quality.

Suggestions

Append an explicit 'Use when...' clause to the description, e.g. 'Use when the user asks for a Table 1, baseline characteristics, or demographic summary table for a clinical research manuscript.'

Add synonyms such as 'demographic table' and 'summary statistics table' directly to the description to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Generate publication-ready baseline characteristics tables (Table 1)', 'automatic variable type detection', 'group comparisons (t-test, chi-square)', 'APA formatting' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Has a clear 'what' (generate Table 1 with the listed features) but no 'Use when...' clause or equivalent explicit trigger guidance in the description itself, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Table 1', 'baseline characteristics', 'clinical research') but omits common synonyms like 'demographic table' or 'summary statistics table' that appear only in the body, not the description.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (clinical-research Table 1 generation) with distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/table-1-generator-advanced/SKILL.md
Commit: f5ef65b

Reviewed: ~10 hours ago

Table of Contents

Discovery Implementation Validation

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.