SKILLEMALL.ai

CD add-integration

Add a complete Sim integration from API docs, covering tools, block, icon, optional triggers, registrations, resolved-secret/model-input safety, and integration conventions. Use when introducing a new service under `apps/sim/tools`, `apps/sim/blocks`, and `apps/sim/triggers`.

simstudioai/sim Claude Code author: simstudioai Apache-2.0 2 files body ≈ 7 370 tokens Open the sourcegithub.com↗ analyzed 11 h ago

Add a complete Sim integration from API docs, covering tools, block, icon, optional triggers, registrations, resolved-secret/model-input safety, and…

As a process D 41/100 · Unfinished process — References files that are not bundled: scripts/README.md

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
D
41/100
Unfinished process
References files that are not bundled: scripts/README.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. 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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 7370 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: scripts/README.md
  • note edit-residue the text marks something as outdated (lines 341, 342, 343, 354, 618): 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

Will not run. References files that are not bundled: scripts/README.md
  • 0Tools and files. 1 referenced file(s) missing: scripts/README.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 49 mutating operations with no state check
  • 70Execution cost. Instruction body is 7370 tokens
  • 85Steps. 135 steps, 1 vague phrases
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 276: enough signal without eating the budget
  • +4Structure: 45 headings
  • +3Step-by-step instructions: 135 items
  • +4Has examples (14 code blocks)

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