BC Profile
View, edit, or clear the LifeOS User Model (PRINCIPAL_IDENTITY.md) — persistent identity context loaded at session startup. Three intents: View, Edit (identity, goals, constraints, preferences), Clear (reset). Read by Algorithm OBSERVE and skills for personalization. USE WHEN profile, show profile, view profile, who am I, my profile, edit profile, update profile, clear profile, user model, PRINCIPAL_IDENTITY. NOT FOR settings.json or CLAUDE.md edits (use update-config).
Skill lets you view, edit, and clear PRINCIPAL_IDENTITY.md — your persistent user profile loaded at session start. Three operations: view, edit (identity, goals, constraints, preferences), reset. Used by OBSERVE algorithm and other skills for personalization.
Tests show B grade: quality 85, safety 100. Five files, no critical issues. Runs on nine platforms from Claude to DeepSeek. Process score of 60 suggests straightforward logic without complex validation. Install if you run LifeOS infrastructure and need to swap identity context between sessions. For standard Claude use, built-in features suffice.
View, edit, or clear the LifeOS User Model (PRINCIPALIDENTITY.md) — persistent identity context loaded at session startup. Three intents: View, Edit…
As a process C 60/100 · Has gaps — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "evals"
Process rating: all ten parameters 60/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (read) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1215 tokens
- 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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 474: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 7 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.