BD paperclip-create-agent
Create new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.
Create new agents in Paperclip with governance-aware hiring.
As a process D 41/100 · Unfinished process — References files that are not bundled: /approvals/<approval-id>, /agents/<agent-url-key-or-id>, /issues/<issue-identifier-or-id>
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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: /approvals/<approval-id> - warning
missing-refreference to a missing file: /agents/<agent-url-key-or-id> - warning
missing-refreference to a missing file: /issues/<issue-identifier-or-id> - note
edit-residuethe text marks something as outdated (lines 189, 196, 197, 205, 206): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 41/100
- 0Tools and files. 3 referenced file(s) missing: /approvals/<approval-id>, /agents/<agent-url-key-or-id>, /issues/<issue-identifier-or-id>
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 100Steps. 24 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2469 tokens
- 100Running it twice. Mutating operations check current state
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 212: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.