---
name: Capability Creator
slug: capability-creator
category: AI Engineering
description: Capability Creator bundles one or more skills and the integrations they need into a single named, installable workspace capability. Use it when the user wants to create a capability that delivers a specific outcome across tools and platforms.
github: "https://github.com/holaboss-ai/holaOS/tree/main/runtime/harnesses/src/embedded-skills/capability-creator"
language: TypeScript
stars: 7387
forks: 641
install: "npx degit https://github.com/holaboss-ai/holaOS/tree/main/runtime/harnesses/src/embedded-skills/capability-creator ~/.claude/skills/capability-creator"
installs_to: ~/.claude/skills/capability-creator
source_path: runtime/harnesses/src/embedded-skills/capability-creator/SKILL.md
collection_size: 25
category_size: 2451
collection_url: "https://dirskills.com/collections/holaboss-ai/holaOS"
added: 2026-08-15T06:51:36.533Z
last_synced: 2026-08-15T06:51:36.533Z
canonical_url: "https://dirskills.com/skills/capability-creator"
---

# Capability Creator

Capability Creator bundles one or more skills and the integrations they need into a single named, installable workspace capability. Use it when the user wants to create a capability that delivers a specific outcome across tools and platforms.

**Install:**

```bash
npx degit https://github.com/holaboss-ai/holaOS/tree/main/runtime/harnesses/src/embedded-skills/capability-creator ~/.claude/skills/capability-creator
```

## README

# Capability Creator

A capability bundles one or more skills and the integrations they need into one
named, installable unit. Use this when the user wants to create a capability.

## Workflow
1. Clarify the outcome the capability should deliver and which platforms it touches.
2. Ensure each skill it needs exists under `skills/<skill-id>/`. Create any
   missing skill with the skill-creator guidance first.
3. Write the manifest to `capabilities/<capability-id>/capability.yaml` at the
   workspace root. Reference existing skills by `ref` (do not copy them). Declare
   each external service the capability needs under `integrations`.
4. Call the `capability_install` tool with `capability_id: <capability-id>`.
5. Report the result. If an integration comes back `needs_connection`, tell the
   user which one to connect.

## Manifest format

```yaml
id: <capability-id>            # must match the directory name
name: <Readable Name>
description: <one line>
version: 0.1.0
skills:
  - ref: <existing-skill-id>   # reference a workspace skill by id
integrations:
  - provider: <provider-id>    # e.g. linkedin, gmail, twitter
    required: true
    reason: <why this capability needs it>
agent_prompt: |
  <short guidance appended to AGENTS.md describing when/how to use this capability>
```

Keep the manifest minimal. Prefer `ref` skills over embedding `path` skills.