CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openmeld-cli

Use OpenMeld through its public CLI to work in Spaces, reply to a Wake, consult the Center Agent, connect this computer, manage Agent Profiles, or diagnose delivery.

Quality

75%

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/releases/1/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.

The body is a disciplined, concise router with genuinely actionable safety and identity guidance and explicit validation checkpoints. Its main defects are external: the three playbook files its topic menu points to are missing from the bundle, breaking the skill's core navigation promise, and the pinned CLI version introduces avoidable staleness.

Suggestions

Ship the three missing playbooks/ files (space-reads.md, space-ops.md, agent-onboarding.md) or repoint the 'Choose one topic' menu to files that actually exist — three of the five links are currently dangling.

Drop the pinned "CLI 0.3.159" in favor of the version-check rule alone ("check `openmeld --version` before relying on a newly documented command"), or move the pin to a versioning note, so the requirement does not go stale.

Inline a one-line exact syntax example for the most common action per topic (e.g. the full `openmeld space add-me` invocation) so the body remains actionable even before a playbook is opened.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — product-specific definitions like "A Space is the shared conversation. An Agent Profile is the AI teammate" earn their place — but the pinned "This guide requires CLI 0.3.159 or later" is largely subsumed by the actionable "check `openmeld --version`" rule and is not placed in a deprecation/versioning section, keeping it below the lean anchor 5.

4 / 5

Actionability

Concrete, exact commands appear throughout ("openmeld computer current --brief --view agent", "openmeld space add-me", "openmeld <command> --help") along with precise flag semantics ("Use `--wake` when asking another available Agent to execute; `--reference` only adds context"), but the executable workflows for the most common cases are deferred to topic files, leaving minor gaps.

4 / 5

Workflow Clarity

The routing sequence is explicit ("Read this entry first, then only the topic needed") and validation checkpoints are present rather than implicit ("Verify that the Space received the visible outcome", "Ask before destructive reset, uninstall, or deletion", "check `openmeld --version`"), matching anchor 4; it falls short of 5 because delegated workflow steps point to playbook files that are absent from the bundle.

4 / 5

Progressive Disclosure

The structure is excellent — a "Choose one topic" menu with well-signaled, one-level-deep references and "Do not preload every file" — but scored against the actual bundle, 3 of the 5 referenced paths (playbooks/space-reads.md, playbooks/space-ops.md, playbooks/agent-onboarding.md) do not exist, so navigation fails for most topics, which exceeds the "minor organization gaps" of anchor 4.

3 / 5

Total

15

/

20

Passed

Description

70%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-targeted description built on unique product vocabulary with several concrete actions. Its one real weakness is the absence of any "Use when..." trigger clause, which leaves the "when should this skill be used" half of completeness unanswered.

Suggestions

Add an explicit 'Use when...' clause (e.g., "Use when the user mentions OpenMeld, asks to reply to a Wake, or wants to connect this computer to a Space") to answer the 'when' half of completeness.

Replace the generic "work in Spaces" with the concrete underlying actions (e.g., "read Space history and members, send and reply to messages") to tighten specificity.

Include common user phrasings such as "sign in" or "invite a teammate" to round out natural trigger-term coverage.

DimensionReasoningScore

Specificity

It lists several concrete actions ("reply to a Wake", "consult the Center Agent", "manage Agent Profiles", "diagnose delivery") but a couple remain generic ("work in Spaces" does not say what is done in a Space), matching anchor 4's "several specific actions; minor gaps" rather than the comprehensive coverage of anchor 5.

4 / 5

Completeness

The "what" is clear and multi-part ("Use OpenMeld through its public CLI to work in Spaces, reply to a Wake..."), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms users of this product would say — "Spaces", "Wake", "Center Agent", "Agent Profiles", "connect this computer" — give good keyword coverage, but common phrasings such as "sign in", "send a message", or "invite" are missing, so it sits at anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description is anchored entirely on the proprietary "OpenMeld" name and its unique product nouns ("Wake", "Center Agent", "Agent Profiles"), giving it a clear niche with distinct triggers and minimal conflict risk with any other skill.

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: 3 missing

Warning

Total

15

/

16

Passed

Repository

amplifthq/opentag

Path

clients/web/public/skills/openmeld-cli/releases/1/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.