CtrlK
BlogDocsLog inGet started
Tessl Logo

devcontainer-management

Guide for identifying, managing, and running commands within the NetAlertX development container. Use this when asked to run commands, testing, setup scripts, or troubleshoot container issues.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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

A tight, actionable body with executable Docker commands and good decision branching. The main gap is the absence of a validation/verification checkpoint before or after the destructive setup script.

Suggestions

Add a validation checkpoint around the destructive setup.sh step (e.g., confirm the container ID, warn the user about DB/tmp resets before running, and verify services restarted successfully afterward) so workflow_clarity is not capped.

Clarify the abstract '/services/' reference — name the specific scripts available or point to where they are listed so the 'Use the scripts in /services/' line is fully actionable.

Consider a brief verification command (e.g., a health check or `docker exec ... ps aux | grep python`) to confirm the environment is healthy after setup.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanation of Docker concepts, just the commands and decision branches needed, so every token earns its place.

3 / 3

Actionability

Provides concrete, executable commands ('docker ps --format ... | grep netalertx', 'docker exec <CONTAINER_ID> bash .../setup.sh') with only an intentional <CONTAINER_ID> placeholder to fill from the prior step, matching copy-paste-ready guidance.

3 / 3

Workflow Clarity

The find-container then run-command sequence is clear with explicit no-container/multiple-container branches, but the destructive setup.sh ('wipes /tmp ramdisks, resets DBs, restarts services') lacks any validation/verification checkpoint, capping this at 2 per the destructive-operation guideline.

2 / 3

Progressive Disclosure

Under 50 lines with no bundle files and no need for external references; content is organized into two clear signaled sections (Finding the Container, Running Commands), which satisfies the simple-skill threshold for a top score.

3 / 3

Total

11

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 well-constructed description with an explicit Use-when trigger clause, natural trigger terms, and a clearly scoped niche. The only weakness is the mildly abstract verb 'managing' in the capability list.

DimensionReasoningScore

Specificity

Names the domain ('NetAlertX development container') and concrete actions ('identifying... running commands'), but 'managing' is abstract and the action list is not comprehensive, matching the level-2 anchor rather than the multiple-specific-actions level-3 anchor.

2 / 3

Completeness

It states what the skill does ('Guide for identifying, managing, and running commands within the NetAlertX development container') and includes an explicit 'Use this when...' trigger clause, satisfying both what and when.

3 / 3

Trigger Term Quality

'run commands, testing, setup scripts, or troubleshoot container issues' are natural phrases a user would say when needing this skill, giving good coverage of common variations per the level-3 anchor.

3 / 3

Distinctiveness Conflict Risk

The NetAlertX development container niche is specific and the triggers are scoped to container/runtime work, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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
netalertx/NetAlertX
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.