AF teslamate-deploy
This skill should be used when the user wants to install or deploy TeslaMate (a self-hosted Tesla vehicle data logger + Grafana dashboard) on a local machine or a remote Linux server. Triggers include requests like "install TeslaMate", "deploy TeslaMate", "装 teslamate", "部署 teslamate", "在云服务器上跑个 teslamate", or "set up a Tesla data logger". The skill handles target selection, pre-flight checks, running the bundled deploy scripts, post-install health checks, and producing a user-facing usage document.
This skill should be used when the user wants to install or deploy TeslaMate (a self-hosted Tesla vehicle data logger + Grafana dashboard) on a local machine…
As a process F 55/100 · Will not run — References files that are not bundled: scripts/deploy-setup.sh, scripts/install-teslamate.sh, scripts/docker-compose.yml
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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/deploy-setup.sh - warning
missing-refreference to a missing file: scripts/install-teslamate.sh - warning
missing-refreference to a missing file: scripts/docker-compose.yml - warning
missing-refreference to a missing file: scripts/README.md - warning
missing-refreference to a missing file: references/troubleshooting.md - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 55/100
- 0Tools and files. 5 referenced file(s) missing: scripts/deploy-setup.sh, scripts/install-teslamate.sh, scripts/docker-compose.yml
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 85Steps. 42 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3213 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 504: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.