feat: add cline skills marketplace entries

[saoudrizwan]

Summary

Adds marketplace skill entries for every skill currently published in github.com/cline/skills, using the Cline skill install alias shape that maps to npx skills add.

Each new entry installs from the multi-skill repo with:

cline skill install cline/skills --skill <skill-name>

That corresponds to the underlying skills CLI form:

npx skills add cline/skills --skill <skill-name>

This PR also updates the existing cline-sdk marketplace entry to install from cline/skills --skill cline-sdk instead of the older standalone cline/sdk-skill repo, since cline-sdk is now present in the consolidated cline/skills source repo.

Technical Approach

I pulled latest main in this repo and confirmed /workspace/cline-skills was already up to date. I then enumerated every SKILL.md under /workspace/cline-skills/skills and created one registry/skills/<id>/entry.json entry per source skill.

The registry schema only needs common marketplace metadata plus install.args, so the entries keep the install surface simple:

"install": {
  "args": ["cline/skills", "--skill", "linear-sdk-scripting"]
}

The marketplace generator derives the rendered command from type: "skill", so clients receive commands like:

cline skill install cline/skills --skill linear-sdk-scripting

Metadata was derived from each source skill's frontmatter and normalized for marketplace display:

• homepage points to the specific skill subdirectory in cline/skills.
• repo points to https://github.com/cline/skills.
• license uses the skill-specific license when the skill declares one; otherwise it falls back to the repo license, Apache-2.0.
• tags use the existing canonical marketplace vocabulary from tags.json.
• verified is set to true for these Cline-hosted skills.
• New entries omit icon because the source skills repo does not provide per-skill icon assets and the field is optional.

Gotchas and Decisions

The source repo has a skill named mintlify, but the marketplace already has an MCP entry with id mintlify. The generator treats ids as globally unique across MCPs, plugins, and skills, so adding registry/skills/mintlify/entry.json failed validation with a duplicate id.

To preserve the actual install target while keeping the marketplace catalog valid, the skill entry uses marketplace id mintlify-skill but keeps the install args pointed at the source skill name:

"id": "mintlify-skill",
"install": {
  "args": ["cline/skills", "--skill", "mintlify"]
}

I also checked the skills CLI help in /workspace/vercel-skills, which confirms --skill <skills> is the selector flag for installing specific skills from a multi-skill source.

Validation

Ran the marketplace validator:

npm run validate

Result:

Validation passed: 202 entries.

I also generated the catalog locally to spot-check rendered commands:

linear-sdk-scripting: cline skill install cline/skills --skill linear-sdk-scripting
mintlify-skill: cline skill install cline/skills --skill mintlify
cline-sdk: cline skill install cline/skills --skill cline-sdk
{"total":202,"mcps":149,"plugins":15,"skills":38}

Additional coverage checks confirmed:

• 37 source skills in /workspace/cline-skills/skills.
• 37 marketplace entries installing from https://github.com/cline/skills.
• No missing source skill install targets.
• No extra install targets.
• No duplicate install targets.
• No taglines over the 120-character schema limit.
• Skill entry JSON is ASCII-only.

Testing

npm run validate
node scripts/generate.mjs