CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

async-repl-protocol

Async REPL Protocol

Quality

55%

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 ./.claude/skills/async-repl-protocol/SKILL.md

The canonical home for this skill is async-repl-protocol in parcadei/Continuous-Claude-v3

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.

The body is a tight, well-organized instruction sheet that adds genuine harness-specific knowledge (await Future-returning tools; only the first code block executes) without any filler. Its main defect is that the file is physically truncated: the BAD example for rule 2 is cut off mid-block with no closing code fence, which both breaks the markdown rendering and leaves the anti-pattern demonstration incomplete. Everything present is high quality; the skill just needs its ending restored.

Suggestions

Complete the truncated BAD example in rule 2 and close the code fence — the file currently ends mid-block at 'content = await view_file(path)', which breaks markdown rendering and leaves the anti-pattern unillustrated.

Show the contrasting BAD example explicitly as a two-block split with the second block marked as never executing, so the failure mode is as concrete as the GOOD case.

Optionally state the consequence of violating each rule in one clause (e.g. what happens when await is omitted — a Future object instead of the content), to make the rules actionable even when only skimmed.

DimensionReasoningScore

Conciseness

The body is lean and efficient — 'Compute AND return in ONE block. Multiple blocks means only first executes.' and the one-line rule statements assume Claude's competence and add only non-obvious harness-specific facts (await semantics, single-block execution). This matches the anchor 'Lean and efficient; assumes Claude's competence; every token earns its place'; there is no padding to trim, so it cannot be 4.

5 / 5

Actionability

The GOOD example is concrete and executable ('content = await view_file(path); return any(c.isdigit() for c in content)') with clear contrast annotations, matching 'Mostly executable guidance; concrete code or commands with minor gaps'. It falls short of 5 because the file ends mid-way through the BAD example — the final code block is truncated with no closing fence, so the anti-pattern illustration is incomplete.

4 / 5

Workflow Clarity

As a simple two-rule skill under 50 lines, each rule's required action is unambiguous, but the document abruptly terminates inside the second rule's BAD example, leaving that rule's illustration unfinished — 'Clear sequence with most checkpoints present; minor validation gaps' rather than the fully polished 5. It is not 3 because nothing in the guidance is ambiguous or missing a step; the rules themselves are complete and unambiguous, and this is not a destructive or batch operation requiring validation.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and content is organized into clear '## Rules' sections with numbered subsections — per the rubric's simple-skill guideline this earns the top anchor 'well-organized sections'. No bundle files exist (references/, scripts/, assets/ are absent), and none are needed, so there are no dangling or nested references to penalize.

5 / 5

Total

18

/

20

Passed

Description

3%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 a three-word title that communicates none of the skill's capabilities, no usage triggers, and no third-person action statements. It would almost never surface as a match for a user query because it shares no vocabulary with what a user would actually say. This is the lowest-quality description tier — essentially the same class as the bad example 'Helps with documents', but even less informative since it names no actions at all.

Suggestions

Rewrite the description in third person stating concrete actions, e.g. 'Runs code correctly in Agentica's async REPL harness by awaiting Future-returning tools and returning results in a single code block.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g. 'Use when executing code in the Agentica async REPL, when tools return Futures, or when responses are being split across multiple code blocks.'

Include the key trigger vocabulary users/agents would naturally mention — 'async REPL', 'await', 'single code block', 'Agentica testing harness' — so the skill is discoverable and distinguishable from general testing skills.

DimensionReasoningScore

Specificity

The description is only the phrase 'Async REPL Protocol' — a title with no concrete actions whatsoever, matching the anchor 'Entirely vague; no concrete actions; pure abstract language'. It cannot score 2 because it does not even name a domain with generic actions like 'Processes PDF files'.

1 / 5

Completeness

Neither 'what does this do' nor 'when should Claude use it' is answered — the description is a bare label, matching 'Missing both what and when'. The judging guideline that a missing 'Use when...' clause caps completeness at 3 applies even more strongly here, since the 'what' is also absent.

1 / 5

Trigger Term Quality

There are no natural keywords a user would say when needing this skill — only a technical protocol name, matching the anchor 'No natural keywords; only technical jargon'. It does not reach 2 because even a generic user-phrase like 'Works with files' is absent.

1 / 5

Distinctiveness Conflict Risk

'Async REPL Protocol' names a somewhat niche area, so it is not 'entirely generic' (anchor 1), but it provides no distinguishing actions or triggers, giving 'very broad; high overlap risk' behavior (anchor 2) — any async/REPL/testing task could plausibly match it. It does not reach 3 because there is no specificity about what the skill actually does that would separate it from similar testing skills.

2 / 5

Total

5

/

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

description_field

'description' is very short (19 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/async-repl-protocol/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.