CC render
Deploy and operate apps on Render from OpenClaw (Blueprint + Dashboard deeplink, native MCP, or REST). Use when the user wants to deploy, host, or publish an app; create or edit render.yaml; add web, static, worker, cron, private, Workflow, Postgres, or Key Value services; get a Blueprint deeplink; connect Render MCP with openclaw mcp add; or configure env vars, health checks, scaling, and previews.
Deploy and operate apps on Render from OpenClaw (Blueprint + Dashboard deeplink, native MCP, or REST).
As a process C 54/100 · Has gaps — References files that are not bundled: references/mcp-integration.md, references/workflows.md, references/codebase-analysis.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/mcp-integration.md - warning
missing-refreference to a missing file: references/workflows.md - warning
missing-refreference to a missing file: references/codebase-analysis.md - warning
missing-refreference to a missing file: references/blueprint-spec.md - warning
missing-refreference to a missing file: references/rest-api-deployment.md - warning
missing-refreference to a missing file: references/post-deploy-checks.md - warning
missing-refreference to a missing file: references/troubleshooting-basics.md - note
edit-residuethe text marks something as outdated (lines 182): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 54/100
- 0Tools and files. 7 referenced file(s) missing: references/mcp-integration.md, references/workflows.md, references/codebase-analysis.md
- 0Result and completion. Does not say what the result is
- 30Running it twice. 52 mutating operations with no state check
- 40Consistency. Frontmatter name (render) differs from the folder (deploy-on-render)
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 66 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 3139 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 402: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 66 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.