Skip to content

docs: add mixed marketplace skills guide#375

Draft
neubig wants to merge 3 commits intomainfrom
docs/mixed-marketplace-skills-example
Draft

docs: add mixed marketplace skills guide#375
neubig wants to merge 3 commits intomainfrom
docs/mixed-marketplace-skills-example

Conversation

@neubig
Copy link
Contributor

@neubig neubig commented Mar 4, 2026

Summary

Add documentation for the new mixed marketplace skills example that demonstrates how to combine local skills with remote skills from the OpenHands extensions repository.

Related PRs

Changes

  • New guide: sdk/guides/mixed-marketplace-skills.mdx

Content

The guide covers:

  • Use case explanation: Why teams need mixed skill sources
  • Loading pattern comparison: Table comparing load_skills_from_dir(), load_public_skills(), and load_available_skills()
  • Full example: Embedded code from examples/01_standalone_sdk/43_mixed_marketplace_skills/main.py
  • Local skill creation: How to create SKILL.md files
  • Precedence rules: How local skills override public skills

Preview

The documentation explains:

  1. Loading local skills from a project directory
  2. Loading remote skills from OpenHands/extensions
  3. Combining both with proper precedence handling
  4. Using the combined skills with an agent

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>
Comment on lines +59 to +62
The marketplace.json can define:
- Local skills to include
- Remote skills to pull from OpenHands/extensions
- Skill dependencies between local and remote skills
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reads like the marketplace defines local skills directly, but in OpenHands we're using the Claude Code plugin marketplace schema as a filter list for which public skills to load. Could we clarify that the marketplace entries are plugin names used as a filter, while local skills are merged separately?

Suggested change
The marketplace.json can define:
- Local skills to include
- Remote skills to pull from OpenHands/extensions
- Skill dependencies between local and remote skills
The marketplace.json follows the Claude Code plugin marketplace schema. In OpenHands, the
plugin entry names are used as a filter list for which public skills to load; local
skills live in local_skills/ and are merged separately.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(HUMAN: this wasn't me - and I read it twice to make sure 😅 ... not fully sure when the agent reviewed this docs/ PR 😇 )

Copy link
Collaborator

@enyst enyst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>
Copy link
Collaborator

enyst commented Mar 5, 2026

OpenHands-GPT-5.2 here. I pushed a docs update clarifying that marketplace.json uses the Claude plugin schema plus the OpenHands skills[] extension, and that marketplace entries point to skill directories while local skills are merged separately. Commit: 32e23db.

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants