Symbol Docs
Features

Your First Plugin

A guided path from an empty workspace to a skill with its own file, running in Claude Code or Codex: the four steps, what to do if you lose the install command, and importing a repository instead.

The first-plugin guide takes you from an empty workspace to running your own skill, with a file it executes, in Claude Code or Codex. It walks through four steps, shows them all from the start, and saves your place as you go.

Open it from the Library of an empty workspace (Build your first plugin). Everything it makes is ordinary: the marketplace and plugin are managed afterwards in the marketplace settings, and the skill is a capsule you edit like any other.

The four steps

  1. Create a marketplace. In your personal workspace you can name it, or leave the name blank for a random one with no personal details. An organization's marketplace is named after the organization, and only an owner or Admin can create it. The marketplace is created together with your first plugin, in the next step.
  2. Create a plugin. The naming rules sit beside the name, and a live preview shows how your skills will be invoked, as /<plugin>:<skill>. If the workspace already has a plugin, for example one made in Settings while the guide was open, the guide asks you to use it instead of making another.
  3. Write a skill and add a file. Start from the working example or write your own title, when to use it, and instructions. Then add a file, write its contents and mark it executable. Saving the skill or its file does not publish anything. If you change the example's instructions, say what reply to expect so you can tell the skill worked.
  4. Publish and install. The guide shows exactly what ships, including each file and whether it is executable, and warns that the plugin runs code on the machine of everyone who installs it. You review the files and confirm, as on any code release; if the skill or its file changes after you reviewed it, review again. If the skill's Type is protected, the publish waits for approval. In your personal workspace you approve it yourself; in an organization, an owner or Admin does. The guide links the change, and once it is approved you continue from where you were, even after leaving the page. Publishing never protects a Type by itself. Once your marketplace serves the release, the guide shows the install commands for Claude Code and Codex, the command to try the skill, and the reply to expect.

Leaving and coming back

Your place is saved as you type, privately: only you see it, even in a shared organization workspace. Leave at any step and the guide reopens there, from the Library's Continue notice or the same link. If something the guide made was deleted meanwhile, it takes you back to the step that makes it.

If you open the guide in two tabs, the second one to save shows the first one's progress instead of overwriting it.

The install command is shown once

The command that adds your marketplace holds a token that works like a password: anyone who has it can install your plugin. The guide warns you before showing it, shows it once, and never puts it in your saved progress, the address bar or the browser's storage. Reloading the page, going back or switching workspace does not show it again.

If you lose it, replace it in the marketplace settings (Rotate it): the old command stops working and you get a new one. The guide never replaces your token on its own. The other instructions, the try command and the expected reply stay available whenever you return.

Importing a repository instead

The first step also offers Import a repo instead. Enter the repository's plain HTTPS address, such as https://github.com/owner/repo. Never include a user name, password or token: an address with one is refused, and the guide keeps only the owner and repository names. Importing is not available yet, so the guide shows the repository it saved and that nothing has been imported, and you can return to building a plugin here.

On this page