feat: Improve Paseo skill discovery - don't undersell them

[cleiter]

Prior search

• I searched existing issues and discussions, and this isn't already proposed.

What's the problem

It was not obvious for me to discover the Paseo skills (/paseo-advisor, /paseo-committee, /paseo-loop, /paseo-handoff). This came up in Discord today: I realized I'd been using Paseo daily without ever knowing /paseo-advisor existed. It's not just me — another user ran into trouble getting the skills working in Paseo too (#567).

The only place skills surface in the app is Settings → Integrations ("Orchestration skills" row), and two things there get in the way:

1. The description reads like it's not for me. "Teach your agents to orchestrate through the CLI" — as someone who doesn't personally use the Paseo CLI, I assumed it didn't apply to me. It's actually an agent capability (the agent uses the CLI under the hood, per the skills docs), but the copy surfaces the mechanism, not the benefit.
2. The docs links were easy to miss. "CLI docs" / "Skills docs" sit in the section header's top-right and read as header chrome, so I overlooked them.

What would solve it

Small, low-risk panel changes, ranked by how confident I am they're improvements:

1. Clarify the description (strongest — fixes a real misread). Teach your agents to orchestrate through the CLI → Teach your agents to spawn and coordinate other agents. Matches the docs' own "spawn, coordinate, and manage" framing; drops the "through the CLI" detail that reads as "not for me."
2. Move the docs links into the rows. Per-row "Learn more ↗" under each description instead of header-corner links. Two wins: each link is clearly attached to its item, and it scales — the section header is a fixed slot that runs out of room as integrations are added, whereas a per-row link works for any number of items.
3. Rename the row: Orchestration skills → Paseo skills. The commands are all namespaced /paseo-*, so the label matches what users actually type; the docs already use "Paseo skills" as a synonym. One snag: the docs' primary heading is still "Orchestration skills," so this creates a UI/docs naming split worth deciding deliberately. This is the most optional of the three.

These are prototyped locally (component + all six locale files). Not opening a PR alongside this — issue-first, per the template note. A PR can follow once there's a direction on the above, particularly the naming.

Alternatives you considered

• The panel only helps people already in Settings → Integrations. The bigger discovery gap is how anyone finds skills in the first place — onboarding mention, a one-time hint, or a more central skills list. That's a larger product question and can be split into its own issue to keep this one scoped to the panel.
• Keep "Orchestration skills" everywhere (UI + docs) and fix only the copy and links. A valid path if the naming shouldn't change — the rename is the most optional of the three.