CtrlK
BlogDocsLog inGet started
Tessl Logo

the-provider-runtime-symmetry

Keep Stave's Claude and Codex provider runtimes in sync when editing one of them. Use when a change touches `electron/providers/claude-sdk-runtime.ts`, `electron/providers/codex-app-server-runtime.ts`, executable lookup, env construction, CLI session launch env, tooling status probes, or any provider-agnostic behavior. Trigger on phrases like "provider runtime", "claude adapter", "codex adapter", "sibling adapter", "PATH env", "CLAUDE_CONFIG_DIR", "CODEX_HOME", "tooling status", "어댑터 대칭", "양쪽 프로바이더 확인".

65

Quality

79%

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 ./skills/the-provider-runtime-symmetry/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 a well-structured, actionable checklist skill with concrete file paths, grep targets, and verification steps tailored to its codebase. Its main weakness is length and some redundancy between the use-when, failure-modes, and guardrails sections.

Suggestions

Tighten redundancy: merge 'Guardrails' into 'Common Failure Modes' or fold the 'Use This Skill When' list back into the description to trim the body.

Add an explicit validate->fix->retry loop in the Verification section (e.g., 'if typecheck or a turn fails, fix and re-run before proceeding') to reach top workflow clarity.

Consider extracting the lengthy 'Symmetry Checklist' into a references file to improve progressive disclosure and reduce inline token load.

DimensionReasoningScore

Conciseness

The ~125-line body is mostly efficient and codebase-specific, but it carries redundancy: 'Use This Skill When' overlaps the description triggers, and 'Common Failure Modes' overlaps 'Guardrails' in framing, so it could be tightened.

3 / 5

Actionability

Provides concrete executable guidance — specific file paths, grep targets ('Grep across electron/providers/, src/store/app.store.ts'), and commands ('bun run typecheck') — with only minor gaps since it is instruction-only without copy-paste code snippets.

4 / 5

Workflow Clarity

A six-section sequenced Symmetry Checklist plus an explicit Verification section with validation steps (typecheck, run a turn with each provider) gives a clear sequence with most checkpoints present; it lacks a formal validate->fix->retry loop.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and self-contained content; no bundle files exist in references/scripts/assets, and references to repo docs and sibling skills are clearly signaled, with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

91%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 specific, complete, and rich in natural trigger terms covering both English and Korean phrasings. It carves out a clear niche with only minor overlap risk against closely related provider skills.

DimensionReasoningScore

Specificity

States a concrete action ('Keep Stave's Claude and Codex provider runtimes in sync') and enumerates specific areas touched (executable lookup, env construction, CLI session launch env, tooling status probes), but the core action is singular while the rest are trigger areas, leaving minor gaps versus a fully comprehensive action list.

4 / 5

Completeness

Explicitly answers both 'what' ('Keep...provider runtimes in sync') and 'when' ('Use when a change touches...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including synonyms ('claude adapter', 'codex adapter', 'sibling adapter', 'provider runtime'), specific env vars (PATH, CLAUDE_CONFIG_DIR, CODEX_HOME), and bilingual phrases a developer on this codebase would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (provider runtime parity) with distinct triggers and minimal conflict risk, though it shares the provider domain with sibling skills like the-provider-router and the-ipc-contract-audit that it itself cross-references.

4 / 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
sendbird/stave
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.