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

69%

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 ./src/omnimarket/adapters/codex/skills/recall/SKILL.md

The canonical home for this skill is recall in OmniNode-ai/omnimarket

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 delivers a concrete, executable dispatch workflow with a preflight checkpoint and explicit error handling, and it avoids generic padding entirely. Its main weaknesses are redundancy between the 'Runtime truth' and 'Contract' sections and a missing worked payload/response example. The inlined generated metadata and the Arguments/table separation also leave organization short of well-structured progressive disclosure.

Suggestions

Deduplicate the '## Contract' section against the generated 'Runtime truth' block, keeping only new information (the backing node path and wrapper script path) there.

Add one complete copy-paste example: a sample JSON payload for a typical query and the shape of a successful output_payloads[0] result.

Move the generator-owned runtime-truth/evidence-schema details into a referenced file (e.g. references/runtime-contract.md) so the Arguments table sits directly under its heading.

DimensionReasoningScore

Conciseness

The body is system-specific with no explanation of known concepts, but the ~40-line generated 'Runtime truth' block over-explains adapter internals (evidence wire schema, binding-field enumerations) that the wrapper handles, and the '## Contract' section repeats the command name and both topics already stated above. Fits 'mostly efficient but could be tightened'; the duplication keeps it below 4.

3 / 5

Actionability

Provides a concrete dispatch command ('env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py --command-name "recall_compute" ...'), explicit payload field mapping, and clear result handling (output_payloads[0], error.code/error.message). Not 5 because '--payload <json-payload>' is a placeholder with no complete worked example payload or sample response.

4 / 5

Workflow Clarity

Clear sequence (run from repo, map inputs, dispatch, interpret result) with an explicit preflight checkpoint (--compile-only) and error-handling guidance; it is a non-destructive single dispatch so the validation cap does not apply. Not 5 because there is no validate-fix-retry feedback loop or numbered step sequence.

4 / 5

Progressive Disclosure

Sections are well-headered and navigable, but at ~100 lines everything is inline: the generator-owned contract metadata is content that could live in a reference file, and the '## Arguments' heading is separated from its own table by that inserted block. No bundle reference files exist to structure around, matching the 'content that should be separate is inline' anchor.

3 / 5

Total

14

/

20

Passed

Description

62%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 is concise, third-person, and includes an explicit 'Use when' trigger, but it describes the skill's mechanism (a shim) rather than its concrete capabilities and relies on internal jargon over natural user phrasing. Distinctiveness within its niche is strong. It sits solidly at the midpoint-above range across all dimensions.

Suggestions

Replace mechanism language ('Thin Codex skill shim') with concrete capabilities, e.g. 'Queries scoped OmniNode runtime knowledge (learnings, architecture, antipatterns) with repo/task filters and returns ranked, attributed results.'

Add natural trigger synonyms users would actually say, such as 'recall', 'search past learnings', or 'look up prior OmniNode work', alongside the existing 'when' clause.

DimensionReasoningScore

Specificity

Names the domain and a single action ("Thin Codex skill shim for node_recall_compute", "querying OmniNode runtime knowledge") but omits the concrete capabilities the body documents (scoped retrieval of learnings/architecture/antipatterns, filters, ranked sources with confidence). Not 4 because it does not list several specific actions; not 2 because the domain and action are concretely named.

3 / 5

Completeness

Explicitly answers both what ("Thin Codex skill shim for node_recall_compute") and when ("Use when querying OmniNode runtime knowledge through the event bus") in third person. Not 5 because the 'what' describes the mechanism rather than concrete capabilities and the trigger clause could be more specific.

4 / 5

Trigger Term Quality

Includes some relevant keywords ("querying", "runtime knowledge", "event bus") but leans on internal jargon ("Codex skill shim", "node_recall_compute") and misses natural variations users would say such as "recall" or "search past learnings". Fits the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Highly niche phrasing ("OmniNode runtime knowledge", "event bus") gives minimal overlap with generic skills, but closely related runtime/node adapter skills in the same ecosystem could overlap on 'runtime' triggers, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

14

/

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

src/omnimarket/adapters/codex/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.