Add shadow-skill entrypoint#4
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
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.
Adds shadow-skill as the recommended provider-neutral Agent Skill entrypoint while keeping privacy-router as a compatibility alias and houdiniswap as the direct provider skill. Updates package metadata, README, installer scripts, and HoudiniSwap docs/error naming to reflect the new shadow skill branding. Strengthens deployment verification by probing shadow-skill/privacy-router runtime entrypoints so shadow-only installs fail instead of passing on SKILL.md alone. Adds regression coverage for full deployments and broken shadow-only deployments; validated with npm run --silent smoke, npm test, git diff --check HEAD, and the shadow-skill list-providers probe.