sop-factory

Turn rough workflows into standard operating procedures with roles, inputs, outputs, checkpoints, and exception handling.

Security Scan

The skill's files, instructions, and minimal python requirement are coherent with its SOP-generation purpose; nothing requests unrelated credentials, remote downloads, or privileged persistence.

Purpose & Capability

Name/description align with the included resources and a small local helper script. Declared dependency (python3) is appropriate for the bundled script and no unrelated binaries or credentials are requested.

Instruction Scope

SKILL.md stays within scope (structure SOPs, use local template and helper). The bundled script is benign but minimal — it only writes an empty SOP-outline JSON skeleton to a user-specified path, so the agent/skill generates substantive content in conversation rather than via the script. This is not a security issue but may be surprising if a user expects the script to produce a full SOP automatically.

Install Mechanism

There is no install spec; the skill is instruction-only with an auditable local script. No remote downloads, package installs, or extraction steps are present.

Credentials

No environment variables, credentials, or config paths are requested. The skill does not declare or use secrets and therefore does not ask for disproportionate access.

Persistence & Privilege

Skill is not forced-always; it does not request system-wide changes or modify other skills. The only file action is the helper script writing a user-specified output file (potential overwrite risk if path is reused), which is within expected scope.

Assessment

This skill appears coherent and locally auditable: it only needs python3 and the included template/script. Before installing or running, you may: (1) inspect scripts/sop_outline_builder.py (it only emits an empty JSON skeleton to the provided --out path), (2) run the smoke test or invoke python3 scripts/sop_outline_builder.py --help to confirm behavior, and (3) when using the skill in an agent session, confirm any file paths the agent will write to (to avoid accidental overwrites). Note that the agent may still act autonomously per platform defaults — ensure you trust any agent prompts that request file writes or access to local data.

Purpose

Turn rough workflows into standard operating procedures with roles, inputs, outputs, checkpoints, and exception handling.

Trigger phrases

• 做 SOP
• turn this workflow into an SOP
• 流程文档化
• 标准作业流程
• 交接文档

Ask for these inputs

• rough workflow
• roles
• tools used
• quality bar
• exception cases

Workflow

1. Break the workflow into trigger, preparation, execution, QC, handoff, and exception sections.
2. Use the SOP template resource to ensure consistency.
3. Add checkpoints, examples, and escalation rules.
4. Return both a quick-start SOP and a formal version.
5. Highlight where screenshots or forms should be attached.

Output contract

• SOP draft
• quick-start version
• roles matrix
• exceptions appendix

Files in this skill

• Script: {baseDir}/scripts/sop_outline_builder.py
• Resource: {baseDir}/resources/sop_template.md

Operating rules

• Be concrete and action-oriented.
• Prefer preview / draft / simulation mode before destructive changes.
• If information is missing, ask only for the minimum needed to proceed.
• Never fabricate metrics, legal certainty, receipts, credentials, or evidence.
• Keep assumptions explicit.

Suggested prompts

• 做 SOP
• turn this workflow into an SOP
• 流程文档化

Use of script and resources

Use the bundled script when it helps the user produce a structured file, manifest, CSV, or first-pass draft. Use the resource file as the default schema, checklist, or preset when the user does not provide one.

Boundaries

• This skill supports planning, structuring, and first-pass artifacts.
• It should not claim that files were modified, messages were sent, or legal/financial decisions were finalized unless the user actually performed those actions.

Compatibility notes

• Directory-based AgentSkills/OpenClaw skill.
• Runtime dependency declared through metadata.openclaw.requires.
• Helper script is local and auditable: scripts/sop_outline_builder.py.
• Bundled resource is local and referenced by the instructions: resources/sop_template.md.