CtrlK
BlogDocsLog inGet started
Tessl Logo

loop-engineering

Loop engineering runtime Grill + Monitor

50

Quality

53%

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 ./src/skills/loop-engineering/SKILL.md
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-structured instruction skill that gives concrete API/callback guidance and a clear interview checklist with verification and manual-review checkpoints. Its main gap is the absence of an explicit end-to-end execute-verify-retry flow and a ready-to-run invocation example.

DimensionReasoningScore

Conciseness

The body is lean and efficient: terse numbered checklist items and callback signatures with no padding or explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Provides concrete callback signatures (onLoopComplete, resolveManualReview, cancel), enumerated success types, and defaults (max attempts 3), but lacks a full copy-paste invocation example covering the common execute-verify-retry case.

4 / 5

Workflow Clarity

The Grill is a clear numbered 7-step interview sequence and verification is explicit (verify agent, max attempts, manual review checkpoint), though the execute→verify→retry loop itself is implied rather than drawn as an explicit numbered flow.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed and no bundle files present; content is well-organized into clear Grill, Loop Monitor, and Notes sections, meeting the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

21%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 terse jargon fragment ('Loop engineering runtime Grill + Monitor') that names a domain but gives no concrete actions, no natural trigger terms, and no 'when to use' guidance. It is too cryptic to reliably surface the skill when needed.

Suggestions

Rewrite in third person with concrete actions, e.g. 'Runs an iterative execute-then-verify engineering loop with a Grill interview to set up goals and a Monitor for callbacks.'

Add a 'Use when...' clause naming natural trigger phrases users would actually say (e.g. 'Use when running a retry-until-pass engineering loop or when the user asks to iterate until tests pass').

Replace internal component names ('Grill', 'Monitor') with user-facing language or introduce them alongside plain-language descriptions.

DimensionReasoningScore

Specificity

Names the domain ('Loop engineering') but the only action language is the jargony fragment 'runtime Grill + Monitor', which lists components rather than concrete actions.

2 / 5

Completeness

It offers only a vague 'what' (a runtime with two components) and entirely lacks any 'when'/'Use when' trigger guidance, matching the vague-what-and-no-when anchor.

2 / 5

Trigger Term Quality

'Grill' and 'Monitor' are internal runtime component names, not natural phrases a user would say when they need this skill; there is no natural trigger keyword.

1 / 5

Distinctiveness Conflict Risk

'Loop engineering' is a somewhat specific niche, but the terse jargon-laden phrasing makes it hard to distinguish from other orchestration/engineering skills to a user.

3 / 5

Total

8

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alvinunreal/oh-my-opencode-slim
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.