CtrlK
BlogDocsLog inGet started
Tessl Logo

capability-creator

Guide for assembling a workspace capability (skills + integrations). Use when the user wants to create a capability.

63

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a lean, actionable instruction sheet: a clear sequenced workflow, a copy-paste manifest template with useful inline comments, and an explicit error-handling step. Its only gaps are the absence of a worked example and a manifest validation checkpoint before install.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanations of concepts Claude already knows: a 5-step workflow, a commented YAML manifest template, and one closing preference note — every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

The manifest template is copy-paste ready with informative inline comments ("# must match the directory name", "# e.g. linkedin, gmail, twitter") and the workflow names a concrete tool invocation ("Call the `capability_install` tool with `capability_id: <capability-id>`"), but there is no fully worked example manifest showing a completed case, keeping it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The five steps are clearly sequenced (clarify outcome, ensure skills exist, write manifest, call capability_install, report result) and step 5 handles the `needs_connection` error path, but there is no validation checkpoint on the manifest itself before install (e.g. confirming id matches the directory), so it fits anchor 4 rather than the explicit-validation anchor 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (none of references/, scripts/, or assets/ exist and the body cites none), and its two sections (Workflow, Manifest format) are well-organized — per the rubric's simple-skill guideline this earns a 5.

5 / 5

Total

18

/

20

Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description cleanly answers both what and when in third person with a distinct niche term, but it is thin: one action verb, one trigger phrase, and no synonyms or related trigger terms a user might naturally say. It sits comfortably in the middle of the quality range.

Suggestions

Enumerate concrete actions instead of the single verb 'assembling', e.g. "Write capability manifests, bundle workspace skills by ref, declare integrations, and install capabilities with the capability_install tool."

Broaden trigger coverage with natural synonyms, e.g. "Use when the user wants to create, build, bundle, or install a capability (a named unit of skills + integrations)."

Add a distinguishing cue against adjacent skills, e.g. mention that individual skill creation is handled by skill-creator and this skill is for multi-skill installable bundles.

DimensionReasoningScore

Specificity

"Guide for assembling a workspace capability (skills + integrations)" names the domain and its concrete constituents (skills, integrations) but relies on a single generic action verb ("assembling") without enumerating several specific actions, matching the 'domain and 1-2 concrete actions' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

Both parts are present: the what ("Guide for assembling a workspace capability (skills + integrations)") and the when ("Use when the user wants to create a capability"), but the when is a single phrase that could be more explicit with concrete trigger situations, matching anchor 4 rather than the fully-explicit anchor 5.

4 / 5

Trigger Term Quality

"Use when the user wants to create a capability" supplies one natural trigger phrase, but common variations users would actually say ("build", "bundle", "package", "install a capability") and platform/integration terms are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"Capability" plus the parenthetical "(skills + integrations)" carves out a distinct niche with clear triggers, though there is minor overlap risk with generic skill-creation requests; not anchor 5 because a user asking to 'create a skill' or 'add an integration' could plausibly land here too.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
holaboss-ai/holaOS
Reviewed

Table of Contents

Is this your skill?

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.