CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openmeld-cli

Official public OpenMeld Skill for agents using the `openmeld` CLI to consult the Center Agent, set up OpenMeld, connect local agents, create or request Agent Profiles, work in Organizations and Spaces, observe or stop Wakes, trace delivery, and repair local state.

Quality

78%

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/openmeld-cli/skills/openmeld-cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, well-checkpointed operational guide whose commands and error-recovery rules are concrete and executable. Its weaknesses are duplicated rule statements that could be tightened and a router structure whose playbook references mostly point at files missing from the bundle.

Suggestions

Ship the five missing `playbooks/*.md` files (space-reads, space-ops, agent-onboarding, plugins, computer) or repoint those references to files that exist, so the router's topic map resolves.

Deduplicate repeated rules: state the add-me no-profile-search rule and the `$OPENMELD_SPACE_ACTION_TOOL_COMMAND_PATH` fallback command once each instead of twice.

Move the detailed computer cloud operation semantics (invocationId/key stability, syncPending handling, worktree guidance) into `playbooks/computer.md` and keep only the health-check commands inline, reducing router token load.

DimensionReasoningScore

Conciseness

The body is dense with product-specific, non-inferable rules (e.g. "syncPending means the process exited but file synchronization is unconfirmed"), but includes clear redundancy: the add-me no-search rule is stated twice ("must not search all existing profiles for a possible match" and later "Do not run a Profile search before an ordinary add-me"), and the "$OPENMELD_SPACE_ACTION_TOOL_COMMAND_PATH" command is spelled out nearly verbatim twice. This fits the 3 anchor (mostly efficient but could be tightened) rather than 4, where over-explanation would be only minor.

3 / 5

Actionability

Commands are copy-paste ready with exact flags across all common cases — full read command blocks ("openmeld space history \"<space-url-or-id>\" --profile <profile-id> --kind text --brief --limit 20 --view agent"), add-me with "--project-folder \"$(pwd)\"", and worked cloud operations including JSON payloads and paired start/poll examples. Fits the 5 anchor (fully executable, specific examples cover common cases); not 4 since even retry/poll semantics are concretely exemplified.

5 / 5

Workflow Clarity

Explicit conditionals and recovery checkpoints appear throughout: "if it is unknown, run `openmeld profiles list --view agent` and rerun the same read with explicit --profile", "If a Space Action fails, preserve the full error and stop", "Continue polling unless `syncError` or `nextAction: inspect` is present", and "Diagnose before repair". Fits the 4 anchor (clear sequence, most checkpoints present); not 5 because key flows dead-end into playbook files absent from the bundle and there is no consolidated end-to-end sequence.

4 / 5

Progressive Disclosure

The router design is well executed — "This file is a router: start here, then read only the one topic file needed", "Do not preload every file", with a clearly signaled one-level-deep topic map — but scored against the actual bundle, 5 of 7 referenced paths (all `playbooks/*.md`: space-reads, space-ops, agent-onboarding, plugins, computer) do not exist; only `references/commands.md` and `references/runtime-resolution.md` resolve. This fits the 3 anchor (structure present but undermined) rather than 4, since unresolvable references are more than a minor organization gap, and not 2, since the inline content is not an inappropriately monolithic dump and existing references are real and clearly signaled.

3 / 5

Total

15

/

20

Passed

Description

75%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 highly specific, distinctive description that comprehensively enumerates the CLI's capabilities in third person. Its main weakness is the absence of an explicit "Use when..." trigger clause, leaving the activation condition only weakly implied.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to set up, sign in to, or operate OpenMeld, work in Spaces or Organizations, wake or stop Agent Profiles, or trace message delivery."

Add natural trigger terms the body covers but the description omits, such as "sign in", "install", "connect local agents", "plugins", and "add a teammate to a Space".

DimensionReasoningScore

Specificity

Enumerates eight concrete actions — "consult the Center Agent, set up OpenMeld, connect local agents, create or request Agent Profiles, work in Organizations and Spaces, observe or stop Wakes, trace delivery, and repair local state" — comprehensively covering the CLI's surface. This fits the 5 anchor (multiple specific concrete actions, comprehensive coverage) better than 4, whose coverage has minor gaps.

5 / 5

Completeness

The "what" is explicit via the action list, but the only "when" signal is the scope qualifier "for agents using the `openmeld` CLI to", which weakly implies rather than states the trigger; per the rubric guideline, a missing "Use when..." clause caps completeness at 3. Not 4 because no explicit trigger guidance exists.

3 / 5

Trigger Term Quality

Contains strong natural domain terms users would say ("openmeld CLI", "Center Agent", "Agent Profiles", "Organizations and Spaces", "Wakes", "trace delivery"), matching the 4 anchor (good coverage, a few natural terms missing) — e.g. "sign in", "install", "plugins", and "add teammate" from the body are absent. Not 5 because it offers no synonyms or variations beyond the core product nouns.

4 / 5

Distinctiveness Conflict Risk

Unique product vocabulary ("OpenMeld", "Center Agent", "Wakes", "Agent Profiles") creates a clear niche with minimal conflict risk against other skills, matching the 5 anchor. Not 4 because no closely related skill would plausibly overlap these triggers.

5 / 5

Total

17

/

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

amplifthq/opentag

Path

clients/openmeld-cli/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.