DB Document Signature Packet Builder
(no description)
Turn a set of document-signing instructions into a practical sign-here and logistics checklist.
As a process B 68/100 · Nearly there — weak spots: failures and branches, consistency, running it twice
ProcedureWriting and documentsFinanceAI and agentstype and topics are labelled automatically from the skill text
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
For the model run — optional
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-missingSKILL.md: no `description` — the skill can never trigger - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 68/100
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (Document Signature Packet Builder) differs from the folder (document-signature-packet-builder)
- 50When it triggers. States when to use, but not when not to
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 56 steps
- 100Execution cost. Instruction body is 1713 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)
- +3Description length 0: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 20 headings
- +3Step-by-step instructions: 56 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 34.
External checks
ClawHub: clean
This is a prompt-only document checklist skill with no code, network access, credentials, or persistence, though users should be careful with its example about storing sensitive scans in cloud storage.
LLM: benign (high) · VirusTotal: · 16 Sept 2026