Skip to main content

Create a Registry Resource

Go to Registry → Add Resource. Every resource is created in two steps: fill in its identity, then publish its content — this page walks through one example per type.

Skill​

  • Type: SKILL
  • Key: java-spring-boot
  • Name: Java Spring Boot
  • Description: JHipster 9 entity pattern, Liquibase, MapStruct, REST resources

Save, then click Publish version on the new row. Source type Inline (the default) — paste the skill's Markdown content into the Content field and publish.

Permission Preset​

Same steps, Type: PERMISSION_PRESET. Content is YAML:

allow:
  - Bash(git status *)
  - Bash(git commit *)
  - Bash(git push *)
deny:
  - Bash(git reset --hard *)
  - Bash(git clean -f *)

Hook​

Type: HOOK. Content is a Claude Code hook manifest — see Registry Resources for which event/handler combinations are valid:

hooks:
  Stop:
    - hooks:
        - type: command
          command: 'cd "${CLAUDE_PROJECT_DIR}" && ./mvnw test -q'
          timeout: 900
          statusMessage: Running Java verification

The console validates this before letting you publish — an unsupported event/handler combination is rejected with a clear message before it can reach a run.

MCP Server​

For a real, vendor-hosted MCP server, choose Source type External Reference in the Publish dialog instead of Inline — no content, just a small metadata form: Provider (e.g. github), the server URL, and any headers it needs.

Plugin (Claude Code Marketplace)​

Choose Source type Claude Marketplace. Enter the plugin name and the marketplace it comes from (e.g. frontend-design from claude-plugins-official), then click Check availability. At run time the worker installs or resolves the selected version when package installers are enabled; otherwise the plugin must already be available on that worker.

Knowledge​

Type: KNOWLEDGE, Source type Inline, Content is a reference document such as team conventions, a glossary, or an architecture note. Select its published key@version from the Agent Profile's Knowledge picker and choose whether it is required.

Next​

With skills, hooks, plugins, and presets in the registry, wire them together into a role: Create an Agent Profile.