lading-optimize-submit

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

Quality

47%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/lading-optimize-submit/SKILL.md

Quality

Discovery

17%

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 too terse and relies on internal jargon ('/lading-optimize-hunt') without explaining what the optimization actually targets. It lacks a 'Use when...' clause entirely, making it difficult for Claude to know when to select this skill. The git-related actions are somewhat specific but don't clarify the core purpose of the skill.

Suggestions

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user wants to run a lading performance optimization and automatically manage the git workflow for the changes.'

Replace or explain the internal reference '/lading-optimize-hunt' — describe what kind of optimization it performs (e.g., performance tuning, resource optimization) so Claude can match user intent.

Include natural keywords users might say, such as 'performance optimization', 'benchmark', 'lading', 'optimize and commit', or whatever domain-specific terms apply.

Dimension	Reasoning	Score
Specificity	Names the domain (optimization workflow) and some actions (git branch creation, commits, optional PR), but 'wraps /lading-optimize-hunt with git automation' is vague about what the actual optimization does. The concrete actions listed are mostly git-related scaffolding rather than the core capability.	2 / 3
Completeness	The description partially addresses 'what' (optimization workflow with git operations) but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	The description uses internal/technical jargon like '/lading-optimize-hunt' and 'git automation' which users would not naturally say. Terms like 'optimization workflow' are generic and lack natural trigger terms a user would use when needing this skill.	1 / 3
Distinctiveness Conflict Risk	The reference to '/lading-optimize-hunt' and the specific combination of optimization + git workflow provides some distinctiveness, but 'optimization workflow with git branch creation, commits, and optional PR' could overlap with many CI/CD or git workflow skills.	2 / 3
	Total	6 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured workflow skill with clear phasing, explicit checkpoints, and highly actionable bash commands throughout. Its main weakness is some verbosity in Phase 2 explaining responsibility boundaries between skills, and the inability to verify referenced assets (commit-template.txt) since no bundle was provided. Overall it serves its purpose well as a git automation wrapper around the optimization hunt workflow.

Suggestions

Trim Phase 2's 'The hunt will/does NOT' lists into a single concise sentence like 'The hunt handles analysis, benchmarks, and review but NOT git operations (branch/commit/push/PR) — those are handled below.'

Include the actual commit-template.txt content in the bundle or inline a minimal version, since the skill references it but it's not available for verification.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary explanation, particularly the detailed list of what the hunt 'does' and 'does NOT' do (Phase 2), which is more about clarifying responsibility boundaries than providing actionable guidance. The commit example and PR template are appropriately detailed since they serve as templates.	2 / 3
Actionability	Provides fully executable bash commands throughout, including specific git commands, branch naming conventions with examples, a complete commit message template with real benchmark data, and a full gh pr create command with heredoc body. Everything is copy-paste ready with clear placeholders.	3 / 3
Workflow Clarity	Clear phased sequence (0-4) with explicit checkpoints: pre-flight check, dirty working directory stop-gate, critical return instruction after hunt phase, and validation checklist in the PR body. The 'STOP if working directory is dirty' and 'CRITICAL: you MUST return here' are effective validation/control flow gates.	3 / 3
Progressive Disclosure	References external skills (/lading-optimize-hunt, /lading-preflight) and an asset file (commit-template.txt) appropriately, but no bundle files were provided to verify these references. The inline PR template and commit example are somewhat lengthy but justified as templates. The content is well-structured with phases but the Phase 2 responsibility clarification could be more concise or moved to a reference.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: DataDog/lading
Commit: 01ef8d7

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

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.