Generalize source-specific skill save location (WIP)#3
Open
justinf-cdata wants to merge 1 commit into
Open
Conversation
Don't assume a fixed ~/skills path for the skill generated by `cdatacli drivers skill`. Instruct saving the SKILL.md to wherever the user's AI coding tool loads skills from (e.g. ~/.claude/skills for Claude Code; other tools use their own convention), and to ask the user if unsure. Update Step 1 to match. Still WIP ahead of release.
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.
Updates the
cdata-driver-cliskill so the file generated bycdatacli drivers skillis saved to the location appropriate for the user's AI coding tool, instead of a hardcoded~/skills/cdata-<source>/path.SKILL.mdto whichever directory the user's tool loads skills/rules/instructions from (examples for Claude Code user/project paths; note other agents use their own conventions); ask the user if unsure.Status: WIP ahead of the CLI release. Does not touch the top-level README (PR #2 is handling that separately).
Requires one approving review from another CData maintainer (self-approval is blocked).