OpenClaw Skill Scaffolder

Generate complete OpenClaw skill projects with SkillPay.me billing pre-wired. Describe what you want, get deployable code.

Security Scan

The skill's code, runtime instructions, and required environment variable (SKILLPAY_API_KEY) are consistent with its stated purpose of scaffolding billable OpenClaw skills, but there are a few operational and trust-related issues you should review before using it.

Purpose & Capability

Name/description say it scaffolds OpenClaw skills with SkillPay billing; the code and SKILL.md generate skill boilerplate, wrangler config, and worker code that uses SKILLPAY_API_KEY to call SkillPay.me. The single required env var is directly related to billing functionality and is proportionate.

Instruction Scope

Runtime instructions tell the agent to POST skill configuration to an external endpoint (openclaw-skill-scaffolder.swmengappdev.workers.dev). That aligns with a hosted scaffolding service but means you and the agent will send user_id, skill metadata, and env var names to an external third party. The endpoint returns templates; the flow does not ask for secret values in the request body, but user-provided descriptions or metadata could contain sensitive information. Also the included templates instruct users to run 'npx wrangler secret put' to store SKILLPAY_API_KEY in their workers (expected for enabling billing).

Install Mechanism

There is no install spec and this is effectively instruction-plus-templates; nothing is downloaded from arbitrary URLs during install. Code files are included in the package (templates and a handler), so no additional install-time network fetches are required by the skill bundle itself.

Credentials

Only SKILLPAY_API_KEY is required by the scaffolder itself, which is appropriate for a component that charges via SkillPay. The generated templates optionally include additional env var names requested by the skill author (e.g., OPENAI_API_KEY) but the scaffolder only requires the key needed to operate billing. There are no unrelated credential requests in the package.

Persistence & Privilege

always is false and the skill does not request persistent or system-wide privileges. It does not attempt to modify other skills' configurations. It will, however, instruct users to store SKILLPAY_API_KEY as a wrangler secret for their deployed worker (normal for enabling billing).

Assessment

This skill appears coherent for building billing-enabled skill projects, but before using it: (1) be aware you or your agent will POST skill metadata (including user_id and any descriptive text) to an external endpoint you do not control — avoid sending secrets or highly sensitive descriptions in those requests; (2) the scaffolder charges users using its SkillPay credentials on the hosted endpoint; when you deploy a generated skill you will be asked to set your own SKILLPAY_API_KEY as a wrangler secret — that grants the deployed worker the ability to bill on your SkillPay account, so only set it after you review the generated code; (3) review the returned templates (especially worker code) for any hidden endpoints or unexpected network calls before deploying; (4) note minor code issues (the scaffolder's handler imports from ../../shared/* which are not bundled here, and the scaffolder hard-codes a 0.02 charge in one place) — if you plan to use this in production, consider self-hosting the scaffolder or auditing and adapting the templates first.

Generate complete, deployable OpenClaw skills with SkillPay.me billing already wired up.

How to Use This Skill

Step 1: Charge billing and get templates

POST to the skill endpoint with your skill configuration:

POST https://openclaw-skill-scaffolder.swmengappdev.workers.dev/scaffold
Content-Type: application/json

{
  "user_id": "<user_id>",
  "name": "my-cool-skill",
  "description": "A skill that does something cool",
  "price_usdt": 0.01,
  "env_vars": ["SOME_API_KEY"]
}

The endpoint charges billing and returns scaffold templates:

• SKILL.md template
• wrangler.toml template
• src/index.ts worker template with SkillPay billing pre-wired
• src/billing.ts billing types
• Deploy commands

Step 2: Generate custom logic

Using your own capabilities, generate the custom skill logic based on the user's description. The scaffold provides the boilerplate — you fill in the business logic.

Guidelines for generating skill logic:

• Keep the Worker thin — only put server-side logic in it
• If the skill is mostly LLM-based, put the instructions in SKILL.md and only use the Worker for billing
• If the skill needs external API calls or computation, put that in the Worker
• Always include SkillPay billing before any work
• Use TypeScript, target Cloudflare Workers runtime
• Follow the patterns from this project (see existing skills for reference)

Step 3: Assemble the final skill

Combine the templates with your generated logic to create the complete skill project. The file structure should be:

my-cool-skill/
├── SKILL.md
├── wrangler.toml
└── src/
    ├── index.ts      (Worker with billing + your logic)
    └── billing.ts    (BillingResult type)

Step 4: Deploy instructions

Tell the user to run:

cd my-cool-skill
npx wrangler secret put SKILLPAY_API_KEY
npx wrangler deploy
clawhub publish . --slug my-cool-skill --name "My Cool Skill" --version 1.0.0 --tags latest

Pricing

$0.02 USDT per call via SkillPay.me