AC aispace
Secure temporary file storage and encrypted asynchronous delivery with the aispace CLI. Use when the user asks to upload or download an artifact, create or revoke an expiring share, send or receive a sealed bundle, deliver to a pinned agent inbox, manage aispace identities or recipient trust, pair a transfer to another device, recover a transfer, inspect quota, or request adaptive durable-first transport. Do not invoke merely because a task creates a local file; use it when aispace or remote artifact exchange is requested or clearly needed.
Secure temporary file storage and encrypted asynchronous delivery with the aispace CLI.
As a process C 63/100 · Has gaps — weak spots: result and completion, 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 63/100
- 0Result and completion. Does not say what the result is
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 14 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, read) that frontmatter does not declare
- 100Steps. 14 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1556 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 546: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.