Repository navigation
docs(skills): clarify miniapp CLI coverage so it stops reading web-only - #92
Merged
maidang-xing merged 2 commits intoSep 28, 2026
Merged
Conversation
The two shared miniapp skills said 'No tuyaopen-cli CLI coverage' and left the reader to conclude submit/release/bind are web-only - exactly what a field agent concluded while shipping a real product. The heading is literally true (no native tuyaopen-cli subcommands) but the section never said what the absence means, and never pointed at the surfaces that DO publish the shell route. Both bodies now state the heading's precise meaning: the platform steps are scriptable outside the IDE, and the route is published by the CLI itself - the miniapp upload envelope's webSteps block and schema list discovery. No commands are added to the payloads (repo gate skillIsolationScan keeps these Broker-only by owner decision). Versions bumped 2.7.4 / 2.5.3 for the payload change; registry skills 1.1.2 -> 1.1.3 and publishedAt refreshed per the domains gate.
The '申领 appid / 网页步骤' row pointed at 'skill tuyaopen-miniapp 0.2 (3)' - an anchor that no version of that skill's SKILL.md carries (it died with the pre-migration shared-skill layout and the capability-broker migration removed the last body that could have held it). The row now states what is actually true: the appid itself is issued on the web console only, and the post-appid version/bind page URLs ride the tuyaopen-cli miniapp upload webSteps envelope. tuyaopen-start 2.0.2 -> 2.0.3 for the payload change.
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.
What
The two shared miniapp skills (
miniapp-development-workflow2.7.3,tuyaopen-miniapp2.5.2) carried a## Notuyaopen-cliCLI coveragesection that said what the payload does not have, and nothing else. A field agent developing a real product read it and concluded submit-for-review / release / bind are web-only, sent the user to the browser, then got stuck for a round onMINIPROGRAM_UI_INFO_NOT_COMPLETEwith no recoverable hint.Why the bodies only get prose
The repo gate on the IDE side (
skillIsolationScan.test.ts) keeps these four shared executable skills Broker-only by owner decision, so no command table is added here — the executable route's authoritative discovery surfaces are the CLI itself: theminiapp uploadenvelope'swebStepsblock andschema list. Both bodies now say the heading's precise meaning: no native subcommands ≠ web-only; the steps are scriptable outside the IDE and the CLI publishes the route itself.Bookkeeping
skills.version1.1.2 → 1.1.3,publishedAtrefreshed (domains gate)Validation
validate-skills-index.py— OK (24 items)check-skill-version-bumps.py— OK (2 changed payloads)check-domain-version-bumps.py --base-ref origin/main— OK (4 domains)skillIsolationScan.test.ts— 12/12 green against the updated payloads