Skip to content

Feature: Skills and Prompts

Jump to bottom
Claude Agent edited this page Jul 6, 2026 · 1 revision

Skills and Prompts

The Skills & Prompts feature in the OSC Builders section lets you publish reusable AI skills, prompts, and runbooks to the platform. Once published, they can be shared with other teams or discovered via the OSC MCP server.

What You Can Contribute

  • Skill — a Claude Code slash command (.md file) that an AI agent can invoke
  • Prompt — a reusable natural language instruction or system prompt
  • Runbook — a step-by-step operational guide intended for AI-assisted execution

Each contribution is stored as a public Gitea repository under your workspace's namespace and is versioned using semantic versioning tags.

Prerequisites

  • An OSC account (any plan)
  • A Builders workspace (available to all contributors listed in the Creator section)

Contributing a Skill or Prompt

Via Web Console

  1. Navigate to Builders in the OSC web console
  2. Click the Skills & Prompts tab
  3. Click Contribute
  4. Fill in the form:
    • Name — a slug (lowercase alphanumeric and hyphens), unique per workspace
    • Type — Skill, Prompt, or Runbook
    • Description — a short description of what it does
    • License — MIT, Apache 2.0, or CC-BY 4.0
    • Content — the Markdown or YAML content of your skill or prompt
  5. Click Contribute to publish

After submission, a share URL is shown that links directly to the Gitea repository for the contribution. Copy it to share with others.

Via MCP (AI Agent)

You can list skills published in your workspace:

list-published-skills

And fetch the content of a specific skill:

get-published-skill
  name: "my-skill"

The shareUrl in the response links to the public Gitea repository. The cloneUrl can be used to clone the repository locally.

Licensing

Choose the license that matches how you want others to use your contribution:

License Summary
MIT Permissive — anyone can use, modify, and redistribute
Apache 2.0 Permissive with patent grant
CC-BY 4.0 Requires attribution — suitable for documentation and prompts

Versioning

After publishing, you can tag a specific version of your contribution using the deploy-manager API. Tags follow the semver convention (e.g. v1.0.0, v1.1.0). The Gitea repository for each contribution tracks full revision history.

Related Resources

  • Creator — How to become a builder on OSC
  • Feature: My Agent Tasks — Scheduling AI agent tasks that can use published skills
  • Developer Guide: Overview — Building and publishing applications on OSC

Clone this wiki locally