domains / families / science / protocol-standardization

protocol-standardization

separate

Standardize fragmented experimental steps into reproducible protocol documents when you need method organization, lab SOP drafting, or cross-operator reproducibility; missing parameters must be explicitly marked as "To be supplemented/Not provided".

When to use

• You have messy notes (chat logs, notebook fragments, bullet points) and need a formal, reproducible experimental protocol.
• You are preparing a lab SOP for standardization across multiple operators or sites.
• You need to convert exploratory/iterative experimental steps into a structured method for documentation or publication support.
• You are onboarding new team members and must clarify steps, parameters, and checkpoints without inventing missing information.
• You are auditing an existing method to identify missing critical parameters and quality-control points.

When not to use

• Do not proceed when required input files, identifiers, parameters, or context are missing — ask the user to provide them first.
• Do not assume capabilities beyond this skill's declared scope when the user requests external operations or inferences.
• Do not proceed without user confirmation when overwriting existing results, executing high-cost batch operations, or expanding task scope.

Skill page

Source