AF profile-use
Safely use a user's private local personal profile to help fill registration, signup, checkout, banking, KYC, and onboarding forms. Use when the user asks to enter or reuse identity details such as name, address, phone, postal code, email, birthdate, payment card, bank account, tax ID, or other personal data. Prioritize privacy, redaction, consent before submission, and local/iCloud/encrypted profile sources rather than storing personal data in chat or Git.
Safely use a user's private local personal profile to help fill registration, signup, checkout, banking, KYC, and onboarding forms.
As a process F 59/100 · Will not run — References files that are not bundled: references/profile-template.json, references/profile-schema.json, references/sync-model.md
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/profile-template.json - warning
missing-refreference to a missing file: references/profile-schema.json - warning
missing-refreference to a missing file: references/sync-model.md
Process rating: all ten parameters 59/100
- 0Tools and files. 3 referenced file(s) missing: references/profile-template.json, references/profile-schema.json, references/sync-model.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 3 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
- 100Steps. 55 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3704 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (4 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 461: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 55 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.