Conciseness

Lean and dense throughout — numeric rules ('Overlap length 15–40 bp', 'Overlap Tm ≈ 48–65 °C'), tool outputs, and enzyme sites with no conceptual padding about what cloning is. Not a 5 because 'Step 4 — Gotchas' re-states rules already given in Steps 1–2 (internal Type IIS sites, non-unique overlaps, repeats/secondary structure, Tm imbalance), a redundancy that could be trimmed.

Actionability

Three fully executable `tu run` commands with realistic JSON payloads and expected return fields, plus concrete decision guidance — this is near copy-paste ready. Not a 5 because Step 3 cites `scripts/cloning_qc.py` without any invocation example; the CLI syntax exists only in the script's docstring, so the QC step is not executable as written in the body.

Workflow Clarity

Clear Step 0–4 sequence (pick method → design → QC → gotchas checklist) with an explicit validation gate ('QC before ordering', PASS/WARN screening) and a genuine feedback loop with error diagnosis: 'If the assembly reports that the fragments do not chain, digest the inputs individually with DNA_virtual_digest... Getting 1 means the enzyme name or circular is wrong — not that the plasmid lacks sites.' This matches the level-5 anchor (explicit validation, error-recovery loop, checklist); the level-4 anchor's 'minor validation gaps' does not apply.

Progressive Disclosure

Well-sectioned body with a real bundle script correctly placed at `scripts/cloning_qc.py` (verified present and matching the described checks), and hand-offs to sibling skills. Not a 5 because everything else is inlined — the enzyme-site table, overhang-set guidance, and QC details have no one-level-deep reference files, so structure is good but not split for progressive loading; a 3 would require buried references or misplaced bulk content, which is not the case.

Specificity

Lists multiple concrete, comprehensive actions — 'overlap design for seamless multi-fragment joining', 'Type IIS / BsaI / BbsI / Esp3I / BsmBI / SapI design with unique 4-bp fusion overhangs', 'digest them, join the fragments by their overhangs, and identify features of the product (expressed ORF, gRNA spacer and its target gene)' — matching the level-5 anchor. Docked one point per the voice guideline: the trigger clause 'Use when you need to plan...' is second person rather than the third-person voice ('Use when the user needs to...') used by the anchor examples.

Completeness

Explicitly answers both what (both directions: DESIGN overlaps/overhangs; ANALYSIS 'digest them, join the fragments by their overhangs, and identify features of the product') and when ('Use when you need to plan how to join DNA fragments into a construct, design assembly overlaps/overhangs, decide between cloning methods, or determine the product of a stated Gibson/Golden Gate reaction'). Clear what + clear when with concrete trigger phrases matches the level-5 anchor exactly.

Trigger Term Quality

Comprehensive natural terms a user would actually say: 'Molecular cloning', 'Gibson Assembly', 'Golden Gate Assembly', 'join DNA fragments into a construct', 'design assembly overlaps/overhangs', 'digest', 'plasmid', 'gRNA', plus concrete enzyme names (BsaI, Esp3I, BsmBI). Not a 4 because synonyms are well covered ('cloning methods', 'construct', 'join') and file extensions are not applicable to this domain.

Distinctiveness Conflict Risk

Clear niche (Gibson/Golden Gate assembly design and product analysis) with distinct triggers, and it explicitly delimits the boundary with a sibling skill: 'For PCR primers to generate the fragments, see tooluniverse-primer-design.' This removes the main overlap risk with the adjacent primer-design skill, matching the level-5 anchor (clear niche, minimal conflict).