SKILLEMALL.ai

AC agent-deployment-checklist

Production deployment checklist for AI agent infrastructure. Covers Mac Mini and server deployment with 5-layer stack (base install, IAM config, client software, security hardening, onboarding), 5-file memory system pre-scaffolding, security baselines, starter crons, and day-1 onboarding. Use when deploying agents for clients or setting up new infrastructure. NOT for cloud/serverless deployments or containerized agents.

ClawHub Agent Skills author: samledger67-dotcom v98.0.1 MIT-0 2 files body ≈ 3 008 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

TemplateInfrastructureAI and agentstype 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
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
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-cron-mention SKILL.md:356
      Mentions editing / listing crontab (documentation of a security skill)
      crontab -l > "$BACKUP_DIR/crontab.bak"
      security skill

    Files scanned: 2. 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 52/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 26 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
    • 85Steps. 74 steps, 1 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3008 tokens
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 423: enough signal without eating the budget
    • +4Structure: 26 headings
    • +3Step-by-step instructions: 74 items
    • +4Has examples (15 code blocks)
    • +1License stated

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

    External checks

    ClawHub: suspicious
    This is a coherent deployment checklist, but it under-scopes sensitive credential and backup handling for production client agent systems.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026