SKILLEMALL.ai

AB render-deploy

Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.

davila7/claude-code-templates Agent Skills author: davila7 MIT 19 files body ≈ 4 328 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy…

As a process B 69/100 · Nearly there — weak spots: result and completion, progress reporting

AnalyzerGitHubGitLabDockerInfrastructureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
99
Quality 40%
89
Run on models
none yet
Process rating
B
69/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Dangerous commands cmd-pipe-to-shell-known-host SKILL.md:112
      Pipe-to-shell installer from a well-known host (still executes remote code) (quoted — discussed, not commanded)
      - Linux/macOS: `curl -fsSL https://raw.githubusercontent.com/render-oss/cli/main/bin/install.sh | sh`
      quoted

    Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 69/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 60Tools and files. Uses tools (bash, web, git) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 70Execution cost. Instruction body is 4328 tokens
    • 85Steps. 76 steps, 2 vague phrases
    • 100Inputs and preconditions. Inputs and preconditions are listed
    • 100Failures and branches. 9 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Running it twice. Mutating operations check current state
    • low 11 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (4 tags): a typed call is more reliable

    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
    • +2Single-language instructions
    • +3Description length 229: enough signal without eating the budget
    • +4Structure: 34 headings
    • +3Step-by-step instructions: 76 items
    • +4Has examples (26 code blocks)
    • +4Reference files are cited in the instructions (9 of 10)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.