Skip to content

feat(skills): the cs-cli skill knows the Drive — cs drive, every built-in prefix; plugins 0.2.2 and 0.1.1 - #5

Merged
BestOwl merged 2 commits into
mainfrom
feat/cs-cli-drive
Oct 26, 2026
Merged

BestOwl merged 2 commits into
mainfrom
feat/cs-cli-drive

Conversation

@corespeed-agent-ensemble

@corespeed-agent-ensemble corespeed-agent-ensemble Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Why

Codex uses CoreSpeed through the cs CLI (the corespeed-cli plugin is skills-only), and the cs-cli skill never named Drive: its prefix list stopped at memory__* and manage__*, so an agent reading it concluded Drive was unavailable (Slack #chat, 2026-10-25). cs 0.10.0 (corespeed-haas #1292, on npm since 2026-10-26) adds cs drive put / get / ls / mv / rm / share / usage, the way a local file reaches the Drive from a shell, since bytes never travel through tool arguments.

What

  • cs-cli skill (source in plugins/corespeed/, copied byte-for-byte to plugins/corespeed-cli/ as CI requires): the description and triggers name cs drive; the prefix paragraph lists every built-in family (drive__, media__, web__, social__, mail__) and says a missing prefix is switched off or not connected, not missing from the CLI; a Drive section with the cs drive commands and when to use cs mcp call drive__… instead; the commands table gains the drive rows. The memory example now calls memory__search (the current name; the _memory suffix was dropped on the server, and the public docs use the new name).
  • Manifests: corespeed 0.2.1 → 0.2.2 (both manifests, as CI requires), corespeed-cli 0.1.0 → 0.1.1; descriptions, long descriptions and keywords name the Drive; corespeed-cli's default prompts stay at the Plugins Directory's limit of three, the Drive upload prompt replacing the memory one (memory is reached through the find-and-call prompt), and check.yml now holds both Codex manifests to that limit (round 1 of review). The Claude Code marketplace description names Drive too.
  • README: the "Codex, CLI only" paragraph and the plugin table mention cs drive; the intro names the Drive among what the server carries.

Everything written here is on the public docs: https://corespeed.io/docs/cli/drive (ships with the haas PR) and https://corespeed.io/docs/drive. No suppliers, storage or ticket numbers.

Order

@corespeed/cs 0.10.0 is on npm (released from corespeed-haas #1292), so the skill describes commands the installed CLI has.

🤖 Generated with Claude Code

Agent and others added 2 commits October 25, 2026 23:37
…mv/rm/share/usage, every built-in prefix; plugins 0.2.2 and 0.1.1

Codex reaches CoreSpeed through the cs CLI, and the skill never named
Drive, so an agent reading it took Drive for unavailable. cs 0.10.0 adds
cs drive; this names it, lists every built-in tool family, and bumps the
manifests.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… both Codex manifests to the limit

The Plugins Directory refuses a manifest with more than three
interface.defaultPrompt entries (plugin_default_prompt_too_many). The Drive
prompt replaces the memory one — memory is reached through the find-and-call
prompt — and check.yml now fails a Codex manifest over the limit.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

@corespeed-hopper corespeed-hopper Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Approved after two review rounds, cycle 1, at 409edc1.

Reviewed the complete diff from merge base 3572d85 and the fix commit. No blocking findings remain. The CLI manifest now has three starter prompts. The new guard passes both manifests and rejects the prior four-prompt manifest. Targeted fixtures also cover a single string, three prompts, empty entries, and non-string entries. The PR description reflects the final change.

Verified the Drive commands against public documentation and the integrity-checked @corespeed/cs 0.10.0 npm artifact. The package help lists all seven verbs. The linked private implementation PR was outside this reviewer's repository scope; its release claims were checked against the published artifact.

CI passed on the exact reviewed SHA: manifests and scan, https://github.com/corespeed-io/cs/actions/runs/40250535306. GitHub reports no separately required checks for this branch. No CI-covered full suite was rerun locally.

Reviewer session: 503f08ba-3343-4012-a1f0-b698db9f4f20.

@BestOwl
BestOwl merged commit fe28f8d into main Oct 26, 2026
3 checks passed
@BestOwl
BestOwl deleted the feat/cs-cli-drive branch October 26, 2026 00:58
corespeed-agent-ensemble Bot pushed a commit that referenced this pull request Oct 26, 2026
… client reaches it

main brought #5 (the cs-cli skill knows the Drive; manifests 0.2.2 and the
prompt-count guard). The Claude Code manifest keeps main's wording — its
server is the full /mcp, Drive tools included — and names .mcp.claude.json.
The Codex manifest keeps this branch's wording — its server is the fixed
plugin surface, which has no Drive tools — and says files move through
cs drive, as the connected apps' tools move through cs mcp call. Both go
to 0.3.0. The README carries both table rows and names cs drive in the
Codex paragraph; the skill copies merged identically.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant