Sop Architect

Automatically generates detailed Standard Operating Procedures (SOPs) for recurring digital tasks. Ideal for scaling agency operations or documenting interna...

Security Scan

The skill is internally consistent with its description: a small instruction-driven SOP generator plus a simple shell script that writes markdown files; no network access or credentials are requested.

Purpose & Capability

Name/description match the provided files. SKILL.md describes generating SOPs and the included script creates SOP markdown files from provided inputs — this is proportionate to the stated purpose.

Instruction Scope

Runtime instructions stay within the skill's purpose and only describe composing SOP content and saving it under SOPs/<task-name>.md. One implementation detail: scripts/generate_sop.sh writes files using the raw task name (spaces replaced with underscores) and does not sanitize path traversal segments (e.g., TASK_NAME='../foo' leads to SOPs/../foo.md which resolves outside the SOPs directory). This is a minor safety/overwrite risk but not evidence of malicious intent.

Install Mechanism

No install spec; instruction-only skill with a small helper script. Nothing is downloaded or executed from external URLs.

Credentials

No environment variables, credentials, or config paths are requested. SKILL.md suggests documenting 'access levels' in SOP content but does not request or access any secrets.

Persistence & Privilege

always is false and the skill does not request persistent privileges or modify agent-wide configuration. It writes files only under the working directory (with the minor path-traversal caveat noted).

Assessment

This skill appears to do what it says: it generates SOP markdown files and contains a small bash helper. No network calls or credentials are requested. Before installing, consider: 1) review or sanitize task names you pass to avoid accidental path traversal or file overwrite (the script does not sanitize '..' segments); 2) run the skill from a safe working directory or container so file writes cannot overwrite important files; 3) if you expect to use untrusted input for task names, modify the script to reject or sanitize non-alphanumeric characters. Otherwise the skill is coherent and low-risk.

Turn any complex task into a repeatable manual.

Workflow

1. Input Task: Describe the goal (e.g., "Monthly SEO Audit").
2. Deconstruct: Identify required tools, access levels, and prerequisites.
3. Step-by-Step: Generate 5-10 specific, numbered steps.
4. Failure Modes: Document what to do when things go wrong at each step.

Output Format

SOPs are saved to SOPs/<task-name>.md.

Benefits

• Reduces agent errors.
• Makes results consistent across different sessions.
• Easy to hand off to human team members.

Installation

clawhub install sop-architect