Repository navigation
Publish first-party analytics assistant plugins - #1
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.
Package HitKeep's five canonical analytics skills as one first-party distribution with native Claude and portable OpenAI manifests, plus each platform's repository marketplace catalog. Users connect their own instance separately; no fixed region, credentials, hooks, contributor skills or new runtime are bundled.
Canonical files are copied byte-for-byte from HitKeep/hitkeep@d903126 and checked against recorded hashes. The package verifier checks both catalogs and manifest versions, and creates a deterministic ZIP.
Validation: five local tests pass, canonical verifier passes, and Claude native plugin/marketplace validation passes. Claude's optional public-directory icon warning is separate from native installation. Native installation/load acceptance and exact-head GitHub package checks are required before tagging; public directory approval and authenticated MCP/OAuth are reported separately.