CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ai-ide-runner

Run prompts in Claude Code, OpenCode, Cursor, or Codex CLIs from this session — one IDE, fan-out, or model comparison. Relay the other runtime's stdout verbatim. Use on run in <ide>, compare <ide> vs <ide>, try on <model>, run across models.

71

Quality

89%

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

81%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 with an explicit workflow and a strong self-check checklist, and it makes good use of two real one-level-deep reference files. Its main weakness is repetition: the courier rule and hook-blocked behavior are each explained in multiple sections, inflating token cost without adding guidance.

Suggestions

State the 'courier, not co-author' verbatim-relay rule once (in the Output contract section) and cross-reference it from the intro and Self-check instead of repeating it in full three times.

Merge 'Hook-blocked tool calls count as tool output' and 'Where the tool's stdout actually lives' into one section covering the blocked case, keeping a single Right/Wrong example pair rather than two parallel walkthroughs.

Move the dated benchmark note ('2026-09-06: ai-ide-runner-single-cursor-read-only …') into a reference or past-failures note; time-sensitive entries in the main body add tokens and will go stale.

DimensionReasoningScore

Conciseness

Most sections are dense and substantive, but the core rule 'You are a courier, not a co-author' is stated three times (intro, Output contract, Self-check) and the hook-blocked/MOCK-prefix behavior is explained in three separate places ('Hook-blocked tool calls count as tool output', 'Where the tool's stdout actually lives', and duplicated Right/Wrong example blocks). A dated benchmark log entry ('(2026-09-06: ai-ide-runner-single-cursor-read-only …)') adds time-sensitive detail outside any 'old patterns' section. Not 2 because there is little concept-teaching fluff; not 4 because the repetition is substantial and clearly trimmable.

3 / 5

Actionability

Fully executable throughout: exact binaries and flags ('claude -p "<prompt>"', 'opencode run', 'cursor-agent -p --trust', 'codex exec'), a copy-paste parallel bash script with 'wait' and PID tracking, discovery commands per runtime, and a concrete env override ('CLAUDECODE="" claude -p …'). Covers the common single-run, fan-out, and comparison cases.

5 / 5

Workflow Clarity

The four-step workflow (Parse intent → Pick model → Build & run → Present) is clearly sequenced, and the 'Self-check before sending the final message' section is an explicit validation checklist with corrective feedback loops ('If no → go back and add it', 'Revert to pure relay'). Error-recovery paths for auth failures, missing binaries, and native-provider errors are specified (stop, report verbatim, ask user).

5 / 5

Progressive Disclosure

Good structure with well-signaled one-level-deep references: full flag sets deferred to references/runtimes.md and the model catalogue to references/models.md (both files exist and match their descriptions). Not 5 because the 299-line main file carries extended Right/Wrong example walkthroughs and the multi-section hook-blocked narrative that would fit better in a reference or a single consolidated section — minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

92%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 excellent: it names concrete capabilities, answers both what and when explicitly, and carries natural trigger patterns tied to specific IDE names. The only minor gap is absence of synonyms for the trigger phrases (e.g., 'second opinion', 'ask <ide>').

DimensionReasoningScore

Specificity

The description lists four concrete actions — 'Run prompts in Claude Code, OpenCode, Cursor, or Codex CLIs', 'one IDE, fan-out, or model comparison', and 'Relay the other runtime's stdout verbatim' — which comprehensively cover the skill's scope. Not the level below (4) because there is no noticeable coverage gap: single-IDE run, multi-IDE fan-out, model fan-out, and verbatim relay are all enumerated.

5 / 5

Completeness

Both questions are explicitly answered: the 'what' ('Run prompts in … CLIs from this session … Relay the other runtime's stdout verbatim') and the 'when' ('Use on run in <ide>, compare <ide> vs <ide>, try on <model>, run across models') with concrete trigger phrases. Matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Trigger phrases 'Use on run in <ide>, compare <ide> vs <ide>, try on <model>, run across models' are natural user phrasings and the IDE names (Claude Code, OpenCode, Cursor, Codex) are present. Not 5 because common synonyms such as 'second opinion from <ide>', 'ask <ide>', or 'cross-check with <ide>' are missing; not 3 because the included patterns are natural, not generic.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — invoking external AI-CLI runtimes and relaying their output verbatim — with distinct triggers naming the four specific IDEs. Minimal conflict risk with general coding or comparison skills since generic phrasings are avoided.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

korchasa/flowai-plugins

Path

plugins/flowai-beta/skills/ai-ide-runner/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.