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

76%

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/12/SKILL.md

The canonical home for this skill is openmeld-cli in amplifthq/opentag

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 disciplined, information-dense router skill: lean product-specific rules, a clearly sequenced workflow with explicit validation and retry loops, and concrete flag-level guidance. Its main structural weakness is bundle completeness — five of the seven referenced playbooks are missing from the local bundle and only resolve through the external openmeld.ai entry.

Suggestions

Ship the five playbooks/*.md files in the skill bundle alongside references/ so 'follow relative links from this folder' works locally without depending on the external openmeld.ai host.

Move the '0.3.238 or later' CLI version requirement into a dedicated compatibility note so time-sensitive details do not sit in the main reading flow.

Untangle the most compressed sentences (e.g. 'Ask only when the choice changes the audience, acting identity, target, timing, or scope and context cannot resolve it') into two shorter, separate rules.

DimensionReasoningScore

Conciseness

Nearly every sentence carries product-specific operational rules Claude could not know ('A Profile is who acts; --view agent is structured output, not identity', 'Submission is not completion; local terminal output is not a published Space reply'), with no padding or explanations of known concepts. Kept from anchor 5 by a version-number requirement ('requires CLI 0.3.238 or later') embedded in the main flow and a few overloaded sentences (e.g. 'Ask only when the choice changes the audience, acting identity, target, timing, or scope and context cannot resolve it') that need re-reading.

4 / 5

Actionability

Provides concrete flag syntax ('--wake <agent-profile-id> executes; --reference <agent-profile-id> adds context; --mention <human-profile-id> notifies a person'), executable checks ('check openmeld --version when a command is missing', 'Use openmeld <command> --help'), a status taxonomy ('saved, submitted, running, awaiting input, completed, stopped, failed'), and a need-to-topic routing table making next steps unambiguous. The copy-paste command detail is delegated to reference files rather than the body, which fits anchor 4's 'concrete commands with minor gaps' rather than anchor 5's fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

The three-step workflow is explicitly sequenced and ends in verification ('Carry out the authorized work and check its result'), reinforced by a dedicated validation section ('Distinguish saved, submitted, running, awaiting input, completed, stopped, and failed... Read the relevant public result before claiming delivery or completion') and an error-recovery feedback loop ('Preserve an uncertain outcome and inspect the existing request before retrying'; 'A missing capability, denied permission, or offline computer calls for its specific next step'). Explicit validation steps plus retry loops match the anchor-5 pattern, exceeding anchor 4's 'minor validation gaps'.

5 / 5

Progressive Disclosure

The routing table is well-signaled and one level deep, and both bundled reference files (references/commands.md, references/runtime-resolution.md) are real and substantive. But measured against the actual bundle, 5 of the 7 referenced paths (all playbooks/*.md: space-reads, space-ops, center-agent, plugins, agent-onboarding) are absent locally and resolve only via the external public URL, so 'follow relative links from this folder' fails for most topics — a gap beyond anchor 4's 'minor organization gaps', though the strong structure and working public fallback keep it above the minimal-structure anchors.

3 / 5

Total

16

/

20

Passed

Description

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

Explicit, well-targeted trigger guidance with highly distinctive product vocabulary, but the description is all 'when' and no 'what' — it never states what OpenMeld actually is or does, leaving capabilities to be inferred from the enumerated needs. One up-front capability sentence would lift both completeness and specificity.

Suggestions

Open with an explicit 'what' clause before the triggers, e.g. 'OpenMeld gives local agents access to an Organization's shared resources — Spaces, files, Skills, a cloud Center Agent, and Agents on connected computers.'

Convert need-noun phrases into concrete action verbs users can match against their request: 'Consult the Center Agent, read and send Spaces, delegate work to other Agents, upload Team/My files, schedule cloud routines.'

Add natural trigger synonyms users actually say: 'sign in / connect this computer', 'Team files / My files', 'routines', 'delegate'.

DimensionReasoningScore

Specificity

Enumerates concrete capability areas ('Organization knowledge or Skills, Center Agent help, shared Spaces or Files, another Agent or computer, or scheduled cloud work', 'OpenMeld setup and Wake replies') beyond a bare domain label, but the only stated action is the generic 'Use OpenMeld' — no verbs describe what the tool actually does. This sits between anchor 2 (domain named, actions minimal) and anchor 4 (several specific actions), matching anchor 3's 'domain and 1-2 concrete actions, not comprehensive' with setup and Wake replies as the quasi-actions.

3 / 5

Completeness

The 'when' is explicit and multi-triggered ('Use OpenMeld when a task needs...', 'Also use for...'), but the 'what' is never stated — no clause says what OpenMeld is or does, so capabilities are only implied by the enumerated needs. This mirrors anchor 3's one-clear/one-weak pattern (there: clear what, weak when) rather than anchor 4, which requires both explicitly; it is above anchor 2 because the 'when' is rich and specific, not vague like 'Use when working with documents'.

3 / 5

Trigger Term Quality

Covers the product vocabulary an OpenMeld user would naturally say — 'Center Agent help', 'shared Spaces or Files', 'another Agent or computer', 'OpenMeld setup', 'Wake replies' — which is good keyword coverage mapping to real user phrasings. A few natural terms are missing (Team/My Files, routines, sign in/connect, delegate), so it does not reach anchor 5's comprehensive synonym coverage; it is clearly above anchor 3's single-keyword level.

4 / 5

Distinctiveness Conflict Risk

Dominated by product-specific terms ('OpenMeld', 'Organization knowledge', 'Center Agent', 'Spaces', 'Wake') that no other skill would claim, creating a clear niche with distinct triggers and minimal conflict risk. The semi-generic 'Skills' and 'another Agent' carry only trivial overlap potential, not enough to drop to anchor 4's 'minor overlap risk with closely related skills' since no closely related skill shares this vocabulary.

5 / 5

Total

15

/

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/12/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.