Repository navigation
Improve Cursor skills and validate component metadata - #17
Merged
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
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.
Improve the five bundled Cursor skills so each has a focused discovery trigger, a concrete example, clear tool-selection boundaries, and a purple Custom Mode badge. Align the enrichment agent and validation command with these workflows, including reuse of validated finder results and recovery from bulk timeouts.
Replace regex-only frontmatter checks with strict YAML parsing and metadata validation. CI now rejects malformed YAML, duplicate keys, incorrect names or types, empty instructions, and invalid badge colors without echoing potentially sensitive field contents. Add a manual Cursor discovery and behavior checklist, and bump the plugin to 0.1.10.
Authoring follows Cursor's built-in create-skill, create-rule, and create-subagent guidance and the current public Agent Skills documentation. The skills intentionally remain discoverable for relevant enrichment requests.
Validation: 28 tests pass, npm ci and schema validation pass, npm audit reports zero vulnerabilities, public-file checks pass, and hosted health responds HTTP 200. Authenticated Cursor behavior and UI discovery are documented manual checks, not claimed as executed.