[Feature] Manage skills and agents from T3, route to providers via symlinks

[Fenris159]

Agents & Skills manager (central store + per-provider symlink routing)

Summary

T3 already sits as a control plane over multiple coding agents (Claude Code, Codex, Cursor, Grok Build, OpenCode). Skills and custom agents are still managed separately in each provider’s native folders, which means duplication, drift, and no single place to see or control what is installed where.

I’d like T3 to own a canonical agents/skills store and optionally expose those files to enabled providers via symlinks, with a dedicated UI for inventory, routing, and repair.

What I’m proposing

• A new sidebar entry (e.g. robot icon) that opens an Agents & Skills window
• A T3 panel as the source of truth (~/.t3/agents, ~/.t3/skills) for create / import / edit / delete
• Collapsible per-provider panels that show what each harness currently sees
• Per-item provider toggles so each skill/agent can be routed to any combination of enabled providers
• Clear status for managed vs native vs broken vs name-collision entries
• Toolbar actions for Repair and Remove T3 symlinks (never deleting the canonical files)
• View/light-edit through T3’s existing right-panel preview surface, with Open in… for real editing
• A persistent routing matrix under the user folder so intent survives reinstalls

No marketplace. Strictly file-managed. Symlinks only — no silent copying or rewriting of provider configs.

Why T3

This fits T3’s role as the multi-provider control surface. Providers keep loading skills/agents from their own paths; T3 only manages a central store and the symlink map into those paths. Portable SKILL.md content stays shared; provider-specific quirks can be warned about without blocking.

Attachment

I’ve attached an MD agent action plan as a launchpad: layout, row/routing model, collision handling, validation (warnings only), empty states, persistence shape, phased implementation, and non-goals. It’s a design reference, not a demand that this land as one large PR.

Happy to shrink this to a minimal Phase 1 (canonical store + list + routing file + basic symlink toggle for one provider) if the direction is interesting.
T3-Agents-Skills-Manager-Action-Plan.md

[NK-Works]

Following up from #18637 (closed as dup) — the symlink-routing approach here is exactly the right mechanism; adding the safety contract we specced there:

• T3 library is truth, native files are generated outputs with backup + dry-run diff on every sync.
• Fail-closed translation: incompatible permission/hook/env fields block with a clear error, never silently drop.
• No silent overwrite: if a harness file changed outside T3, ask before overwriting; every sync = diff preview + auto-backup + one-click rollback + sync log.
• Subagents as a separate section, disabled by default with an opt-in Enable button; per-harness custom subagents always allowed via the same per-harness-only flag.
• Import first (pull existing into library, dedupe by name+hash), then explicit push/copy.

Happy for this thread to own the routing mechanism if #6987 owns the central-list scope.