Skip to content
cccskills
FreePublished on GitHub

customize-capability

Customize an installed workspace capability, a bundle of agent tools and guidance. It updates the configuration to add MCP servers, which connect agents to tools, or change skills, integrations, and instructions while preserving existing settings.

OriginalShow the original description

Guide for modifying an already-installed workspace capability — adding or editing its MCP servers, skills, integrations, or agent guidance. Use when the user wants to customize, change, or extend an existing capability.

See how to install

Good for

  • Add an MCP server to an installed capability
  • Update existing skills and integrations
  • Revise instructions for a capability's agent
  • Extend a catalog capability while keeping its settings

Files included (1)

  • SKILL.md3.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Customize Capability

Modify a capability that is already installed in this workspace. The most common request is giving it an MCP server so its agent gains new tools, but the same flow covers adding skills, integrations, or guidance.

A capability's source of truth is its manifest at capabilities/<capability-id>/capability.yaml. Re-installing reads that manifest and upserts the capability — re-install IS the update mechanism, and it never creates a duplicate.

Workflow

  1. Identify the capability id from the user's request.
  2. Read the current state:
    • If capabilities/<capability-id>/capability.yaml exists, edit it in place.
    • If it does NOT exist (the capability was installed from the catalog), create it. Reconstruct the existing config first so nothing is dropped: keep the capability's current skills (as ref), its integrations, and its agent_prompt, then add your change on top.
  3. Apply the change (see "Adding an MCP server" for the common case).
  4. Call the capability_install tool with capability_id: <capability-id>. It re-reads the manifest and upserts the capability. A malformed manifest is rejected with a precise error — fix and retry.
  5. Tell the user the change takes effect on the next agent run: the runtime compiles MCP servers at run start, so the current run won't see the new tools. Ask them to send a new message to pick them up.

Adding an MCP server

Add an mcp: block to the manifest. Each server connects the capability's agent to an MCP endpoint and exposes the tools you list.

Remote server (an HTTP/SSE MCP endpoint):

mcp:
  servers:
    - id: x                              # letters/digits/_/-, unique in this capability
      type: remote
      url: https://mcp.example/sse
      headers:                           # optional — e.g. auth
        Authorization: Bearer <token>
      tools: [create_post, list_posts]   # which tools to expose (required, ≥1)

Local server (a subprocess speaking MCP over stdio):

mcp:
  servers:
    - id: helper
      type: local
      command: [npx, "-y", "@modelcontextprotocol/server-everything"]
      environment:                       # optional
        SOME_TOKEN: "{env:SOME_TOKEN}"   # reads from the runtime environment
      tools: [echo, add]

Rules:

  • tools must list at least one tool name — you declare exactly which tools to expose.
  • Remote servers require url; local servers require command.
  • Put auth in headers (remote) or environment (local). Both header and environment values may use {env:VAR_NAME} to read from the runtime environment instead of hard-coding secrets.
  • Ask the user for the server url/command, which tools to expose, and any auth before writing the manifest.

The exposed tools become available to the capability's agent on the next run.

After installing

Confirm what you changed and remind the user to start a new message so the agent picks up the new MCP tools.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

app-builder-sdk

FreeSummary

Build holaOS apps for connecting external services or managing work through a dashboard. The skill uses shared SDK building blocks for stored records, actions, and synchronization, with the dashboard and agent tools working on the same data.

  • Building an external service integration
  • Creating a CRM dashboard
  • Building a content planning workspace
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

audience-analyst

FreeSummary

Analyze audience demographics and engagement to identify distinct groups, understand what they want, and prioritize valuable segments. Turn those findings into recommendations for content topics, formats, posting times, and tone, while explaining limits in the data.

  • Identify distinct groups within an audience
  • Prioritize groups that engage or convert
  • Plan topics and formats for each audience group
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

Guide an agent through efficient use of an embedded browser by choosing targeted actions, searches, and waits. Reduce repeated tool calls and unnecessary page snapshots, while using more detailed inspection when the target or result remains unclear.

  • Act on known buttons or fields with fewer browser calls
  • Locate a known target on a large page
  • Wait for navigation or downloads to finish
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

browser-qa

FreeSummary

Validate workflows and reproduce issues in an embedded browser. Distinguish application problems from incorrect targets, missing waits, or session state, then report the shortest reliable reproduction steps with only the evidence needed to support the finding.

  • Reproducing a browser workflow failure
  • Checking for regressions after a fix
  • Distinguishing timing issues from application failures
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

build-dashboard

FreeSummary

Build the user interface for a holaOS app whose data resources are already connected through the SDK. Choose a feed, table, kanban board, form, or calendar layout using shared components and workspace styling.

  • Display scheduled items in a chronological feed
  • Show CRM contacts or tickets in a table
  • Organize issues by status on a kanban board
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

Package workspace skills and their required service integrations into one named, installable capability. Create a manifest that references existing skills, install the capability, and report which integrations still need to be connected.

  • Bundle multiple skills for a shared outcome
  • Declare required external service integrations
  • Create a manifest that references existing skills
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

See all skills by holaboss-ai

Report a problem with this skill