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

73%

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/session-bootstrap/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is a strong, highly actionable adapter shim: an executable dispatch command, a complete payload example, explicit argument mapping, and defined success/error handling cover the common path end-to-end. Its main weaknesses are mild — a Contract section that restates the generated runtime-truth metadata, and deep evidence-schema detail inlined in the main file rather than split into a reference. Workflow checkpoints are present via the compile-only preflight, though steps are not explicitly numbered.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific contract metadata rather than concepts Claude already knows, and the arguments table and mapping list are compact; however, the "Contract" section duplicates the command name, both topics, and the wrapper path already stated in the generated runtime-truth section. Not a 5 because that duplicated block and some deep evidence-schema detail could be trimmed; not a 3 because padding is minor, not pervasive.

4 / 5

Actionability

The dispatch section provides a copy-paste-ready command (`env -u PYTHONPATH uv run python scripts/run_codex_runtime_request.py --command-name "session_bootstrap" ...`), a complete minimal JSON payload, an explicit argument-to-payload mapping, a `--compile-only` preflight flag, and concrete success/error handling ("If `ok` is `false`, surface `error.code` and `error.message`"). This fully covers the common cases.

5 / 5

Workflow Clarity

The sequence (build payload from arguments → dispatch via wrapper → interpret ok/output_payloads → render result) is clear, with an explicit validation checkpoint (`--compile-only` preflight) and an error branch. Not a 5 because the steps are unnumbered and there is no fix-and-retry feedback loop; not a 3 because checkpoints are present, not merely implicit.

4 / 5

Progressive Disclosure

As a single-file skill with no bundle files present, it is well-organized into clearly headed sections (Arguments, Dispatch, Contract, Output) with the generated metadata fenced by BEGIN/END markers. Not a 5 because the runtime-evidence and binding-field documentation is inlined in SKILL.md where a one-level-deep reference file could carry it, and the duplicate Contract section adds organizational noise.

4 / 5

Total

17

/

20

Passed

Description

53%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 states a clear, narrowly-scoped purpose tied to a specific node, which makes it highly distinguishable, but it reads as internal architecture documentation rather than user-facing trigger guidance. It has a clear "what" yet no explicit "Use when..." trigger clause, and its keywords are dominated by system jargon instead of natural user phrasing. These issues place most dimensions at the midpoint of the scale.

Suggestions

Add an explicit trigger clause such as "Use when starting a new OmniMarket build session or when the user asks to bootstrap a session" to raise completeness.

Include natural user phrasings and synonyms (e.g., "start a session", "session setup", "kick off a build loop") alongside the internal terminology to improve trigger term quality.

Briefly enumerate the node's other concrete capabilities (contract validation, snapshot persistence, scheduler-plan emission) for fuller coverage of what the skill does.

DimensionReasoningScore

Specificity

"initialize a session contract snapshot and launchd scheduler plan" names the domain and two concrete actions, but coverage is not comprehensive (no mention of contract validation, snapshot persistence, or dispatch). Not a 4 because only two actions are listed, not several; not a 2 because the actions are specific rather than generic.

3 / 5

Completeness

The "what" is clear ("initialize a session contract snapshot and launchd scheduler plan"), but "Use to initialize..." states purpose rather than trigger conditions — there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 4 because no distinct "when" is present, only a weakly implied one.

3 / 5

Trigger Term Quality

Relevant keywords exist ("session", "bootstrap", "session contract snapshot", "launchd scheduler plan") but they skew toward internal jargon ("thin Codex skill shim", "node_session_bootstrap") and miss natural variations users would say, like "start a session", "set up a session", or "kick off a build loop". Not a 4 because keyword coverage is thin; not a 2 because there are several domain-relevant terms rather than one or two generic ones.

3 / 5

Distinctiveness Conflict Risk

"Thin Codex skill shim for node_session_bootstrap" pins the skill to one specific backing node, and "session contract snapshot and launchd scheduler plan" are distinct artifacts, giving a clear niche with only minor overlap risk against sibling session/scheduler shim skills. Not a 5 because the shared generic terms ("session", "scheduler") leave minor conflict risk and the triggers are jargon-heavy rather than distinct natural phrases.

4 / 5

Total

13

/

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