Guide for assembling a workspace capability (skills + integrations). Use when the user wants to create a capability.
63
74%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./runtime/harnesses/src/embedded-skills/capability-creator/SKILL.mdA 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.
skills/<skill-id>/. Create any
missing skill with the skill-creator guidance first.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.capability_install tool with capability_id: <capability-id>.needs_connection, tell the
user which one to connect.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.
4684714
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.