SKILLEMALL.ai

CC paseo-plugin

Build and manage trusted local Paseo plugins. Use when the user asks to create, edit, install, reload, enable, disable, remove, or troubleshoot a Paseo plugin; add lifecycle hooks; transform agent configuration, environment, MCP servers, or workspace creation; automate permissions or turn follow-ups; add a screen, sidebar header or footer item, workspace panel, or file panel; add Command Center items or slash commands; add composer pills or attachment sources; transform, render, or append agent timeline items; contribute a theme; use Paseo from plugin code; or add plugin RPCs.

getpaseo/paseo Agent Skills author: getpaseo NOASSERTION 1 file body ≈ 9 895 tokens Open the sourcegithub.com↗ analyzed 34 h ago

Build and manage trusted local Paseo plugins.

As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, execution cost

GeneratorGitHubAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
C
60/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Execution cost w 6
40
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.
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 body-long SKILL.md body ≈ 9895 tokens (recommended < 5000); move details to references/
  • note edit-residue the text marks something as outdated (lines 736): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 60/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 40Execution cost. Instruction body is 9895 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
  • 60Failures and branches. 2 branches
  • 100Steps. 30 steps
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 17 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (7 tags): a typed call is more reliable

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
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 583: enough signal without eating the budget
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 30 items
  • +4Has examples (24 code blocks)

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