docs(skill-sources): add authoring guide for third-party skill-source contributors#708
Merged
Merged
Conversation
…tributors Step-by-step guide from the source-repo side — how a third-party org lays out its repo, authors Magpie-shaped skills, picks an org identity, chooses a distribution method + verification anchor, writes a source descriptor, gets listed for discovery, validates with Magpie's own validator, and maintains releases. Complements docs/skill-sources/README.md (the adopter side); links both ways.
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.
Summary
Adds
docs/skill-sources/authoring-a-source.md— a step-by-step guide for third-party repos/organizations that want Magpie adopters to be able to pull their skills. It's the source-repo counterpart todocs/skill-sources/README.md(which covers the adopter side) and fills a gap left after the feature landed (Phase A #677 + Phase B #707).Ten steps: two-tree layout → author skills in the Magpie shape → keep the eval binding resolvable → pick an org identity (
independentor register one) → choose a distribution method + verification anchor → write the source descriptor → get listed for discovery → validate with Magpie's ownskill-and-tool-validate→ tell adopters how to pull it → maintain releases. Grounded in the actual validator contract (required frontmatter/descriptor keys, install methods) and cross-linked both ways with the README.Verification
prekclean on the new + edited docs — markdownlint, doctoc (TOC generated), typos, and lychee (every relative cross-reference/anchor resolves).🤖 Generated with Claude Code