skill: Skill references wrong binary name for run/describe commands#2
Draft
ATX24 wants to merge 1 commit into
Draft
skill: Skill references wrong binary name for run/describe commands#2ATX24 wants to merge 1 commit into
ATX24 wants to merge 1 commit into
Conversation
Builder fix for issue #15
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.
Auto-drafted by
baml-bench-builderfrom builder issue #15.Issue
Skill references wrong binary name for run/describe commands
The baml:core skill states that the relevant commands live in baml-cli, but run and describe only exist on the baml-lang binary (the standalone language runtime). baml and baml-cli are the Python SDK CLI and do not expose these subcommands. Agents following the skill's guidance immediately hit 'unrecognized subcommand' errors. The skill must distinguish the three binaries shipped by baml-py and direct agents to baml-lang for run/describe and to baml/baml-cli for generate/check. Additionally, baml-lang has no init subcommand, and baml check misreports baml.math as an unknown namespace while baml-lang handles it correctly — both gaps compound the two-CLI confusion.
Builder summary
Builder fix for issue #15
Evidence
535156586059This is a draft PR generated from deduplicated agent reports. Review before merging.