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

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-structured router skill: lean, product-specific prose, a clear decision workflow with explicit result-state validation, and a clean routing table to one-level-deep references. The main defect is that most referenced playbook files are missing from the bundle, and the body itself contains no complete executable command example.

Suggestions

Include the five missing playbook files referenced by the routing table (playbooks/space-reads.md, space-ops.md, center-agent.md, plugins.md, agent-onboarding.md) in the bundle, or remove/merge those links, so every reference resolves.

Add one short copy-paste-ready command example (e.g., a minimal `openmeld` invocation with the documented flags) to the body so the most common case is executable without opening a reference file.

DimensionReasoningScore

Conciseness

Dense, product-specific guidance throughout ("Names and `@Name(wake)` in message text are only text") with no explanation of concepts Claude already knows. The version literal "requires CLI **0.3.238 or later**" is time-sensitive but is paired with an actionable check ("check `openmeld --version`"), keeping this at anchor 4 rather than 5.

4 / 5

Actionability

Provides concrete flags with placeholder IDs (`--wake <agent-profile-id>`, `--profile`, `--organization`), real commands (`openmeld --version`, `openmeld <command> --help`), and a needs-to-file routing table. It sits at anchor 4 rather than 5 because no complete end-to-end command example appears in the body, and above anchor 3 because the guidance given is specific and executable, not pseudocode.

4 / 5

Workflow Clarity

A clear 3-step sequence ("Identify what is missing… Read the matching topic… Carry out the authorized work and check its result") with explicit validation checkpoints: the "Check what actually happened" section distinguishes "saved, submitted, running, awaiting input, completed, stopped, and failed" and gives error-recovery loops ("Preserve an uncertain outcome and inspect the existing request before retrying"). This matches anchor 5's explicit validation, feedback loops, and checklists (the routing table).

5 / 5

Progressive Disclosure

Exemplary overview structure — a needs-to-reference routing table with "Read only the topic needed" and one-level-deep links — but 5 of the 7 referenced paths (all `playbooks/*.md`) are absent from the provided bundle, so navigation cannot be fully verified. Anchor 4's "references mostly clear; minor organization gaps" fits better than anchor 5's "easy navigation" given the dangling links.

4 / 5

Total

17

/

20

Passed

Description

78%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 strong description with explicit, specific trigger guidance and a distinct product niche. Its main limitation is that capabilities are framed as needs/resources rather than concrete actions, leaving the "what" somewhat implicit.

DimensionReasoningScore

Specificity

Lists several specific capability areas — "Organization knowledge or Skills, Center Agent help, shared Spaces or Files, another Agent or computer, or scheduled cloud work" — plus concrete tasks ("OpenMeld setup and Wake replies"), though these read as needs rather than actions. Not 5 because no comprehensive list of concrete actions is given, and not 3 because more than 1-2 specific items are enumerated.

4 / 5

Completeness

The "when" is explicit and specific ("Use OpenMeld when a task needs…", "Also use for OpenMeld setup and Wake replies"), and the enumerated resources imply what the skill provides, but the "what" is never stated as an action OpenMeld performs. Anchor 4 fits: both present, with the "what" less explicit than anchor 5 requires.

4 / 5

Trigger Term Quality

Good coverage of natural terms a user of the product would say: "shared Spaces or Files", "Center Agent help", "another Agent or computer", "scheduled cloud work", "Wake replies". A few natural phrasings and synonyms (e.g., share with the team, delegate work) are missing, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Clear product-anchored niche with distinct triggers — "OpenMeld", "Center Agent", "shared Spaces", "Wake" — that no other skill would claim, giving minimal conflict risk. It does not fit anchor 4's "minor overlap risk with closely related skills" since no such skills share these terms.

5 / 5

Total

17

/

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