AC file-management
File Management: Upload and manage files in one tool: upload_standard, upload_large, list with previews, get signed URLs, download, delete, share, update metadata, inspect access history, and extend expiration. Use when an agent needs file management, small file upload, large file upload, signed upload url generation, temporary file hosting, access history, file id, limit through AgentPMT-hosted remote tool calls. Discovery terms: file management, small file upload, large file upload.
File Management: Upload and manage files in one tool: uploadstandard, uploadlarge, list with previews, get signed URLs, download, delete, share, update…
As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, consistency, running it twice
The same skill appears in 1 more place: ClawHub
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 63/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 17 mutating operations with no state check
- 40Consistency. Frontmatter name (file-management) differs from the folder (file-management-newest)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 113 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 3377 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
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 489: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 113 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.