SKILLEMALL.ai

CD create-runner-adapter

Add a new harness/provider integration to native Paperclip Runner, from requirements and protocol research through implementation, packaging, and real end-to-end acceptance. Use for new Runner adapters; legacy direct adapter authoring and migration are outside this skill.

paperclipai/paperclip Agent Skills author: paperclipai 1 file body ≈ 1 342 tokens Open the sourcegithub.com↗ analyzed 10 h ago

Add a new harness/provider integration to native Paperclip Runner, from requirements and protocol research through implementation, packaging, and real…

As a process D 43/100 · Unfinished process — References files that are not bundled: ../../../doc/RUNNER-INTEGRATION-PLAYBOOK.md, ../../../doc/runner-integration-templates.md

IntegrationSoftware developmentAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
D
43/100
Unfinished process
References files that are not bundled: ../../../doc/RUNNER-INTEGRATION-PLAYBOOK.md, ../../../doc/runner-integration-templates.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../../doc/RUNNER-INTEGRATION-PLAYBOOK.md
  • warning missing-ref reference to a missing file: ../../../doc/runner-integration-templates.md
  • note edit-residue the text marks something as outdated (lines 73): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: ../../../doc/RUNNER-INTEGRATION-PLAYBOOK.md, ../../../doc/runner-integration-templates.md
  • 0Tools and files. 2 referenced file(s) missing: ../../../doc/RUNNER-INTEGRATION-PLAYBOOK.md, ../../../doc/runner-integration-templates.md
  • 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
  • 30Running it twice. 3 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 18 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1342 tokens

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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 272: enough signal without eating the budget
  • +4Structure: 3 headings
  • +3Step-by-step instructions: 18 items

Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.