Name: restarting-netalertx-services
Rating: 76 (1 reviews)
Author: netalertx

restarting-netalertx-services

Control NetAlertX services inside the devcontainer. Use this when asked to start backend, start frontend, start nginx, start php-fpm, start crond, stop services, restart services, or check if services are running.

Quality

93%

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

Quality

Content

87%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.

An efficient, highly actionable single-purpose skill with clear sections and executable commands throughout. Its only weakness is the destructive stop-all operation lacking an explicit verify-after-stop checkpoint.

Suggestions

Add a validation step after 'Stop All Services' — e.g., 'Then verify: pgrep -a python3|nginx|php-fpm|crond should return nothing' — to close the destructive-operation loop and raise workflow clarity.

State startup readiness/verification inline (e.g., after starting backend, poll port 5678 or the API on 20212) so Claude can confirm services are actually up rather than relying on '~5 seconds'.

Clarify that the Start Frontend commands are backgrounded and how to confirm nginx/php-fpm are listening on 20211.

Dimension	Reasoning	Score
Conciseness	Lean body with one-line commands and minimal prose ('Backend runs with debugpy on port 5678 for debugging. Takes ~5 seconds to be ready.'), assuming Claude's competence and adding only non-obvious detail. Not score 4 because there is no over-explanation to trim.	5 / 5
Actionability	Copy-paste-ready executable commands for every case — '/services/start-backend.sh', '/services/start-php-fpm.sh &', 'pkill -f ...', 'pgrep -a ...' — covering the common operations. Matches the score-5 anchor for fully executable guidance.	5 / 5
Workflow Clarity	'Stop All Services' runs 'pkill -f php-fpm83\|nginx\|crond\|python3 \|\| true', a destructive/batch operation with no inline validation checkpoint, so workflow_clarity is capped at 3 per the rubric. A separate 'Check Running Services' pgrep command exists but is not tied as a verify step to the destructive stop, keeping it at 3 rather than 4.	3 / 5
Progressive Disclosure	Under 50 lines, self-contained, with well-organized sections (Start Backend, Start Frontend, Start Scheduler, Stop All, Check Running, Service Ports) and no need for external references — the simple-skill exception applies. The /services/*.sh paths are devcontainer targets, not bundle references.	5 / 5
	Total	18 / 20 Passed

Description

100%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.

A concise, third-person description that explicitly states what the skill does and when to use it, with comprehensive natural trigger phrases. Voice and trigger coverage are exemplary.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'start backend, start frontend, start nginx, start php-fpm, start crond, stop services, restart services, or check if services are running' — giving comprehensive coverage of service control. This matches the score-5 anchor for multiple specific concrete actions and is not the score-4 anchor (which implies minor gaps).	5 / 5
Completeness	Explicitly answers both: what ('Control NetAlertX services inside the devcontainer') and when ('Use this when asked to start backend, ... or check if services are running') with concrete trigger phrases. Matches the score-5 anchor exactly.	5 / 5
Trigger Term Quality	Natural phrases a user would actually say — 'start backend', 'start frontend', 'stop services', 'restart services', 'check if services are running' — cover the domain comprehensively including synonyms. Not score 4 because no common natural terms are missing.	5 / 5
Distinctiveness Conflict Risk	Clear niche tied to NetAlertX services inside the devcontainer with distinct, specific triggers and minimal overlap risk with other skills. Not score 4 since the triggers are unambiguous rather than merely 'mostly distinct'.	5 / 5
	Total	20 / 20 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: netalertx/NetAlertX
Path: .github/skills/devcontainer-services/SKILL.md
Commit: 257431b

Reviewed: 2 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.