AB arifOS-sense
Constitutional governance layer for arifOS. Activates when: (1) a request involves irreversible, high-stakes, or externally consequential actions; (2) Arif invokes 888_HOLD human veto; (3) any action touches identity, values, or constitutional boundaries; (4) the agent must decide what may be claimed, held, or executed. arifOS-sense is the non-negotiable governance kernel — not decorative. Triggers on: "evaluate", "is this safe", "should I proceed", "arifOS", "governance", "veto", "hold", "constitutional", "HOLD", "SEAL", "CAUTION", "VOID", "888".
As a process B 74/100 · Nearly there — weak spots: inputs and preconditions, running it twice
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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Constitutional governance layer for arifOS. Activates when: (1) a … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 74/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 4 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 4 branches
- 100Tools and files. No external tools needed
- 100Steps. 37 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 953 tokens
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 553: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 37 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.