feat(mothership): send workspace skill ids and descriptions in the chat inventory by waleedlatif1 · Pull Request #9264 · simstudioai/sim · GitHub
Skip to content

feat(mothership): send workspace skill ids and descriptions in the chat inventory - #9264

Merged
waleedlatif1 merged 1 commit into
stagingfrom
feat/workspace-skill-catalog
Oct 21, 2026
Merged

waleedlatif1 merged 1 commit into
stagingfrom
feat/workspace-skill-catalog

Conversation

@waleedlatif1

@waleedlatif1 waleedlatif1 commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • The chat's workspace inventory now sends each workspace skill's id and description, not just its name, built-ins included (builtin-<name>). The mothership agent can then show workspace skills as a catalog (name, id, description) and load a matching one with skills get <id>, the way frontier clients and the Agent Skills spec list name and description and load the body on demand. Before, it saw only names: it couldn't judge relevance, and it needed a search round to find an id.
  • generated/protocol.ts is regenerated from the worker contract. The new fields are optional, so either side can deploy first.

Companion: simstudioai/mothership#778

Type of Change

  • New feature

Testing

  • workspace-inventory.test.ts now checks skill ids and descriptions, including a built-in and an empty description. It fails before the change; after, 2 pass. CI runs the rest.

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

…at inventory

The mothership agent now sees workspace skills as a catalog, name, id and description, and
loads a matching one with skills get <id>, as Agent Skills clients do; with names alone it
could not judge relevance and had to search for an id first. Built-ins carry their
builtin-<name> id. The generated protocol copy is synced from the worker contract, where
both fields are optional so either side can ship first.
@vercel

vercel Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

@github-actions github-actions Bot added the requires-mothership-merge Has a companion PR on the mothership/copilot side — merge in lockstep label Oct 21, 2026
@github-actions

Copy link
Copy Markdown

⚠️ Cross-repo companion check

One or more companion PRs aren't merged into staging yet. Merging this without them will leave copilot and sim out of sync — merge them in lockstep.

  • ❌ simstudioai/mothership#778 — OPEN, not merged (targets staging) — feat(worker): show workspace skills to the agent as a catalog

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 3 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Turn on auto-fix | Re-trigger cubic

@greptile-apps

greptile-apps Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

@waleedlatif1
waleedlatif1 merged commit 463350c into staging Oct 21, 2026
55 checks passed
@waleedlatif1
waleedlatif1 deleted the feat/workspace-skill-catalog branch October 21, 2026 01:56

This branch was previously deployed

1 inactive deployment
Preview — c5eaff32 Deployed Oct 21, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

requires-mothership-merge Has a companion PR on the mothership/copilot side — merge in lockstep

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant