CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

experiment-bridge

Workflow 1.5: Bridge between idea discovery and auto review. Reads EXPERIMENT_PLAN.md, implements experiment code, deploys to GPU, collects initial results. Use when user says "实现实验", "implement experiments", "bridge", "从计划到跑实验", "deploy the plan", or has an experiment plan ready to execute.

Quality

88%

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

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

An exceptionally actionable, well-sequenced workflow skill: every phase carries executable commands, templates, and checklists, and batch deployment is guarded by sanity checks, code review, and explicit recovery loops. Its only weaknesses are mild — some redundancy in the failure-handling prose and a large inline reviewer prompt that belongs in a reference file.

DimensionReasoningScore

Conciseness

The body is dense and directive with no padding of concepts Claude already knows; every phase is commands, tables, or checklists. Minor tightening is possible — e.g., the sanity-failure guidance in Phase 3 spreads over two overlapping paragraphs.

4 / 5

Actionability

Fully executable throughout: exact commands (git clone <BASE_REPO> base_repo/, /run-experiment, /experiment-queue), a complete copy-paste spawn_agent review template, result-file templates, and self-review checklists. Matches anchor 5's copy-paste-ready coverage of common cases.

5 / 5

Workflow Clarity

Phases 1–6 are clearly sequenced with explicit validation for batch operations: sanity-first gate, code review before deployment, a checkpoint when AUTO_DEPLOY = false, and layered error-recovery loops (read logs → fix → re-run, discard and reimplement, second-opinion rescue). Anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist in this skill; shared-references are well-signaled one level deep via markdown links (reviewer-backends.md, output-versioning.md, etc.). Kept at anchor 4 because the ~50-line inline reviewer prompt template and backend lifecycle rules could live in a separate reference file.

4 / 5

Total

18

/

20

Passed

Description

83%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 description that clearly states what the skill does through concrete actions and when to use it via explicit bilingual trigger phrases. Both dimensions of completeness (what and when) are fully satisfied; only minor refinements — dropping the generic "bridge" trigger and naming output artifacts — would raise it further.

DimensionReasoningScore

Specificity

Lists four concrete actions — "Reads EXPERIMENT_PLAN.md, implements experiment code, deploys to GPU, collects initial results" — covering the core workflow. Falls short of anchor 5 only because outputs (results summary, tracker updates) go unmentioned.

4 / 5

Completeness

Explicitly answers both questions: the "what" is the four concrete actions, and the "when" is a full "Use when user says..." clause listing concrete trigger phrases. Matches anchor 5 exactly.

5 / 5

Trigger Term Quality

Natural trigger phrases in both English and Chinese ("implement experiments", "deploy the plan", "从计划到跑实验") plus a state trigger ("has an experiment plan ready to execute"). Not a 5 because "bridge" alone is generic and no file-extension or artifact-style triggers are included.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Workflow 1.5 bridging idea discovery and auto review) with mostly distinct triggers. Minor overlap risk with sibling skills like /run-experiment and /experiment-queue, and the standalone word "bridge" is generic.

4 / 5

Total

17

/

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

relative_links

Relative link issues: 5 suspicious

Warning

Total

15

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex/experiment-bridge/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.