CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recall

Thin Codex skill shim for node_recall_compute. Use when querying OmniNode runtime knowledge through the event bus.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/onex/skills/recall/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 actionable and workflow-safe: it provides a real dispatch command, a compile-only validation path, and explicit error semantics, and it stays lean by assuming competence. Its main weaknesses are the duplicated contract metadata between the generated block and the "## Contract" section, the missing concrete payload/response example, and the awkward nesting of the runtime-truth block under "Arguments".

Suggestions

Collapse the duplication between the generated "Runtime truth" block and the "## Contract" section (e.g. have ## Contract point at the generated block or keep only file paths there) to reclaim tokens.

Add one concrete example payload and a trimmed example response (ok true with output_payloads[0], and a node_not_implemented failure) so the dispatch command is copy-paste ready.

Move the generated "Runtime truth" block out from under "## Arguments" into its own top-level section so the arguments table is discoverable immediately under its heading.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes competence (no explanations of known concepts), but the "## Contract" section restates four facts already given in the generated "Runtime truth" block (command name, both topic names, backing node), and the generated block itself repeats binding details. This matches anchor 3 (mostly efficient but could be tightened) rather than 4, since a fully duplicated section is more than minor trimming.

3 / 5

Actionability

The dispatch section gives an executable command with the real wrapper script, environment handling, a --compile-only preflight flag, and explicit error-handling instructions ("surface error.code and error.message directly"), which is mostly executable guidance. Not 5 because the payload is a placeholder ('<json-payload>') and no concrete example payload or example response is shown for the common case.

4 / 5

Workflow Clarity

The single-action workflow is clearly sequenced: run location, map user inputs to payload fields, dispatch via the wrapper, interpret output_payloads[0] or the error, with an explicit validation checkpoint (--compile-only) and an explicit stop state for node_not_implemented. Not 5 because the "## Output" rendering guidance ("Render confidence, sources, partial, and a ranked result summary") is vague and there is no worked example payload to confirm the mapping step.

4 / 5

Progressive Disclosure

The skill is a single well-organized file with clear sections (Arguments, Dispatch, Contract, Output) and no nested references, and referenced paths point to the target repo rather than missing bundle files. Not 5 because the generated "Runtime truth" block with its own ### subsections is nested under "## Arguments" ahead of the arguments table, making that heading misleading, and the Contract/Runtime-truth duplication signals content that could be consolidated.

4 / 5

Total

15

/

20

Passed

Description

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

The description has an explicit and appropriately scoped 'Use when' clause and is highly distinct, but it is written in implementation jargon. It states what the skill is rather than what it does, and its trigger vocabulary is narrow relative to how users would naturally phrase a knowledge query.

Suggestions

Lead with capabilities instead of identity, e.g. "Queries OmniNode runtime knowledge (learnings, architecture, antipatterns) via node_recall_compute over the event bus" so the 'what' states actions rather than what the skill is.

Broaden trigger terms to natural user phrasings: "Use when the user asks to search, look up, or recall runtime knowledge or past learnings".

Drop low-value jargon from the description ("Thin Codex skill shim", "through the event bus") and keep it in the body where it guides implementation.

DimensionReasoningScore

Specificity

The description names the domain ("node_recall_compute", "OmniNode runtime knowledge") and one concrete action ("querying OmniNode runtime knowledge through the event bus"), but the 'what' is mostly stated as implementation identity ("Thin Codex skill shim") rather than a list of capabilities. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, which requires several specific actions.

3 / 5

Completeness

Both parts are present: a 'what' ("Thin Codex skill shim for node_recall_compute") and an explicit 'when' ("Use when querying OmniNode runtime knowledge through the event bus"). Not 5 because the 'what' describes what the skill is in jargon terms rather than clearly stating capabilities, and the 'when' lacks concrete trigger variations; not 3 because the 'Use when' clause is explicit.

4 / 5

Trigger Term Quality

"Use when querying OmniNode runtime knowledge" is a relevant trigger phrase, but "through the event bus" and "Thin Codex skill shim" are implementation jargon a user would not naturally say, and common variations like "search", "look up", or "recall" are missing. This fits anchor 3 (some relevant keywords, missing variations) better than 4 (good coverage) or 2 (generic keywords only).

3 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (OmniNode runtime knowledge, node_recall_compute, event bus) with triggers that would not plausibly fire for any other skill, matching anchor 5 (clear niche, distinct triggers, minimal conflict risk).

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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

OmniNode-ai/omnimarket

Path

plugins/onex/skills/recall/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.