CtrlK
BlogDocsLog inGet started
Tessl Logo

chat-first-workbench

Implement or extend the opt-in Codex/T3-like chat-first shell. Use when changing chat rails, contextual app panes, app opening, or local/mobile shell preferences across Electron, Dispatch, or mobile.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, well-structured guardrail skill that provides concrete method-level guidance and an explicit verification checklist without token waste. The main gap is the absence of executable code examples, which is acceptable for an instruction-only skill.

DimensionReasoningScore

Conciseness

The body is lean and dense guardrail prose with no concept-explanation padding (no 'what Electron is'), assuming Claude's competence; every line is a constraint or instruction that earns its place.

5 / 5

Actionability

Guidance names concrete methods and exact constraints ("list-workspace-apps and create_embed_session", "never iframe a raw workspace URL", shelf "capped at six"), which is actionable; it stops short of 5 only because there is no copy-paste code, though absence of code is acceptable for an instruction skill.

4 / 5

Workflow Clarity

The Verification section gives an explicit checklist (rail ordering, chat history, app selection, embed-session errors, pane close, completed open_app) plus the 'configuration alone is insufficient proof' guard; it is constraint-based rather than a linear sequence, so it lacks the explicit error-recovery loop of a 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and four well-organized sections (Contract, Client behavior, Agent and state boundaries, Verification), satisfying the simple-skill exception that well-organized self-contained content scores 5.

5 / 5

Total

18

/

20

Passed

Description

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

A strong, specific description that clearly states both what the skill does and when to use it, with concrete platform-scoped triggers. Voice is imperative/third-person with no first/second-person drift.

DimensionReasoningScore

Specificity

The description names the domain and several concrete change-areas ("changing chat rails, contextual app panes, app opening, or local/mobile shell preferences"), matching the 'lists several specific actions; minor gaps' anchor rather than the fully comprehensive 5.

4 / 5

Completeness

It explicitly answers both what ("Implement or extend the opt-in Codex/T3-like chat-first shell") and when with concrete trigger phrases via a clear 'Use when...' clause, matching the 5 anchor; the 'Use when' clause is present so it is not capped at 3.

5 / 5

Trigger Term Quality

"Use when changing chat rails, contextual app panes, app opening, or local/mobile shell preferences across Electron, Dispatch, or mobile" gives good natural-term coverage a developer would say; it falls short of 5 only in lacking synonyms/variations.

4 / 5

Distinctiveness Conflict Risk

The niche is highly specific (chat-first shell, Codex/T3-like, Electron/Dispatch/mobile), giving distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
BuilderIO/agent-native
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.