Plugin · Claude Code · Development Tools

Gekko68 My First Plugin

gekko68-my-first-plugin is a Claude Code plugin for the Build phase that provides a minimal one-plugin community bundle for learning plugin catalog registration.

by gekko68 · github.com/gekko68/my-first-plugin

Install a minimal community Claude Code plugin bundle to learn how plugin registration and keywords work before publishing 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 gekko68-my-first-plugin@gekko68/my-first-plugin
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:gekko68/my-first-plugin") and the paste-ready config with skillselion.get_install_config("plugin:gekko68/my-first-plugin").

About

What it does

gekko68-my-first-plugin is a community Claude Code plugin listing with almost no functional surface beyond proving the packaging pipeline works. Solo builders who have never registered a plugin can treat it as a smallest-possible example: one plugin in the bundle, a short description, and keyword hints for catalog search. It does not advertise skills, MCP servers, or statusline features—only that the repo exists as a Claude Plugin artifact. Install or fork it when you want a concrete repo layout to copy before you add real commands, hooks, or skills. Skip it when you need working productivity features; pair it with official Claude Code plugin docs and a real tool like history search or a custom statusline once you understand the install path.

Highlights

  • Single-plugin bundle (pluginCount: 1) from gekko68/my-first-plugin
  • Tagged for discovery with keywords: erstes, first, plugin, testplugin
  • Community catalog entry with auto-ingested metadata and zero votes at ingest
  • Useful as a reference slug when comparing empty starter repos to production plugins

Why builders use it

You want to ship your first Claude Code plugin but only see abstract docs and no tiny real repo to mirror.

After adding the bundle, you have a known-good single-plugin layout and catalog keywords to sanity-check your own packaging before you publish something serious.

At a glance

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

FAQ

Who is gekko68-my-first-plugin for?

Solo and indie developers who are experimenting with Claude Code plugin discovery and want the smallest community example repo to compare against their own project.

When should I use gekko68-my-first-plugin?

Use it during early Build-phase agent setup when you are validating install steps, repo naming, and catalog keywords—not when you need features that change how Claude works in the terminal.

How do I add gekko68-my-first-plugin to my agent?

Install or register the plugin from the gekko68/my-first-plugin repository through Claude Code’s plugin flow (marketplace or local path per your Claude Code version), then confirm one plugin appears in the bundle.

Discussion

Comments

Share how you use gekko68-my-first-plugin, 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.