Plugin · Claude Code · Development Tools

Kentanakae Claude Code Plugins Demo

kentanakae-claude-code-plugins-demo is a Claude Code plugin for the Build phase that provides a minimal one-plugin sample bundle for learning plugin structure.

by kentanakae · github.com/kentanakae/claude-code-plugins-demo

Install a minimal reference plugin bundle to learn how Claude Code plugins are structured before authoring your own.

0
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install kentanakae-claude-code-plugins-demo@kentanakae/claude-code-plugins-demo
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:kentanakae/claude-code-plugins-demo") and the paste-ready config with skillselion.get_install_config("plugin:kentanakae/claude-code-plugins-demo").

About

What it does

kentanakae-claude-code-plugins-demo is a one-plugin Claude Code bundle aimed at solo builders who want to see a working plugin skeleton without wading through a large monorepo. It lives in the community category on Skillselion and exists to answer practical questions: where files go, how a plugin is named, and what metadata surfaces in discovery. You would install or fork it when you are about to ship your first custom skill or hook pack and need a sanity-checked example rather than documentation alone. Because it is explicitly a demo, it does not solve domain problems like deployment or SEO; it reduces friction in the agent-tooling step so you can iterate on real plugins faster. Pair it with your own repo once you understand the layout, and treat this entry as a starter artifact, not a dependency for production apps.

Highlights

  • Single-plugin demo bundle (pluginCount: 1) for copy-paste learning
  • Community-tagged catalog entry with demo, description, and plugin1 keywords
  • Shows the smallest viable plugin layout for Claude Code registration
  • Useful as a template repo before publishing a real marketplace entry
  • No production integrations—purely illustrative structure

Why builders use it

New Claude Code users struggle to find a tiny, trustworthy example repo that mirrors how real plugins are packaged and discovered.

After cloning or registering the demo, you have a concrete plugin layout you can rename, extend, and publish as your own marketplace entry.

At a glance

  • Type - Plugin in Development Tools.
  • Adoption - 0 installs, 0 stars, 0 votes.

FAQ

Who is kentanakae-claude-code-plugins-demo for?

Solo builders and indie devs who are new to Claude Code plugins and want the smallest working example to fork.

When should I use kentanakae-claude-code-plugins-demo?

Use it during the build phase when you are scaffolding your first plugin manifest, skill folder, or local registration test.

How do I add kentanakae-claude-code-plugins-demo to my agent?

Clone the GitHub repo, point Claude Code at the plugin path per official plugin install docs, and enable the bundled demo plugin in your workspace settings.

Discussion

Comments

Share how you use kentanakae-claude-code-plugins-demo, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.