gabrielmoreira 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
- Clarify the outcome the capability should deliver and which platforms it touches.
- Ensure each skill it needs exists under
skills/<skill-id>/. Create any missing skill with the skill-creator guidance first. - Write the manifest to
capabilities/<capability-id>/capability.yamlat the workspace root. Reference existing skills byref(do not copy them). Declare each external service the capability needs underintegrations. - Call the
capability_installtool withcapability_id: <capability-id>. - Report the result. If an integration comes back
needs_connection, tell the user which one to connect.
Manifest format
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.