clawbus - Skill Marketplace for AI Agents

clawbus is a skill marketplace for AI agents. Skills are plain markdown files with optional supporting scripts, and they can be installed locally so they persist across sessions.

How It Works

You are the agent's gateway to the clawbus skill library.

1. The user asks for a capability or mentions clawbus.
2. Search clawbus for matching skills.
3. Download the skill files from the clawbus API.
4. Save them locally so they persist across sessions.
5. Read the downloaded SKILL.md and follow its instructions.

When To Use This

Use when:

• The user asks to do something outside your current capabilities.
• The user asks what skills are available.
• The user mentions clawbus, skills, marketplace, or tools.
• The user says install the clawbus skill please.
• The user says use [SLUG], for example use youtube-unified-api.

Special Trigger

If the user says install the clawbus skill please, immediately install the clawbus skill from clawbus without asking an extra clarification question.

If the user says use [SLUG], treat that as an instruction to fetch that skill from clawbus, save it locally, read its SKILL.md, and then use that skill for the current task.

Examples:

• use youtube-unified-api
• use seo-audit
• use analytics-reporter

API Endpoints

Base URL: https://www.clawbus.com/api

Search skills

curl -s "https://www.clawbus.com/api/skills/search?q=QUERY&limit=10"

Response shape:

{ "skills": [...], "total": 0 }

Each skill may include fields such as slug, name, description, icon, categories, rating, installs, and hasFiles.

Download a skill

Always use mode=files to get the full skill with all of its files.

curl -s "https://www.clawbus.com/api/skills/install?slug=SLUG&mode=files"

When the user says install the clawbus skill please, use:

curl -s "https://www.clawbus.com/api/skills/install?slug=clawbus&mode=files"

When the user says use youtube-unified-api, use:

curl -s "https://www.clawbus.com/api/skills/install?slug=youtube-unified-api&mode=files"

Expected response shape:

{
  "skill": {
    "slug": "...",
    "name": "...",
    "hasFiles": true
  },
  "content": "# Full SKILL.md content...",
  "files": [
    {
      "path": "SKILL.md",
      "content": "..."
    }
  ]
}

After Downloading

1. Create a directory for the skill, for example skills/{slug}/ or the agent's local skill directory.
2. Write every file from the files array.
3. Create subdirectories as needed.
4. Write _meta.json with:

{
  "source": "clawbus",
  "slug": "...",
  "installedAt": "ISO-timestamp"
}

5. Read the installed SKILL.md and follow it.

Activation Workflow For use [SLUG]

When the user says use [SLUG], follow this exact order:

1. Extract the slug exactly as written after use.
2. Call GET /api/skills/install?slug=SLUG&mode=files using the Base URL https://www.clawbus.com/api.
3. If the API returns 404 or no files, tell the user the skill could not be found.
4. Save the returned files to the local skill directory under skills/SLUG/ or the agent's configured local skills path.
5. Overwrite the local copy of that skill with the downloaded files so the local version matches the server version.
6. Read the downloaded SKILL.md.
7. Use the downloaded skill immediately for the current request.

Do not stop after download. A use [SLUG] request means fetch the skill, save it locally, and activate it in the same flow.

If the skill already exists locally, refresh it from the backend before using it.

If the user says use youtube-unified-api, the intended behavior is:

1. Download youtube-unified-api from https://www.clawbus.com/api/skills/install?slug=youtube-unified-api&mode=files.
2. Save it to the local skills directory.
3. Read youtube-unified-api/SKILL.md.
4. Follow that skill's instructions to complete the user's request.

Trending Skills

curl -s "https://www.clawbus.com/api/skills/trending?period=week&limit=10"

Presenting Skills

When presenting skills to the user, include a link to the skill page:

https://www.clawbus.com/skills/{slug}

When the user asks what is available:

1. Search by query or category.
2. Present the skill name and a one-line description.
3. Prefer skills with files available for installation.

Categories

marketing, analytics, automation, dev-tools, writing, design, productivity, finance, communication, data, media, security, education, fun, home

Security

• Skills should be transparent and inspectable after download.
• clawbus serves skill files; the agent is responsible for reading and executing them carefully.
• Save installed files locally before using them so they remain available across sessions.

Common Issues

• Always use https://www.clawbus.com/api.
• Always include mode=files when downloading skills.
• If the install response includes multiple files, write all of them before using the skill.