CC teleport-tbot-bootstrap
Bootstrap a persistent Teleport Machine ID (tbot) setup on macOS using LaunchAgent and tbot configure identity. Trigger when asked to set up, automate, or validate local Teleport bot identity refresh, including proxy/token/join-method inputs, LaunchAgent persistence, and first-run verification with tsh. Complements the teleport-tsh-ssh skill for day-to-day SSH/command/scp usage with the refreshed identity.
As a process C 57/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 7
-
high Dangerous commands
cmd-persistencereferences/launchagent-notes.md:13Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.openclaw.tbot.plist
-
high Dangerous commands
cmd-persistencescripts/bootstrap_tbot_launchagent.sh:89Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl bootstrap "gui/$(id -u)" "$PLIST_PATH"
Medium and low: 5
-
medium Dangerous commands
cmd-persistencereferences/launchagent-notes.md:7Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)- Starts at login and can be started immediately with `launchctl bootstrap`.
quoted -
medium Dangerous commands
cmd-persistencescripts/bootstrap_tbot_launchagent.sh:43Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)PLIST_PATH="${HOME}/Library/LaunchAgents/com.openclaw.tbot.plist"code literal -
medium Dangerous commands
cmd-persistenceSKILL.md:28Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)- Starts immediately when loaded with `launchctl bootstrap gui/<uid> ...`.
quoted -
medium Dangerous commands
cmd-persistenceSKILL.md:80Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)- `launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.openclaw.tbot.plist`
quoted -
medium Dangerous commands
cmd-persistenceSKILL.md:110Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)- `rm -f ~/Library/LaunchAgents/com.openclaw.tbot.plist`
quoted
Files scanned: 5. 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 57/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 41 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1102 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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 409: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 41 items
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.