skills: endpoint-first story; drop JSON API / /v3/call framing#12
Merged
Conversation
…ll framing Lead the API + entry skills with the gateway's compat endpoints, multimodality (images/audio/video), realtime, and roundtable. Structured output is now a response_format parameter, not a /v3/call canonical example. Left the SDK skill untouched (opper.call is the real SDK primitive; SDKs get their own pass).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The product story moved off the proprietary JSON API (
/v3/call/ "task completion"). The skills still led with it. This makes the main story the endpoints we actually promote: the gateway's compat endpoints, multimodality, realtime, and roundtable.What
opper-api/SKILL.md(main rewrite): "Pick your endpoint" now leads with/v3/compat, then/v3/images,/v3/audio/*,/v3/videos, realtime, and roundtable. Canonical example is a compat chat completion; structured output is shown viaresponse_format(a parameter, not a separate endpoint). New Multimodal generation and Roundtable sections. Gotchas and "where to look next" updated; stale doc links fixed (/build/gateway/*,/build/multimodal/*).opper/SKILL.md(entry): decision table, proposals, Phase-4 test table, and the "API surfaces" vocabulary reframed from "Chat API / JSON API" to compat / multimodality / realtime / roundtable. Also fixed two pre-existing inaccuracies: a non-existentopper.chat(...)andresult.json_payload(the SDK returnsresult.data).compatibility.md/migration.md: replaced the "prefer/v3/call" guidance withresponse_formatfor structured output and Route aliases for multi-model fallback.README.md,opper-cli/SKILL.md: small wording fixes.Deliberately left alone
opper-sdksskill:opper.call()is the genuine SDK primitive (the SDK doesn't expose compat), so removing it would make the skill wrong. The SDKs get their own update pass; only minimal clarity touches belong here, none were needed.🤖 Generated with Claude Code