CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

session-bootstrap

Thin Codex skill shim for node_session_bootstrap. Use to initialize a session contract snapshot and launchd scheduler plan.

Quality

70%

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/session-bootstrap/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 highly actionable: a complete dispatch command, a concrete payload template with an explicit argument mapping, preflight validation, and unambiguous response/output handling. Its weaknesses are redundancy — contract metadata repeated between the generated runtime-truth block and the Contract section — and monolithic inline structure that would benefit from splitting the generated metadata into a reference file.

Suggestions

Deduplicate the contract metadata: the command name and command/terminal topics appear in both the generated "Runtime truth" block and the "Contract" section — keep one authoritative copy and cross-reference it.

Move the generated "Runtime truth" block into a references/ file (e.g., references/runtime-contract.md) linked from a short overview line, restoring a clean Arguments section and improving progressive disclosure.

Tighten the payload mapping section by merging the bullet list into the arguments table (a 'payload path' column) to remove the doubled enumeration of each argument.

DimensionReasoningScore

Conciseness

Mostly dense and specific (payload shape, argument mapping, error handling), but it repeats the same contract metadata three times — the command name, wrapper path, and command/terminal topics appear in both the generated "Runtime truth" block and again verbatim in the "Contract" section — and the ~39-line generated block sits awkwardly between "## Arguments" and the arguments table. This is more than the 'minor instances' of the 4 anchor, so it sits at 'mostly efficient but could be tightened'.

3 / 5

Actionability

The Dispatch section gives an executable command ("env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py --command-name \"session_bootstrap\" --payload '<json-payload>' --timeout-ms 30000"), a complete minimal JSON payload covering the common build-session case, an explicit argument-to-payload mapping (e.g., "cost_ceiling -> contract.cost_ceiling_usd"), preflight via --compile-only, and concrete response handling ("If ok is false, surface error.code and error.message directly"). This matches 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'; the only placeholders (<session-id>, <json-payload>) are directly fillable from the supplied template, so it is not merely the 4 anchor's 'minor gaps'.

5 / 5

Workflow Clarity

The sequence is clear and ordered — run location, build the nested contract payload, dispatch via the wrapper, interpret ok/output_payloads, render the result — with real checkpoints present: compile-only preflight ("validates the payload, command topic, response topic, correlation id, timeout") and explicit error surfacing. It falls short of the 5 anchor because there is no error-recovery feedback loop (errors are surfaced, not fixed and retried), but it exceeds the 3 anchor since validation steps are explicit rather than missing.

4 / 5

Progressive Disclosure

Sections exist (Arguments, Dispatch, Contract, Output) and there are no broken or nested references, but the skill is a single ~140-line file whose generated "Runtime truth" block (~39 lines of adapter/node contract metadata) is inline content that clearly belongs in a separate reference file, and it duplicates the "Contract" section's topics verbatim. The block's placement under "## Arguments" before the table is also an organization wart, matching 'some structure but could be better organized; content that should be separate is inline' rather than the 4 anchor's well-placed content.

3 / 5

Total

15

/

20

Passed

Description

57%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 honest, concise, and clearly scoped to a single niche node adapter, giving it excellent distinctiveness. However, it only enumerates two concrete actions, relies on internal jargon for triggers, and lacks an explicit 'Use when...' trigger clause, capping specificity, trigger term quality, and completeness at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to bootstrap or start a session, create a session contract snapshot, or set up the launchd scheduler plan."

Enumerate one or two more concrete capabilities (e.g., dispatching via the Pattern-B request wrapper, supporting --compile-only preflight and dry_run) to raise specificity.

Include natural user-facing synonyms ("start a session run", "session setup") alongside the internal node name so trigger matching does not depend solely on jargon.

DimensionReasoningScore

Specificity

The description names its domain ("Thin Codex skill shim for node_session_bootstrap") and exactly two concrete actions ("initialize a session contract snapshot and launchd scheduler plan"), matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not a 4 because no further specific capabilities (e.g., argument handling, dispatch, dry-run/preflight behavior) are listed.

3 / 5

Completeness

The 'what' is clear ("initialize a session contract snapshot and launchd scheduler plan"), but the only usage clause is "Use to initialize...", which restates the purpose rather than giving explicit trigger guidance (no 'Use when...' or equivalent conditions). Per the judging guideline, a missing 'Use when...' clause or equivalent explicit trigger guidance caps completeness at 3; it is not a 2 because the 'what' is concrete and a weak 'when' is implied by the 'Use to' phrasing.

3 / 5

Trigger Term Quality

Phrases like "session contract snapshot" and "launchd scheduler plan" are relevant domain keywords a user in this ecosystem might say, but the wording leans on internal jargon ("Codex skill shim", "node_session_bootstrap") and misses natural variations such as "start a session", "set up a session run", or "scheduler plan". This lands on 'some relevant keywords but missing common variations or synonyms', not 4, since natural phrasing coverage is thin.

3 / 5

Distinctiveness Conflict Risk

"Thin Codex skill shim for node_session_bootstrap" plus the snapshot/scheduler-plan framing carves out a clear niche with distinct triggers and virtually no overlap risk with generic session, scheduling, or document skills. It clearly matches the 'clear niche with distinct triggers; minimal conflict risk' anchor rather than the 4 anchor, which expects some overlap with closely related skills.

5 / 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

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