local-dev

Local development environment setup and commands. Use when helping with dev server, Docker, or local testing.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/local-dev/SKILL.md

Quality

Content

87%

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

The body is an efficient, highly actionable command reference with clean sectioning and appropriate deferral of detail to --help; its main gap is the lack of an explicit validation/confirmation checkpoint around the destructive --clean database reset.

Suggestions

Add an explicit checkpoint before the destructive reset, e.g., run '--verify' and confirm data loss is acceptable before './opik.sh --clean'.

Surface a brief 'after restart, verify health' step (curl the /health-check endpoint) to close the troubleshooting feedback loop.

Consider moving the dense Platform (EM) block to a referenced file or --help excerpt to keep the core Quick Start path even leaner.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with inline comments and no padding about concepts Claude already knows; even the denser Platform section covers repo-specific details (comet mode, JDK versions, nginx proxy) that earn their tokens.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands throughout (dev-runner flags, tail/docker logs, exports, mvn and npm fallbacks), each annotated with its purpose.	3 / 3
Workflow Clarity	Troubleshooting sequences are listed and a --verify status command exists, but the destructive database reset (--clean, 'WARNING: deletes data') has no explicit validation checkpoint before it runs, which caps workflow clarity at 2 per the destructive-operations guideline.	2 / 3
Progressive Disclosure	Content is organized into clear sections (Quick Start, Modes, URLs, Build, Logs, SDK, Troubleshooting) and defers deeper detail (env vars, --platform-build) to the one-level-deep './scripts/dev-runner.sh --help' reference rather than inlining it.	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 cleanly answers both 'what' and 'when' with an explicit Use-when clause, but its action list is generic and its triggers are narrow enough to risk overlap with other development-oriented skills.

Suggestions

Replace the generic 'setup and commands' with a few concrete actions (e.g., 'start/stop the dev server, run builds, lint, migrate the database') to lift specificity.

Expand trigger terms with natural variations users say (e.g., 'run the app locally', 'start the backend', 'rebuild Opik') to improve coverage and distinctiveness.

Add a repo-scoping cue (e.g., 'for the Opik local stack') to reduce conflict with general dev-environment skills.

Dimension	Reasoning	Score
Specificity	Names the domain ("Local development environment setup and commands") but the actions are general categories rather than multiple concrete actions, so it does not reach the 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	It states what the skill does ("Local development environment setup and commands") and provides an explicit "Use when helping with dev server, Docker, or local testing" trigger clause, satisfying both the what and the when.	3 / 3
Trigger Term Quality	"dev server, Docker, or local testing" are natural user terms, but coverage is limited to three phrases and misses common variations like 'run locally', 'start the server', or 'build', placing it between the single-term and full-coverage anchors.	2 / 3
Distinctiveness Conflict Risk	"dev server, Docker, local testing" are common terms that many general development skills would also match, so it is somewhat specific but could still overlap with similar skills.	2 / 3
	Total	9 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: comet-ml/opik
Path: .agents/skills/local-dev/SKILL.md
Commit: aae4650

Reviewed: 5 days 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.