Conversation
Add documentation for combining local and remote skills from OpenHands extensions repository. Includes: - Use case explanation - Loading pattern comparison - Full example code reference - Local skill creation guide - Precedence rules Co-authored-by: openhands <openhands@all-hands.dev>
enyst
left a comment
There was a problem hiding this comment.
Reviewed latest changes. I left one inline suggestion to clarify that OpenHands uses the Claude Code plugin marketplace schema as a filter list for public skills, while local skills are merged separately. Otherwise LGTM.
Co-authored-by: openhands <openhands@all-hands.dev>
|
OpenHands-GPT-5.2 here. I pushed a docs update clarifying that |
The example was updated to use skills/ instead of local_skills/ to follow the standard plugin structure. Co-authored-by: openhands <openhands@all-hands.dev>
Address review feedback: Clarify that marketplace.json plugin entry names are used as a filter list for loading public skills, not defining skills directly. Local skills are merged separately from local_skills/ directory. Co-authored-by: openhands <openhands@all-hands.dev>
all-hands-bot
left a comment
There was a problem hiding this comment.
Taste Rating: 🟡 Acceptable - Good content but has clarity gaps that will confuse users.
Key Issue: The guide mentions concepts (marketplace.json, Claude Code plugin schema) that are never explained or demonstrated, while the example code uses a completely different approach. This creates a disconnect between what users read and what they learn.
|
Moved to draft - Evidence needs live run The Evidence section currently shows a code snippet, but not actual output from running it. Since this is a documentation PR clarifying schema requirements, acceptable evidence would be:
Please either:
|
all-hands-bot
left a comment
There was a problem hiding this comment.
Taste Rating: 🟡 Acceptable - Good content but has clarity gaps that will confuse users.
Key Issue: The guide mentions concepts (marketplace.json, Claude Code plugin schema) that are never explained or demonstrated, while the example code uses a completely different approach. This creates a disconnect between what users read and what they learn.
Co-authored-by: openhands <openhands@all-hands.dev>
all-hands-bot
left a comment
There was a problem hiding this comment.
Taste Rating: 🟡 Acceptable - Working code but has documentation gaps that will confuse users.
Key Issue: The guide shows the .plugin/marketplace.json format but never demonstrates how to load from it or what API consumes it. Users will wonder "how do I actually USE this file?" Additionally, the PR description mentions repo and marketplace parameters that don't appear in the guide itself.
|
@OpenHands resolve the review comments above and then mark them resolved through graphql. |
|
I'm on it! neubig can track my progress at all-hands.dev |
Co-authored-by: openhands <openhands@all-hands.dev>
|
Here’s the final summary of the work completed since the last summary:
Conciseness check:
So yes — the request has been completely addressed, and the instructions were followed faithfully. |
Summary
Updates marketplace schema documentation to clarify that both
repoandmarketplacefields are required.Closes #374
Details
The marketplace JSON schema requires both fields:
repo: The GitHub repository URL (e.g.,https://github.com/OpenHands/extensions)marketplace: Path to marketplace JSON within the repo (e.g.,marketplaces/default.json)This clarification helps users correctly configure custom skill repositories.
Testing
Documentation change - no unit tests applicable.
CI checks:
Evidence
Verification link: View conversation
Live command output against the SDK behavior documented here:
This is the behavior the docs are clarifying: users need both a repository source and a marketplace path to load a custom curated marketplace from a skills repo.
Checklist