server-management

Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.

Quality

72%

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/server-management/SKILL.md

Quality

Content

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

The body is exceptionally concise and well-structured for a single-file principle-based skill, but its deliberately command-free stance leaves it low on actionability, and the workflows lack explicit validation checkpoints for risky operations.

Suggestions

Add one or two concrete, copy-paste-ready examples per major area (e.g. a sample PM2 ecosystem config, a logrotate snippet, or a systemd unit) so the guidance is executable, not just conceptual.

Insert validation checkpoints into destructive or batch workflows (e.g. after a restart, verify the process and health check before declaring success; after scaling, confirm new instances pass health checks).

Optionally split detailed tool configs into a reference file and signal it from the overview, which would let the body stay lean while recovering actionability.

Dimension	Reasoning	Score
Conciseness	Lean table-driven body with almost no prose padding; it assumes Claude's competence and avoids explaining what servers, logs, or monitoring are, so every token earns its place.	5 / 5
Actionability	Despite the "teaches thinking, not commands" framing, the body offers only high-level hints (e.g. "Simple: Just return 200", "Profile first, then scale") with no concrete commands, config snippets, or executable examples to act on.	2 / 5
Workflow Clarity	The Troubleshooting Priority section gives a numbered sequence, but it is a diagnostic checklist rather than an executable workflow, and destructive or batch operations (restarts, scaling, firewall changes) lack validation checkpoints, capping clarity at 3.	3 / 5
Progressive Disclosure	A short, well-organized single-file skill under 50 lines with no need for external references; sections are clearly headed and self-contained, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	15 / 20 Passed

Description

80%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 strong, specific description that names concrete capabilities and supplies a clear use-when clause via when_to_use. It is held back only by slightly limited synonym coverage and the trigger guidance being split across frontmatter fields.

Suggestions

Fold the when_to_use trigger phrases into the description itself (e.g. append 'Use when managing servers, configuring PM2, setting up monitoring, or planning scaling') so both what and when sit in one field.

Add common user-facing synonyms such as 'uptime', 'alerts', 'process crashes', or 'auto-restart' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities ("Process management, monitoring strategy, and scaling decisions") and explicitly names the skill's pedagogical angle ("Teaches thinking, not commands"), giving comprehensive coverage of what the skill covers.	5 / 5
Completeness	The description answers "what" clearly and the when_to_use field provides a "when" clause ("When managing servers, configuring process managers (PM2), setting up monitoring, or planning scaling strategies"), but the when guidance lives in a separate frontmatter field rather than the description itself and could be slightly more specific.	4 / 5
Trigger Term Quality	Strong natural terms ("managing servers", "PM2", "monitoring", "scaling strategies") a user would actually say, but it misses common synonyms and concrete trigger variants like "uptime" or "alerts"; a few natural phrases are absent.	4 / 5
Distinctiveness Conflict Risk	The server-management niche with PM2/monitoring/scaling triggers is fairly distinct and unlikely to collide with unrelated skills, with only minor overlap risk against generic devops or deployment skills.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/server-management/SKILL.md
Commit: 211561c

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