DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to publish existing SKILL.md files as a marketplace bundle with Claude Plugins Official

List skill folders from a source repo in a marketplace entry with strict set to false.

Who it is forA maintainer of an SDK or skills repo who ships SKILL.md files but no plugin.json manifest.

The problemSkills in a source repo cannot be offered through the marketplace without a manifest unless the marketplace entry declares them directly.

The outcomeA marketplace entry that exposes a chosen set of skills from the source repo, each registered in Claude Code.

What you need first

  • Claude Code with its plugin system
  • A plugin name listed in the claude-plugins-official marketplace
  • Git and a text editor for building or publishing a plugin

Steps

  1. Confirm each skill folder you want to publish contains a SKILL.md file.
  2. Create a marketplace entry with name, description, author, category, and a git-subdir source that gives the url, path, ref, and sha.
  3. Set "strict": false and list the skill paths in the skills array, relative to source.path.
  4. Add a homepage URL and submit the entry for review.
  5. Confirm each skill appears in Claude Code after the entry is accepted.

Prompt for your agent

Using the strict false skill-bundle format in the anthropics/claude-plugins-official README, draft a marketplace entry for the skills at <skill-path> in <source-repo-url>. Output the JSON entry. Verify that every path in the skills array points to a directory containing a SKILL.md file.

Caveat. The README example for the source sha field shows a blank value, so confirm the required value against the marketplace documentation before submitting.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page