Getting Started
High confidenceUpdated 25 Apr 2026 by David Olsson
Getting Started
The toolkit installs in 30 seconds and works in any Claude environment that reads ~/.claude/.
Installation
bash
curl -L https://scsiwyg.com/claude-skills-and-pipelines-by-worksona.zip -o skills.zip
unzip skills.zip
cp -r clean-export/commands/* ~/.claude/commands/
cp -r clean-export/skills/* ~/.claude/skills/
That's it. Restart your Claude session and the skills are available.
Environments
| Environment | Support |
|---|---|
| Claude Code | Full โ parallel agents, file writes, terminal |
| Cursor (agent mode) | Full |
| Claude.ai Projects | Partial โ sequential agents, no file writes |
| Claude Desktop | Partial โ chat-only |
Most pipelines note which modes they support in their Reference page.
How Triggers Work
Pipeline commands use slash syntax:
/code-audit
/security-audit
/landing-page
Type the command in Claude and it reads the SKILL.md, inventories the current directory, and starts the pipeline.
Skills respond to natural language:
"publish a post about the new auth system"
"what should I blog about"
"run a design review on this component"
Each skill documents its trigger phrases in its Reference page.
Running Your First Pipeline
- Open Claude Code in a project directory
- Type
/code-audit - The pipeline inventories your codebase with
project-scanner - Five auditors run (parallel in Claude Code)
- Results land in
docs/03-code-audit/
Each pipeline writes numbered Markdown reports to a docs/ subfolder. Reports are standalone โ share them, commit them, or feed them into the next pipeline.
Skill Categories
- Code Quality โ audit, security, design review
- Documentation โ project docs, portfolio synthesis
- Strategy โ competitive moat, infrastructure costs
- UX โ experience health, positioning and conversion
- Marketing โ landing pages, design systems
- Publishing โ scsiwyg blog, git-to-post pipeline
- Standalone โ SR&ED ledger, deploy