ref(skill-writer): make path guidance portable#103
Merged
Conversation
Clarify that generic skills should use skill-root-relative paths and avoid provider-specific path variables. Keep registration guidance tied to the active repository layout while preserving a small orchestration layer in SKILL.md. Co-Authored-By: Codex <codex@openai.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
plugins/sentry-skills/skills/skill-writer/references/registration-validation.md
Show resolved
Hide resolved
Replace ambiguous references to generic skills in the portability guidance. This makes it clear the path and naming rules apply to any skill that should remain provider-agnostic, not only the generic classification. Co-Authored-By: OpenAI Codex <codex@openai.com>
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
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.

Clarify how skill-writer should handle bundled file paths and registration paths so generated skills stay portable across hosts.
This updates the authoring and validation guidance to prefer skill-root-relative references like references/... and scripts/..., avoid provider-specific path variables in generic skills, and keep repository registration steps tied to the active workspace layout.
It also does a self-pass on skill-writer so the portability rule lives in the design, authoring, and validation references instead of expanding the top-level orchestration flow.