AF alter-my-standing
Use when an agent or member needs to know what its own ~alter account can currently do, what raises its tier next, or why a call just failed. Covers reading your canonical handle and summary, checking whether your key is still valid and what scopes it carries, reading your trust tier and what raises it, reading your full portfolio of activity and standing, and checking a person's remaining privacy budget before you query sensitive trait data. Trigger phrases include "who am I on alter", "is my alter key still valid", "what scopes do I have", "what is my trust tier", "why did my alter call fail", "what raises my tier next", "check my alter standing".
Covers reading your canonical handle and summary, checking whether your key is still valid and what scopes it carries, reading your trust tier and what raises…
As a process F 28/100 · Will not run — weak spots: steps, result and completion, when it triggers
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: 2. 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 28/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1043 tokens
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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 657: enough signal without eating the budget
- +4Structure: 8 headings
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.