sanger-chromatogram-qa

Use sanger chromatogram qa for data analysis workflows that need structured execution, explicit assumptions, and clear output boundaries.

Quality

39%

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/sanger-chromatogram-qa/SKILL.md

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 content is structurally complete with executable commands, a numbered workflow, and a real accompanying script, but it is weighed down by repetitive boilerplate, generic process filler, and undefined parameter stubs. The QA-specific guidance is thin compared to the volume of templated meta-instructions.

Suggestions

Delete the duplicated description echoes in 'When to Use' and 'Key Features' and the empty cross-references ('See ## Prerequisites above'), which repeat what is already in the frontmatter.

Add a validation checkpoint to the workflow (e.g. confirm the trace parses and total_bases > 0 before reporting) so the batch file-processing flow meets the validation standard.

Replace the stub parameter list ('ab1_file: Chromatogram', 'expected_seq: Reference') with actual CLI flags from the script (--ab1, --reference/-r, --demo) and one runnable non-demo example.

Dimension	Reasoning	Score
Conciseness	The body is padded with repetitive boilerplate (the full description is quoted verbatim in 'When to Use' and again in 'Key Features', plus repeated cross-references like 'See ## Prerequisites above') that explains generic process concepts Claude already knows.	2 / 5
Actionability	Concrete executable commands are present ('python -m py_compile scripts/main.py', 'python scripts/main.py --help') and the bundle script exists, but the core QA workflow itself has no runnable example beyond --demo and the listed parameters are undefined stubs ('ab1_file: Chromatogram').	3 / 5
Workflow Clarity	A numbered Workflow with five steps and a Quick Check is provided, and the script reads input files and writes outputs (a batch/file operation), but there is no validation checkpoint verifying the trace is valid or confirming outputs before returning — only generic 'stop early' guidance.	3 / 5
Progressive Disclosure	The body is organized into clear sections and the single bundle file (scripts/main.py) is correctly referenced and present, but most content is generic template material inlined in SKILL.md rather than split out, and no reference files exist for the domain detail.	3 / 5
	Total	11 / 20 Passed

Description

36%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 largely a rephrasing of the skill name padded with abstract workflow meta-language, lacking both concrete capabilities and an explicit trigger clause. It names the domain but does not describe what it actually does or when to use it.

Suggestions

Rewrite in third person with concrete actions, e.g. 'Quality-checks Sanger sequencing chromatograms: computes per-base quality scores, detects mixed/heterozygous peaks, and confirms variants against a reference sequence.'

Add an explicit trigger clause: 'Use when validating Sanger sequencing traces (.ab1), confirming clones, or checking for heterozygous variants.'

Remove the generic 'structured execution, explicit assumptions, and clear output boundaries' language, which applies to any analysis skill and dilutes distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ('sanger chromatogram qa') but the only 'action' stated is the generic 'data analysis workflows', echoing the skill name rather than listing concrete QA actions like peak detection or variant confirmation.	2 / 5
Completeness	It states a vague 'what' ('data analysis workflows that need structured execution...') with no 'Use when...' trigger clause, so the 'when' is entirely missing.	2 / 5
Trigger Term Quality	'sanger chromatogram qa' and 'chromatogram' are relevant domain keywords a user might say, but common natural synonyms and file extensions (e.g. 'sequencing trace', '.ab1', 'heterozygous peak') are absent.	3 / 5
Distinctiveness Conflict Risk	The narrow 'sanger chromatogram qa' niche is somewhat distinct, but the generic 'data analysis workflows that need structured execution, explicit assumptions, and clear output boundaries' framing could overlap with almost any analytical skill.	3 / 5
	Total	10 / 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/sanger-chromatogram-qa/SKILL.md
Commit: f5ef65b

Reviewed: ~7 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.