DD LifeOS
Install and onboard a user into LifeOS — the Life Operating System (current state → ideal state via TELOS + the Algorithm). The agentic installer detects your OS + harness, wires hooks with permission, scaffolds your USER tree, pulls in sources you provide, and runs the TELOS / current→ideal interview that seeds your Pulse dashboard. USE WHEN install LifeOS, set up LifeOS, lifeos setup, lifeos-setup, lifeos interview, onboard me, run the interview, integrate LifeOS into my harness, update LifeOS, uninstall LifeOS, first-time setup, lifeos doctor, check my install, what capabilities are broken, pulse setup, set up pulse, install pulse, audit pulse setup, is Pulse healthy, report a LifeOS bug, file an issue upstream, report this to the project, contribute this fix, open a PR to LifeOS, suggest a feature, ask the LifeOS project. NOT FOR building or cutting a LifeOS release (private release tooling), editing TELOS after onboarding (use Telos / Interview), or LifeOS system maintenance (use the private maintenance skill).
Install and onboard a user into LifeOS — the Life Operating System (current state → ideal state via TELOS + the Algorithm).
As a process D 44/100 · Unfinished process — References files that are not bundled: Setup.md
The same skill appears in 1 more place: Personal_AI_Infrastructure
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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
- Shorten the description to 1024 characters.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Dangerous commands
cmd-pipe-to-shellINSTALL.md:18Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation of a security skill)curl -fsSL https://ourlifeos.ai/install.sh | bash
security skill -
low Risky intent
intent-offensive-securityinstall/commands/secupdates.md:4Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)argument-hint: [optional focus, e.g. "ransomware" or "this week"]
detector
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1031 chars, limit 1024 - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
missing-refreference to a missing file: Setup.md - note
frontmatter-keyunknown frontmatter key "evals" - note
edit-residuethe text marks something as outdated (lines 51): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 44/100
- 0Tools and files. 1 referenced file(s) missing: Setup.md
- 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
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1926 tokens
- low The response is described with custom markup (7 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
- +3Description length 1031: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 6 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 48.