arklabshq/create-operational-sop
skills/create-operational-sop/SKILL.md
Generate validated operational SOPs for Ark ecosystem projects by testing commands before documenting them. Use when: user wants to create or audit SOPs for a project.
$ install --global
skillsauthnpx skillsauth add arklabshq/arkadian create-operational-sopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 29, 2026, 5:25 AM174.0s1 file scanned
SKILL.md
- name:
- create-operational-sop
- description:
- Generate validated operational SOPs for Ark ecosystem projects by testing commands before documenting them. Use when: user wants to create or audit SOPs for a project.
- allowed-tools:
- [Read, Write, Edit, Bash, Glob, Grep]
Create Operational SOPs
When to use:
- User wants to generate operational documentation for a project
- User wants to audit existing SOPs for completeness
User input: A project ID and optionally an SOP type (development-workflow, deployment-guide, all, audit).
Examples:
arkd— Audit and generate all missing SOPswallet development-workflow— Generate development workflow onlyfulmine audit— Only audit, don't generate
Outline
This skill generates validated operational documentation by actually testing commands before documenting them.
1. Validate Project
- Load
${ARKADIAN_DIR}/docs/INDEX.mdand find project entry - Resolve
docs_pathandrepo_path - Verify repository access
2. Detect Project Type
| Type | Indicators | Common Commands |
|------|-----------|----------------|
| Go Backend | go.mod, Makefile | make build, make test, go run |
| TypeScript Frontend | package.json + React/Vite | pnpm install, pnpm run start |
| TypeScript Backend | package.json + Node.js | pnpm install, pnpm run dev |
| Infrastructure | *.tf files | tofu init, tofu plan |
| Telemetry | docker-compose.yml + Prometheus | docker compose up |
3. Audit Existing Documentation
Check required files:
sop/development-workflow.md # REQUIRED
testing/usage.md # REQUIRED
testing/how_to_run.md # REQUIRED
testing/how_to_test.md # REQUIRED
testing/troubleshooting.md # REQUIRED
Optional (by type): sop/deployment-guide.md, testing/api-reference.md
Report audit results. If audit mode, stop here.
4. Generate Missing SOPs
For each missing file, follow the validation-first approach:
- Discovery Phase (read, don't execute): Check for build system, config files, scripts
- Validation Phase (test commands): Test ONE command per category to validate
- Generate Content: Only document commands that succeed or fail gracefully
Files to generate:
sop/development-workflow.md: Prerequisites, Setup, Building, Running, Testing, Quality Checks, PR Checklist
testing/how_to_run.md: Prerequisites, Quick Start, Docker Deployment, Local Development, Configuration, Verification
testing/how_to_test.md: Unit Tests, Integration Tests, Running Specific Tests, Test Coverage, CI/CD
testing/troubleshooting.md: Common Issues (Build Failures, Runtime Errors, Test Failures), Debugging (Logs, Docker Logs, Environment)
5. Validation Report
## Generation Report for <project-id>
### Commands Validated:
- `make build` - SUCCESS
- `make test` - SUCCESS (23 tests passed)
### Commands Not Validated (require manual verification):
- `make integrationtest` - Requires external dependencies
Safety Notes
- Never run destructive commands during validation
- Use dry-run flags when available
- Timebox validation — each command should timeout after 60 seconds
- Don't auto-commit — let the user review generated content first
Related Skills
arklabshq/update-project
documentation
VerifiedTrustedCommunity
Update project documentation based on new commits and changes in the repository. Use when: user wants to sync docs after project changes.
3SKILL.mdUpdated Apr 29, 2026
arklabshq/remove-project
testing
VerifiedTrustedCommunity
Remove a project from the Arkadian documentation registry and delete all associated documentation files. Use when: user wants to deregister a project.
3SKILL.mdUpdated Apr 29, 2026
arklabshq/pm-tasks
tools
VerifiedTrustedCommunity
RESTRICTED to ark-project-manager. Generate actionable, dependency-ordered task lists organized by user story.
3SKILL.mdUpdated Apr 29, 2026
arklabshq/pm-spec
testing
VerifiedTrustedCommunity
RESTRICTED to ark-project-manager. Create or update feature specifications from natural language descriptions.
3SKILL.mdUpdated Apr 29, 2026