feat: auto-detect Grok Bot skills target - #70
Merged
Merged
Conversation
Add `grok` as a first-class local target pointing at `~/agent-data/workflows` so SkillSync setup/connect can manage the same skills Codex already uses on Grok Bot VMs.
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.
Summary
~/agent-data/workflowsas a local target during setup.Why
On Grok Bot VMs, SkillSync previously configured only the Codex skill folder. Grok Bot reads user skills from
~/agent-data/workflows, so skills assigned to Codex alone did not appear there.Verification
npm test: 113 passed.setup --yestest confirms Grok is detected when~/agent-dataexists.~/agent-data/workflows.