Update: keep Cursor skills management on skills root#28
Merged
Conversation
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.
Original issue
Skill Manager v0.3.0 incorrectly treats Cursor-owned ~/.cursor/skills-cursor as a managed skills root, so Cursor-built skills appear in Skill Manager and can be managed.
Fix
Removes the skills-cursor managed-root candidate while preserving Cursor.app-based availability detection for Cursor skills actions against ~/.cursor/skills. Adds regressions ensuring Cursor-owned skills-cursor content is not scanned or managed.
Changed files
skill_manager/application/skills/mutations.py
skill_manager/harness/catalog.py
skill_manager/harness/contracts.py
tests/integration/test_skills_mutations.py
tests/support/fake_home.py
tests/unit/test_skills_adapters.py
Reviewer: @SI-RUI-ZHANG