CtrlK
BlogDocsLog inGet started
Tessl Logo

refine-live

In-chat fallback for the Timeline Inspector Refine agent. Use when the user runs `/refine live`, asks to "refine live", "go live", or answer refine jobs — but ONLY when no persistent agent is wired (no `npx transitions-refine live`). Prefer `npx transitions-refine live` for run-and-forget (relay spawns agent per click, no idle credit burn). This skill long-polls the relay, posts suggestions, handles scan/apply jobs.

72

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

77%

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 a clearly sequenced, well-validated poll loop, but it is a large monolithic file that inlines reference-grade detail and repeats some context already present in the description and earlier sections.

Suggestions

Remove the redundant restatement in step 5 and the 'Two modes' section's repetition of the description's persistent-vs-in-chat comparison to tighten the body.

Move the 21-recipe catalog and/or the motion-token tables into a references file the loop can consult when needed, keeping SKILL.md as a leaner overview with one-level-deep pointers.

If keeping recipes inline for latency reasons, add a one-line note explaining that the inlining is deliberate (zero file reads) so the progressive-disclosure tradeoff is explicit.

DimensionReasoningScore

Conciseness

Most content is dense and earned (curl commands, token tables, recipe catalog), but the 'Two modes' section restates the frontmatter description and step 5 re-summarizes the loop exits already detailed in 'The loop' section, so it could be tightened.

2 / 3

Actionability

Fully executable curl commands, complete JSON request/result shapes, concrete motion-token values, and a 21-recipe decision list make the guidance copy-paste ready with no pseudocode.

3 / 3

Workflow Clarity

The poll loop is a clearly sequenced numbered procedure with explicit validation checkpoints (204 vs 200 stop vs 200 job), scan/apply dispatch, and dedicated error/empty-result endpoints providing feedback loops.

3 / 3

Progressive Disclosure

The ~450-line body is well sectioned but largely monolithic, inlining the full 21-recipe catalog and all token tables; the referenced recipe/polish files are user-paste targets rather than navigable bundle files (none exist in references/scripts/assets), so content that could be split remains inline.

2 / 3

Total

10

/

12

Passed

Description

100%

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 concise, specific, and fully answers both what and when with natural trigger terms and an explicit disambiguating guard. It stays in third person and avoids fluff, earning top marks across all dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'long-polls the relay, posts suggestions, handles scan/apply jobs' — naming the domain and several specific operations, matching the 'Lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (in-chat fallback that long-polls, posts suggestions, handles scan/apply) and when ('Use when the user runs `/refine live`... but ONLY when no persistent agent is wired'), with explicit triggers.

3 / 3

Trigger Term Quality

Covers natural phrases a user would say — '/refine live', 'refine live', 'go live', 'answer refine jobs' — plus the persistent-agent alternative 'npx transitions-refine live', giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

A narrow, clearly defined niche (Timeline Inspector Refine in-chat fallback) with an explicit 'ONLY when no persistent agent is wired' guard that disambiguates it from the persistent agent CLI, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Jakubantalik/transitions.dev
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.