CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lading-optimize-submit

Full optimization workflow with git branch creation, commits, and optional PR. Wraps /lading-optimize-hunt with git automation.

58

Quality

73%

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/lading-optimize-submit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 lean, executable workflow with concrete commands, a clear phase sequence, and real validation checkpoints, plus a correctly wired one-level-deep bundle reference. Its only weaknesses are mild redundancy around the hunt-skill responsibility split and the duplicated commit-message content between the inline example and the template file.

DimensionReasoningScore

Conciseness

The body is efficient — terse command blocks with purposeful comments and a concrete commit example that earns its tokens — though the Phase 2 "The hunt will / BUT the hunt does NOT" responsibility listing is somewhat repetitive, and the Note bullets restate the template's rules.

4 / 5

Actionability

Every phase contains concrete, executable shell commands, including a fully filled-in commit message example, three example branch names, and a complete gh pr create heredoc; only minor gaps remain (PR title placeholder, {MODEL} substitution instruction).

4 / 5

Workflow Clarity

Phases 0-4 are clearly sequenced with explicit checkpoints ("STOP if working directory is dirty", "CRITICAL: ... you MUST return here to Phase 3") and validation delegated to /lading-preflight and the review skill's pass/fail judging; it lacks a feedback loop for commit/push/PR failures, keeping it below 5.

4 / 5

Progressive Disclosure

The single bundle file (assets/commit-template.txt) exists and is referenced once by full path — one level deep and clearly signaled — and the body is well-sectioned into phases; the inlined commit example largely duplicates the template file's content, a minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

58%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 communicates a clear, fairly specific capability set anchored to a named sibling skill, but it entirely omits when to use it. Adding an explicit "Use when..." clause with natural trigger phrases would address the two lowest-scoring dimensions.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks to submit, commit, or open a PR for an optimization found by /lading-optimize-hunt.'

Include natural trigger phrases and synonyms users would actually say, such as 'submit optimization', 'commit perf improvement', or 'open an optimization PR'.

Briefly state what the commits contain (benchmark results, target, technique) to close the specificity gap without adding fluff.

DimensionReasoningScore

Specificity

"git branch creation, commits, and optional PR" and "Wraps /lading-optimize-hunt with git automation" name several concrete actions, but coverage has minor gaps (no indication of what the optimization work or commits actually involve).

4 / 5

Completeness

The "what" is clear (branch creation, commits, optional PR wrapping the hunt skill), but there is no "when" clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Terms like "optimization", "git branch", "commits", and "PR" are relevant, but the description lacks the natural phrases and synonyms a user would say (e.g., "submit an optimization", "open a PR for a perf change") and has no trigger guidance.

3 / 5

Distinctiveness Conflict Risk

Naming the specific sibling skill "/lading-optimize-hunt" carves a distinct niche as the git-automation layer, with only minor overlap risk against that hunt skill itself; the generic phrase "Full optimization workflow" keeps it from a 5.

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

DataDog/lading

Path

.claude/skills/lading-optimize-submit/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.