customize-capability
/customize-capability
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.
- Author
- holaboss-ai ↗
- Repository
- holaos ↗
- Licence
- Apache-2.0
- Last repository change
- 21.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 21.08.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Original author 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.
How it works
- Workflow
- Adding an MCP server
- After installing
SKILL.md preview
---
name: customize-capability
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.
---
# 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):
```yaml
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):
```yaml
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.
Versions
The database has no other skills named customize-capability.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 48cd07b9c1e0 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100capability-creator
Guide for assembling a workspace capability (skills + integrations). Use when the user wants to create a capability. - 100self-customize
Customize your own agent — add capabilities, install packages, add MCP servers, edit code or CLAUDE.md. Use when the user asks you to add a feature, install a tool, or modify how you work. For non-trivial code changes, delegate to a builder agent via create_agent. - 100bmad-customize
Authors and updates customization overrides for installed BMad skills. Use when the user says 'customize bmad', 'override a skill', 'change agent behavior', or 'customize a workflow - 90configure-mcp
Check and configure MCP servers for project integration. Use when setting up MCP servers, checking MCP status, or adding new servers to a project. - 100self-customize
Customize your own agent — add capabilities, install packages, add MCP servers, edit code or AGENTS.md. Use when the user asks you to add a feature, install a tool, or modify how you work. For non-trivial code changes, delegate to a builder agent via create_agent. - 100capability
Search, compare, vet, understand, adopt, and guide agent capabilities such as skills, CLIs, MCP servers, and libraries. Use when someone needs candidates, a tool comparison, a security check before install, a deep tool brief, a verified install, or a durable tool guide.