Skip to content

fix(plugin): Add required name field to Hamster skills - #14

Closed
harveyfullstack wants to merge 1 commit into
feat/bundle-plugin-mcpfrom
feat/cursor-plugin-parity
Closed

fix(plugin): Add required name field to Hamster skills#14
harveyfullstack wants to merge 1 commit into
feat/bundle-plugin-mcpfrom
feat/cursor-plugin-parity

Conversation

@harveyfullstack

@harveyfullstackharveyfullstack commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

What changed

Each Hamster skill now has a name that matches its folder.

Why it matters

Cursor expects that name. Without it, a skill can show up under a cache-directory name instead of ask, ship, or the others.

How it works

The shared skill files keep their existing argument and prompt behavior. Only the required name field is added.

User impact

People using Hamster in Cursor should see skills under their real names. Claude Code behavior stays the same.

Scope, limits, and follow-up

This is stacked on the hosted MCP plugin work. It does not change install docs, marketplace listing, or other hosts.

Validation

Official Claude plugin validation passed on the plugin manifest, skills, and agents (strict mode).

@harveyfullstack
harveyfullstack marked this pull request as draft August 25, 2026 22:37
@harveyfullstack
harveyfullstackforce-pushed the feat/cursor-plugin-parity branch from 49d47b4 to 3819eb0CompareAugust 25, 2026 22:38
Cursor identifies each skill by a name that matches its folder.
@harveyfullstack
harveyfullstackforce-pushed the feat/cursor-plugin-parity branch from 3819eb0 to c33d715CompareAugust 25, 2026 22:39
@harveyfullstack

harveyfullstack commented Aug 25, 2026

Copy link
Copy Markdown
ContributorAuthor

Folded into #13.

Sign up for freeto 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.

1 participant

@harveyfullstack