Skip to content

docs: add Skills workflow guidance to CLAUDE.md #78

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ondrejhlavacek wants to merge 1 commit into from
Closed

docs: add Skills workflow guidance to CLAUDE.md #78

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,13 @@ When adding new commands, agents, or skills to a plugin:
3. Bump the version in `.claude-plugin/marketplace.json` for the corresponding plugin entry
4. Update the root README.md feature list for the affected plugin (add/remove items from the list)

## Skill Script Path Conventions
## Skills

### Skills Workflow

- When creating or modifying skills in the AI kit, remember publishing requires a version bump in the skill manifest. Don't rename skills without explicit user approval.

@tomasfejfar tomasfejfar May 25, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate

  1. Bump the version in the plugin's .claude-plugin/plugin.json
  2. Bump the version in .claude-plugin/marketplace.json for the corresponding plugin entry

@ondrejhlavacek ondrejhlavacek May 25, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But it never worked for me unless explicitly told.


### Script Path Conventions

- Scripts must detect their own location using `SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"` and derive `SKILL_DIR="$(dirname "$SCRIPT_DIR")"`
- Scripts run from the user's **project root**, never from the skill directory
Expand Down