CtrlK
BlogDocsLog inGet started
Tessl Logo

lading-optimize-submit

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

64

Quality

76%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/lading-optimize-submit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 clear, checkpointed phase workflow and a well-placed template asset. Its only weakness is mild redundancy in the hunt-responsibility prose that could be condensed.

Suggestions

Merge the two "The hunt will:" / "BUT the hunt does NOT:" blocks into a single concise responsibility split to remove redundancy.

Consider moving the verbose commit-message and PR-body examples into the asset bundle (or a dedicated reference file) so the SKILL.md overview stays leaner.

DimensionReasoningScore

Conciseness

Mostly efficient with executable commands and brief notes, but the dual "The hunt will:" / "BUT the hunt does NOT:" lists repeat overlapping scope and could be tightened into a single responsibility table.

2 / 3

Actionability

Provides copy-paste-ready, executable commands for every phase — git checkout/commit, a full commit-message example, and a complete gh pr create invocation with template.

3 / 3

Workflow Clarity

Phases 0–4 are explicitly sequenced with validation checkpoints ("STOP if working directory is dirty", the CRITICAL return-to-Phase-3 note) and a clear handoff boundary for the destructive git operations.

3 / 3

Progressive Disclosure

Body is organized into well-labeled phases and offloads the commit message skeleton to a real one-level-deep asset (assets/commit-template.txt), keeping the overview navigable.

3 / 3

Total

11

/

12

Passed

Description

67%

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 specific and well-scoped to a distinct workflow, but it omits explicit "when to use" trigger guidance and leans on an internal skill name rather than natural user phrasing. Adding a Use-when clause and broader trigger terms would raise the weaker dimensions.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill (e.g., after a completed optimization hunt that needs committing/PR).

Replace or augment the internal '/lading-optimize-hunt' reference with natural user-facing trigger terms like 'commit an optimization', 'open an optimization PR', or 'submit benchmarked optimizations'.

Include common variations of the trigger phrasing to improve discoverability.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "git branch creation, commits, and optional PR" — each tied to a concrete git operation rather than vague abstraction.

3 / 3

Completeness

It states what the skill does but has no "Use when..." trigger clause; per guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant terms ("optimization workflow", "git branch", "commits", "PR") but relies on the internal slash-command name /lading-optimize-hunt and lacks common user-facing variations.

2 / 3

Distinctiveness Conflict Risk

The niche is distinct — it wraps a specific hunt workflow with git automation — so it is unlikely to fire for unrelated skills.

3 / 3

Total

10

/

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
DataDog/lading
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.