CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openmeld-cli

Use OpenMeld when a task needs Organization knowledge or Skills, Center Agent help, shared Spaces or Files, another Agent or computer, or scheduled cloud work. Also use for OpenMeld setup and Wake replies.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./clients/web/public/skills/openmeld-cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

A tightly written, policy-focused overview with a clear workflow sequence and an unusually strong validation section. Its effectiveness is undermined by the bundle itself: five of the seven linked playbooks are missing, so most routing-table topics dead-end and the executable recipes they promise are unavailable.

Suggestions

Add the missing playbooks/ files (space-reads.md, space-ops.md, center-agent.md, plugins.md, agent-onboarding.md) or repoint those routing-table rows to files that exist — 5 of 7 links currently dead-end.

Include at least one complete example invocation in the body (e.g. a full 'openmeld space send' or 'center-agent ask' command with realistic IDs) so a reader can execute a workflow without depending on a missing reference file.

Move the CLI version requirement ('0.3.238 or later') into a dedicated compatibility note rather than the main flow, so the body does not age as the CLI advances.

DimensionReasoningScore

Conciseness

Dense, policy-only prose with no padding and no explanation of concepts Claude already knows; every section carries OpenMeld-specific rules ('A Profile is who acts; --view agent is structured output, not identity'). It falls short of anchor 5 because the inline version pin ('This guide requires CLI 0.3.238 or later') is time-sensitive information placed in the main flow rather than a compatibility or deprecation section.

4 / 5

Actionability

Real flags and subcommands appear ('--wake <agent-profile-id>', '--profile', '--organization', 'openmeld <command> --help', 'space send'), but the body contains no complete executable invocation and delegates recipes to reference files — 5 of the 7 linked files (all playbooks/*.md) are absent from the bundle, so the executable detail is unreachable for most topics. It is above anchor 2 because the flag semantics and decision rules are concrete and specific, but below anchor 4 because a reader cannot execute a full workflow from what is actually available.

3 / 5

Workflow Clarity

'Choose the smallest useful workflow' gives a clear 3-step sequence (identify what is missing, read the matching topic, carry out and check the result), and 'Check what actually happened' is an explicit validation section with state distinctions ('Submission is not completion') and a retry protocol ('Preserve an uncertain outcome and inspect the existing request before retrying'). It misses anchor 5 because the Wake-handling path defers its steps to the missing space-ops playbook, leaving a checkpoint gap on that branch.

4 / 5

Progressive Disclosure

The routing table is well-designed (need-to-file mapping, one level deep, 'Read only the topic needed') and the two references that exist (references/commands.md, references/runtime-resolution.md) are real and on-topic. However, 5 of the 7 referenced paths (playbooks/space-reads.md, space-ops.md, center-agent.md, plugins.md, agent-onboarding.md) do not exist in the bundle, so navigation resolves for only a minority of topics — better organized than anchor 2's minimal structure, but short of anchor 4's 'most content appropriately placed'.

3 / 5

Total

14

/

20

Passed

Description

73%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.

A distinctive, well-triggered description with explicit 'use when' guidance and broad coverage of OpenMeld's resource surface. Its main weakness is that capabilities are named as resource categories ('Organization knowledge', 'Center Agent help') rather than concrete actions, leaving the 'what it does' partially implicit and relying entirely on product vocabulary for triggers.

Suggestions

State 2-3 concrete actions the CLI performs (e.g. 'read Space history and members, send messages to other Agents, schedule cloud Routines') instead of naming resource categories alone.

Add plain-language trigger synonyms alongside the product terms (e.g. 'delegate work to another Agent', 'shared team files', 'run a task later') so users unfamiliar with OpenMeld vocabulary still match.

DimensionReasoningScore

Specificity

Enumerates six-plus capability areas ('Organization knowledge or Skills, Center Agent help, shared Spaces or Files, another Agent or computer, or scheduled cloud work') but the verbs stay generic ('needs', 'help', 'setup') and no concrete actions are stated. It is above anchor 2 because it goes well beyond a bare domain mention, but below anchor 4 because it never says what the skill actually does with those resources.

3 / 5

Completeness

The 'when' is explicit and strong ('Use OpenMeld when a task needs...', 'Also use for OpenMeld setup and Wake replies'), while the 'what' is conveyed only indirectly through the enumerated resources rather than a direct statement of function. Both are present, matching anchor 4 rather than 3 (the 'when' clause is explicit) and falling short of 5 (the 'what' is not stated as concrete actions).

4 / 5

Trigger Term Quality

Good coverage of the product's natural trigger terms: 'Center Agent help', 'shared Spaces or Files', 'another Agent or computer', 'scheduled cloud work', 'OpenMeld setup', 'Wake replies'. It falls short of anchor 5 because every term is the product's canonical name with no plain-language synonyms or variations (e.g. 'delegate work', 'shared team files', 'run a task later').

4 / 5

Distinctiveness Conflict Risk

Every trigger is an OpenMeld-specific product concept ('Center Agent', 'Spaces', 'Wake', 'OpenMeld setup'), so no other skill would match these terms. This is a clear niche with distinct triggers and minimal conflict risk, matching anchor 5.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 missing

Warning

Total

15

/

16

Passed

Repository

amplifthq/opentag

Path

clients/web/public/skills/openmeld-cli/SKILL.md

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.