Fix broken skill: remove stray conflict marker, re-pin install version - #11
Merged
Conversation
main shipped a literal leftover '>>>>>>> 111dce1 (...)' conflict-marker line from #9's merge, live on the public repo and served by ClawHub and Hermes. Also re-applies the version pin on the npm install example, lost in the same merge (ClawHub's security scan flags a bare, unpinned npm install -g as MEDIUM supply_chain risk).
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.
main is currently serving a broken skill via ClawHub and Hermes — #9's merge left a literal leftover conflict-marker line in skills/charming/SKILL.md:
Removes it. Also re-applies the npm install version pin from #8, which got reverted in the same merge (ClawHub's security scanner flags a bare unpinned
npm install -gas MEDIUM supply_chain risk).