SkillForge — Skill Generator & Auditor

Generate complete, publish-ready OpenClaw agent skills from natural language descriptions. Audit existing skills for quality, safety, and completeness.

Prerequisites

SkillForge CLI must be installed globally:

npm install -g @shadoprizm/skillforge@latest

Check version: skillforge --version (requires 0.3.2+)

Commands

Generate a Skill

Free tier (template scaffold, no API key):

skillforge "<description>" --output <path> --lang <typescript|javascript|python>

Pro tier (AI-powered, requires API key):

skillforge "<description>" --pro --output <path> --lang <typescript|javascript|python>

Audit a Skill

skillforge audit <path> --format <table|json|markdown>

Pro audit with AI analysis:

skillforge audit <path> --pro --format markdown

Publish to ClawHub

First-time auth:

clawhub login

Then publish:

skillforge "<description>" --output <path> --publish

Or publish an existing skill:

clawhub publish <path> --slug <slug> --name "<name>" --version <semver>

Workflow

When asked to create/generate a skill:

1. Clarify the skill purpose if the description is vague
2. Run skillforge "" --pro --output /tmp/skillforge-gen --lang typescript
3. Read the generated files to verify quality
4. Run skillforge audit /tmp/skillforge-gen --pro to score it
5. If score is B+ or above, offer to publish to ClawHub
6. If score is below B+, improve the SKILL.md and scripts manually, then re-audit
7. On operator approval, publish: clawhub publish /tmp/skillforge-gen --slug --name "" --version 1.0.0

When asked to audit a skill:

1. Run skillforge audit --pro --format markdown
2. Present the report to the operator
3. Offer specific fixes for any issues found
4. Re-audit after fixes

API Key Configuration

SkillForge Pro uses the operator's own API key (BYOK model). Supported providers:

Keys can also be stored via: skillforge config:set-api-key

Audit Categories

Constraints

• Always use --pro when an API key is available for best quality
• WARNING: Pro mode sends skill contents to your chosen AI provider. Do not audit directories containing secrets, .env files, private keys, or credentials. Point audits only at skill directories.
• Verify generated skills actually work before publishing
• Never publish without operator approval
• Use --format json for CI/CD contexts, --format table for chat
• Slug must be unique on ClawHub — if taken, try variations
• Never pass production API keys to untrusted skill content for auditing