Per-bot skill attach for Grok Bot (scope skill to one bot id)

[ScriptedAlchemy]

Context

Plugin Library “Apply to bot…” needs to attach a skill (e.g. pstack poteto-mode) to one named Grok Bot. Today Applier returns missing_attach_api.

Current state

• gbot bots update = profile fields only (no skill attach)
• AB skills are plugin-scoped host files loaded by Cursor/Claude/Codex — not addressable to one Grok Bot id
• In Grok Bot, skills are a global shared library across assistants
• Honest interim only: profile bake (gbot bots update --description) or nudge (gbot send)

Ask

A real per-bot skill attach API (gbot and/or agent-bundle), or a documented decision that per-bot attach is out of scope.

Acceptance

• apply(plugin_id, skill_id, bot_ref) can attach without mutating unrelated bots
• Or explicit “use profile_bake / account-wide only” product decision

Filed from Plugin Applier for Plugin Library Delivery.

[ScriptedAlchemy]

Decision: account-wide only. Grok Bot has no per-bot skill attach, so apply(plugin_id, skill_id, bot_ref) cannot exist honestly.

Evidence from the Grok Bot harness runtime (grok-bot-harness/src/runner/conversation-outline.ts):

• FileSkillStore wraps new GlobalSkillLibrary(<sandRoot>/workflows) (:774). listAllFrom returns this.library.list() with no agent filter (:923-932); the only per-agent content is that agent's cron automations. migrateLegacyPerAgentSkills (:1082) exists because the product moved skills out of per-agent directories into this shared library.
• The gateway RPCs getAgentWorkflows, importAgentWorkflowText, deleteAgentWorkflow take an agent id only to pick whose automations ride along; the skill they write lands in the shared library for every bot.

What is now real: ScriptedAlchemy/grok-bot-cli#91 (merged, ships in the next grok-bot-cli minor) adds gbot skills list|add|remove. add ./skills/<name> posts a SKILL.md over the gateway and every bot sees it; remove <id|name> deletes a workflow skill for every bot and refuses managed, plugin, and automation entries. Applier should call that and label the result account-wide. Profile bake (gbot bots update --description) stays the only per-bot lever.