CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paseo-committee

Form a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use when stuck, looping, tunnel-visioning, or facing a hard planning problem.

Quality

85%

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

78%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.

A tight, well-structured instruction-only skill: it stays lean, provides mostly concrete guidance (verbatim safety suffix, tool names, title format), and lays out a clear five-step workflow with a convergence loop. The main gaps are unspecified mechanics — the contents of a problem-level prompt and how arguments are passed between members — plus a small redundancy around profile contrast.

Suggestions

Define what a "problem-level prompt" should contain (e.g., a short template: context, symptoms, failed attempts, desired outcome) in Workflow step 1 so the prompt quality is not left to guesswork.

Specify the mechanism and a bound for step 4: how arguments are relayed between members (e.g., a follow-up prompt quoting the other member's position) and a maximum number of rounds before summarizing the disagreement for the user.

Trim the duplicated contrast guidance — the Prerequisites rationale sentence and the Composition bullet state the same different-provider-families rule.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows, and every section instructs rather than describes. However, the contrast principle is stated twice — "Contrast is the point of a committee, so pick profiles from different provider families" in Prerequisites and again as "one contrasting high-reasoning profile from another provider family" in Composition — which is a minor instance of repetition that could be trimmed, matching the 'efficient; minor instances' anchor.

4 / 5

Actionability

Concrete, executable elements are present: the verbatim no-edits suffix, specific tool calls (`list_profiles`, `create_agent`), and the title format `[Committee] <task>`. Gaps remain: what a "problem-level prompt" should contain is undefined, and the mechanism for "passing their arguments between each other" (e.g., which tool or prompt) is unspecified — the 'mostly executable with minor gaps' anchor.

4 / 5

Workflow Clarity

The five-step numbered workflow is clearly sequenced, includes a convergence feedback loop (step 4-5), and the skill is analysis-only (no destructive or batch operations), so the validation cap does not apply. It falls short of the top anchor because there is no guidance on what a problem-level prompt must include, how many inter-agent rounds to allow, or what to do if members never converge.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files, and its sections (Prerequisites, Composition, Hard rules, Workflow) are well-organized and easy to navigate. Its single external dependency — the **paseo** skill — is clearly signaled at one level of depth, so it earns full marks under the simple-skill provision.

5 / 5

Total

17

/

20

Passed

Description

85%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: it states concrete capabilities, includes an explicit "Use when..." clause with natural trigger terms, and occupies a distinct niche. Trigger coverage is good but could add common synonyms (e.g., "blocked", "spinning in circles") for full marks.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Form a committee of two high-reasoning agents", "do root cause analysis", "produce a plan" — with only "step back" being abstract. It is not comprehensive (e.g., parallel planning and disagreement resolution are absent), so it fits the 'several specific actions; minor gaps' anchor rather than 3 (only 1-2 actions) or 5.

4 / 5

Completeness

It explicitly answers both questions: what ("Form a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan") and when ("Use when stuck, looping, tunnel-visioning, or facing a hard planning problem") with concrete trigger phrases. The 'when' clause is fully explicit, so the score-4 caveat about implicit triggers does not apply.

5 / 5

Trigger Term Quality

"stuck", "looping", "tunnel-visioning", and "hard planning problem" are phrases a user would naturally say, with "stuck" being especially natural. Common variations like "blocked", "spinning in circles", or "going in circles" are missing, keeping it below the comprehensive-coverage anchor.

4 / 5

Distinctiveness Conflict Risk

The multi-agent committee niche is distinct and the trigger set (stuck/looping/tunnel-visioning/planning) is unlikely to fire for document, code, or data skills. Triggers like "stuck" are somewhat generic and could overlap with general debugging or planning skills, but the distinctive "committee of two high-reasoning agents" framing keeps conflict risk minimal — a close call between 4 and 5, settled by the clearly differentiated capability statement.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

getpaseo/paseo

Path

skills/paseo-committee/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.