jb/paseo
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Help agents diagnose Paseo provider problems (#3243)

Browse Source 
* feat(skills): add Paseo help and provider diagnostics

Give support agents a topology-aware troubleshooting entry point backed by the deployed documentation index, and expose the daemon provider diagnostic through the CLI so agents can inspect the affected host directly. Agent-launching skills now use configured profiles instead of the removed orchestration preferences.

* test(cli): keep provider diagnostics on real boundaries

Remove the internal client mock and preserve its normalization and host-targeting assertions through the existing isolated-daemon coverage.
This commit is contained in:
Mohamed Boudra
2026-08-12 00:57:33 +02:00
committed by GitHub
parent 5f5c585e68
commit d012b6f071
10 changed files with 239 additions and 78 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/paseo-committee/SKILL.md
+7 -7
View File
@@ -6,7 +6,7 @@ user-invocable: true
# Committee Skill
Two agents from contrasting providers, fresh context, planning a solution in parallel. They stay alive for review after implementation.
Two agents from contrasting profiles, fresh context, planning a solution in parallel. They stay alive for review after implementation.
The purpose is to step back, not double down. The committee may propose a completely different approach.
@@ -14,18 +14,18 @@ The purpose is to step back, not double down. The committee may propose a comple
## Prerequisites
Read the **paseo** skill. Before choosing committee members, read `~/.paseo/orchestration-preferences.json` unless the user explicitly named providers in this request. Do not create committee agents until you have read it.
Read the **paseo** skill. Call `list_profiles` before choosing committee members. Do not create committee agents until you have read the configured profiles and their `notes`.
Contrast is the point of a committee, so pick across providers deliberately using the configured preferences rather than hardcoded defaults.
Contrast is the point of a committee, so pick profiles from different provider families when possible. Materialize each profile into `create_agent`.
## Composition
Two members with different reasoning styles, selected from orchestration preferences:
Two members with different reasoning styles, selected from configured Agent profiles:
- one planning/research-strength provider
- one contrasting high-reasoning provider
- one whose notes fit planning, research, or root-cause analysis
- one contrasting high-reasoning profile from another provider family
Override only when the user explicitly asks for different members.
If the user names profiles, use those. If fewer than two suitable profiles are configured, use Paseo's provider discovery fallback for the missing member and tell the user. Override the selection only when the user explicitly asks for different members.
## Hard rules