Conversation
Echelon interop audit found construct-artisan was missing the capabilities metadata block required by the 037 pipeline. Values derived from skill-level index.yaml declarations across 14 skills (sonnet, moderate, medium, sequential). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3c604f0b64
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| requires: | ||
| native_runtime: true | ||
| tool_calling: true | ||
| thinking_traces: false |
There was a problem hiding this comment.
If the 037/Echelon pipeline now gates construct admission on construct.yaml capabilities, this top-level thinking_traces: false will misclassify Artisan as runnable on trace-less runtimes even though /envisioning-direction explicitly requires traces in skills/envisioning-direction/index.yaml:55-59. In that environment the construct will be accepted, but invoking that skill will fail or be silently degraded because the pack metadata under-reports one of its contained skills' hard requirements.
Useful? React with 👍 / 👎.
| native_runtime: true | ||
| tool_calling: true | ||
| thinking_traces: false | ||
| vision: false |
There was a problem hiding this comment.
Several shipped skills declare vision: true (skills/iterating-visuals/index.yaml:56-60, skills/decomposing-feel/index.yaml:54-58, skills/styling-material/index.yaml:50-54, and skills/surveying-patterns/index.yaml:50-54), so publishing the pack-level manifest with vision: false under-advertises a hard runtime dependency. Any scheduler that trusts only construct.yaml can now place Artisan on a non-vision model, after which those screenshot- and image-based workflows are guaranteed to be unavailable even though the construct was accepted.
Useful? React with 👍 / 👎.
1 participant
Summary
capabilitiesmetadata block toconstruct.yamlindex.yamldeclarations across 14 skills:sonnet,moderate,medium,sequential,downgrade_allowed: falseTest plan
construct.yamlparses cleanly with yq/yaml lint🤖 Generated with Claude Code