CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

new-stable-load-test

Configures a new Camunda stable branch into the load test workflows.

Quality

69%

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 ./load-tests/skills/new-stable-load-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 efficiently written pointer-skill that adds genuine non-obvious value (two-PR split, staleness warnings, observable-result verification) around an external checklist. Its main weaknesses are that the single reference it depends on is not in the bundle and is linked with two conflicting relative paths, and the skill is not self-sufficient if that doc is unavailable.

Suggestions

Fix the inconsistent relative links: lines 10 and 27/28 point to the same doc with different depths ('../../' vs '../../../'); pick one correct path.

Inline a minimal summary of the steps (which files, which sections) so the skill degrades gracefully if the referenced doc is not reachable.

Add a brief error-recovery note (what to do when a stated observable result does not match) to close the workflow_clarity gap toward explicit feedback loops.

DimensionReasoningScore

Conciseness

The ~35-line body is lean with zero padding: no explanation of what Camunda or load testing is, no restating of the checklist, only the non-obvious meta-guidance (interpolate variables, split into two PRs, reference PRs may be stale). Every token carries information Claude could not infer, matching 'Lean and efficient; assumes Claude's competence; every token earns its place'.

5 / 5

Actionability

Guidance is procedurally concrete (read the doc in full first, open two separate PRs, either order, use reference PRs as templates) but the executable substance — which files to edit, what diffs to make — lives entirely in the referenced doc, and the two links to it use inconsistent relative depths ('../../load-tests/...' on line 10 vs '../../../load-tests/...' on line 27), so at least one is broken. Fits 'Some concrete guidance but incomplete... missing key details'; not 4, since the skill alone cannot execute the task.

3 / 5

Workflow Clarity

A clearly sequenced 3-step process with real validation checkpoints: 'verify against that stated result rather than the diff alone' and 'confirm the referenced file/line still exists in the current version before matching against it'. Matches 'Clear sequence with most checkpoints present; minor validation gaps' — not 5, since error-recovery feedback loops and the per-file checklist itself are deferred to the external doc; not 3, since checkpoints are explicit rather than implicit.

4 / 5

Progressive Disclosure

The body correctly delegates detail to a single one-level-deep reference, but no bundle files exist (no references/, scripts/, or assets/) and the target doc is not part of the skill — the two relative paths are inconsistent ('../../' vs '../../../') and resolve to a nonexistent file, so navigation from the skill alone is unreliable. This fits 'references present but not clearly signaled / could be better organized' territory (3) rather than 4, where references would be reliably navigable.

3 / 5

Total

15

/

20

Passed

Description

53%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 terse, domain-specific description that clearly states one concrete action but omits any 'Use when...' trigger clause and gives no sense of the multi-step scope (two PRs across two base branches, per the body). It is functional for an expert but would not reliably surface for a user phrasing the need differently.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a new stable/X.Y branch is cut from main and needs to run in the load test workflows.'

Enumerate 2-3 concrete actions to lift specificity, e.g. 'Updates load-test workflow files and opens PRs on both the new stable branch and main.'

Add natural keyword variations such as 'new stable version', 'release branch', or 'stable/X.Y' so users' phrasing matches the description.

DimensionReasoningScore

Specificity

The description names the domain ("Camunda stable branch", "load test workflows") and a single concrete action ("Configures... into the load test workflows"), but never says what configuring involves (files edited, PRs opened, CI updated). This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' — not 4, which requires several specific actions, and not 2, since the action is domain-specific rather than generic.

3 / 5

Completeness

The 'what' is clear ("Configures a new Camunda stable branch into the load test workflows"), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3: 'Has a clear what but when is missing or only weakly implied'.

3 / 5

Trigger Term Quality

Relevant natural terms like "stable branch" and "load test" are present, but common variations users would say are missing: "new stable version", "release branch", "stable/X.Y", "X.Y", "load-test workflows". Fits 'Some relevant keywords but missing common variations or synonyms' — above 2 (terms are domain-natural, not generic like "works with files") but below 4 (no synonym coverage).

3 / 5

Distinctiveness Conflict Risk

The Camunda + stable-branch + load-test niche is specific and unlikely to collide with unrelated skills. It sits between 'Mostly distinct; minor overlap risk' (4) and 'Clear niche with distinct triggers; minimal conflict risk' (5) — the niche is clear, but the absence of explicit trigger phrasing leaves minor risk of firing for general load-test or release chores. Not 3, since it is far more specific than 'Works with document files'.

4 / 5

Total

13

/

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: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

camunda/camunda

Path

load-tests/skills/new-stable-load-test/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.