Fix agent skill packaging and CLI guidance - #1
Merged
Conversation
Signed-off-by: Artyom Keydunov <artyom.keydunov@gmail.com>
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
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.
Summary
:valuesWhy
Pre-release smoke testing found that strict YAML parsing caused
npx skills addto discover only four of nine skills. It also exposed several examples whose arguments did not match Cube CLI 1.7.21, plus two workbook commands classified as reads even though they mutate state.Validation
python3 scripts/validate-skills.py— 9 skills, 0 warningsskills@1.5.22clean Codex install and discovery — 9 skillscube-explore-modelRemaining coverage
Mutating model, content, agent, access, embed, and deployment workflows were intentionally not executed against the shared d3-demo tenant. They still need a disposable-tenant pass before those write paths are considered fully verified.