CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and safe: complete executable examples, exact CLI commands, an explicit verification checklist, permission gating, and strong failure-mode recovery. Its main weakness is structure — a single ~765-line file with no local reference files, inlining publishing and theming detail that belongs in separate reference documents.

Suggestions

Split the ~765-line body: keep the contribution routing table, project setup, and verification checklist in SKILL.md, and move the publishing/OVERVIEW.md contract, theme contribution, and full composer-pill example into references/ files (e.g., references/publishing.md, references/themes.md) linked one level deep.

Trim inline policy prose such as the OVERVIEW.md authoring contract and host-picker behavior down to the actionable rules, pointing to the publishing guide for the full content contract.

Add explicit validation output expectations for the mobile audit (e.g., what a hit in client/web.ts versus elsewhere looks like) so the rg-based check is self-verifying.

DimensionReasoningScore

Conciseness

The body is dense and imperative throughout — it never explains concepts Claude already knows (React, npm, semver basics) and every section carries Paseo-specific contract details. Minor over-explanation remains, e.g., the multi-paragraph OVERVIEW.md authoring contract ("Use sentence case and plain factual language, with no em dashes. Omit installation commands, badges...") and the host-picker paragraph, which could be trimmed or moved. It fits the 4 anchor (efficient with minor trimmable instances) rather than 5, and is clearly above the 3 anchor's 'some unnecessary explanation'.

4 / 5

Actionability

Guidance is fully executable: complete copy-paste TSX/TS files for panels, screens, RPCs, attachment sources, and pills (e.g., the `client.addWorkspacePanel({...})` and `defineRpc({...})` examples), exact CLI invocations (`paseo plugin init /absolute/path/to/my-plugin`, `paseo plugin install npm:@acme/paseo-review@1.2.0`), a runnable audit (`rg -n "document\.|window\.|..." client/`), and a common-failures table. This matches the 5 anchor's copy-paste-ready coverage of common cases.

5 / 5

Workflow Clarity

"Verify the outcome" is an explicit 5-step validation checklist (typecheck → install/reload → `paseo plugin ls` requires `running` → confirm on the intended host including compact/mobile and dark theme → exercise the action and its error state), and the trust section adds a permission gate with verification (`paseo reload --json`, checking `appliedPaths`, re-checking `plugin ls`). A reload-failure feedback loop ("inspect `paseo plugin ls` ... fix the source, typecheck, and reload again") and a failures→causes table close the loop. Clear sequence with explicit validation and error recovery — the 5 anchor.

5 / 5

Progressive Disclosure

Headers, a contribution-routing table, and clearly labeled one-level-deep links to hosted docs (reference.md sections, plugin-examples repos) provide real navigation, but there are no local bundle files at all and the ~765-line body inlines content that clearly belongs in separate reference files — the full publishing/OVERVIEW.md contract, the theme section, and the complete composer-pill example. This sits between the 3 anchor (content that should be separate is inline, though structure exists) and the 4 anchor; the absence of any local reference split for this much material keeps it at 3.

3 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person-style imperative voice, an explicit "Use when" clause with concrete triggers, and a comprehensive, specific action list tied to a clearly distinct Paseo-plugin niche. The only weakness is a few missing natural synonyms such as "publish" and "debug".

DimensionReasoningScore

Specificity

The description enumerates many concrete actions — "create, edit, install, reload, enable, disable, remove, or troubleshoot a Paseo plugin", "add lifecycle hooks", "add a screen, sidebar header or footer item, workspace panel, or file panel", "add composer pills or attachment sources", "contribute a theme", "add plugin RPCs" — giving comprehensive coverage of the domain. It matches the 5 anchor (multiple specific concrete actions) rather than 4, since the action list spans the whole plugin lifecycle with no notable gaps.

5 / 5

Completeness

It explicitly answers both questions: "Build and manage trusted local Paseo plugins" states what it does, and "Use when the user asks to create, edit, install, ... or troubleshoot a Paseo plugin; add lifecycle hooks; ..." gives concrete trigger phrases. This is a clear match for the 5 anchor; the 4 anchor's weaker "when" does not apply.

5 / 5

Trigger Term Quality

Phrases like "add a screen", "slash commands", "contribute a theme", and "install, reload, remove, or troubleshoot a Paseo plugin" mirror what a user would naturally say, but a few common synonyms are missing — notably "publish" (a whole section of the skill), "uninstall", and "debug". This lands between the 4 anchor (good coverage, a few natural terms missing) and 5; the missing publish/debug variants keep it at 4.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct: every trigger is scoped to "Paseo plugin" (screens, sidebar items, Command Center items, composer pills, plugin RPCs), so it would not fire for generic plugin, theme, or slash-command skills. Minimal conflict risk, matching the 5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (768 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

getpaseo/paseo

Path

skills/paseo-plugin/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.