How to use OpenSkill

Skills, workflows, and recipes

Skills are single, copy-ready prompts (COSTAR-structured). Each skill page offers Copy Full Prompt and optional separate system / user parts for tools that support them.

Workflows are declarative, multi-step maps. Steps may reference skills (AI-assisted) or mark human work. Nothing “runs” on OpenSkill’s servers — you execute the workflow in your own environment.

Recipes are role- or scenario-specific guides that point you to relevant skills and workflows. Treat them as a curated path and checklist, not an executable package.

Four steps (every tool)

1. Pick a workflow or recipe from the site.
2. Read the trigger, steps, or narrative so you know the intent and order.
3. Open linked skills when a step needs AI assistance.
4. Copy prompts with the skill page’s composer, then paste into your chat, project, or bot.

Between steps, reuse inputs and outputs by copying text into a shared doc (Notion, Google Doc) or the next chat turn, as the workflow describes.

Claude (web, app, or Projects)

Use a workflow as a checklist across one long conversation or several focused chats. For each skill step, open the skill in the library, copy the prompt, and paste into Claude. For human steps, do the work outside the model (meetings, approvals, tools).

In Claude Projects, you can paste frequently used skill system prompts into project instructions and keep the workflow page URL as a bookmark for the overall sequence.

Coze and similar builders

Visual workflow builders map naturally to OpenSkill’s step types at a design level:

• Skill steps → LLM / agent nodes whose prompts you fill from the linked OpenSkill skill page.
• Human steps → manual tasks, approvals, or plugin nodes that call non-LLM tools.

Use a recipe as the product brief before you build: which roles, which skills, which workflows, and in what order. OpenSkill does not provide a one-click “import to Coze” button; you copy content and wire nodes yourself.

OpenClaw

OpenClaw is a self-hosted agent runtime with tools and extensible behavior. Conceptually, OpenSkill supplies prompt text and structured workflow metadata you can align with OpenClaw’s skills and planning — how you wire them depends on your OpenClaw version and configuration.

Treat each OpenSkill skill as an instruction block to attach or paste into your agent, and each workflow as an ordered plan the agent or you follow. Refer to OpenClaw’s own documentation for file layout, tools, and memory.

Advanced: JSON bundles

The site serves static exports (for example under openskill.*.json alongside the app) built from the repository. These are for integrations, scripting, and validation, not required for everyday copy-paste use. Clone the repo and run npm run export if you need the same files locally from dist/.

GitHub repository