Name: server-management
Rating: 50.4 (1 reviews)
Author: administrakt0r

server-management

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

Quality

55%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/server-management/SKILL.md

The canonical home for this skill is server-management in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

61%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 a lean, well-organized reference of principles and decision tables that respects token budget and assumes Claude's knowledge, but its intentional "thinking not commands" stance leaves guidance short of executable action and without validation checkpoints.

Suggestions

Add minimal executable anchors alongside principles (e.g., a sample PM2 ecosystem config, a logrotate snippet, or a systemd unit) so guidance is actionable, not just descriptive.

Insert a validation/checklist step into the troubleshooting flow and any operational decision (e.g., "verify service responds with 200 after restart") to add feedback loops.

Tighten or remove the generic trailing line "This skill is applicable to execute the workflow or actions described in the overview." which adds no information.

Dimension	Reasoning	Score
Conciseness	The body is compact reference tables that assume Claude's competence (no explaining what PM2 or Grafana is), with only minor trimmable bits like the obvious "HTTP 200 = Service responding" row and the vague filler "When to Use" line, fitting anchor 4 over 5 because of those small instances.	4 / 5
Actionability	It names concrete tools (PM2, systemd, Grafana, Sentry, UptimeRobot) and decision rules, but deliberately omits execution detail ("teaches thinking, not commands"), leaving guidance concrete yet incomplete, matching anchor 3.	3 / 5
Workflow Clarity	Section 7 provides a clear ordered troubleshooting sequence, but there are no validation checkpoints and most of the skill is reference tables rather than workflows, fitting anchor 3; the destructive/batch cap does not apply since these are diagnostic/principle tasks.	3 / 5
Progressive Disclosure	It is a single self-contained file organized into 8 clearly headed numbered sections with no nested references; at ~160 lines it exceeds the 50-line simple-skill exception and does not split overview from detail, so anchor 4 fits better than 5.	4 / 5
	Total	14 / 20 Passed

Description

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

The description clearly scopes a distinct niche (server/production operations) and names the core domains, but it stays at a principle/philosophy level with no concrete actions and no "Use when" trigger guidance, capping completeness and specificity.

Suggestions

Add a "Use when..." trigger clause naming concrete situations users would say (e.g., "Use when managing production servers, setting up process monitoring, or making scaling decisions").

Replace abstract phrasing ("principles and decision-making", "teaches thinking") with 1-2 concrete capabilities (e.g., "restart and cluster Node.js processes with PM2", "configure log rotation and alerting").

Include more natural trigger synonyms present in the body, such as logs, troubleshooting, health checks, and uptime, to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	It names the domains ("Process management, monitoring strategy, and scaling decisions") but the actions are abstract ("principles and decision-making", "Teaches thinking, not commands") with no concrete actions, matching anchor 2 rather than 3 which requires 1-2 concrete actions.	2 / 5
Completeness	There is a clear "what" (server management principles across process/monitoring/scaling) but no "Use when..." trigger clause, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural terms like "server management", "process management", "monitoring", and "scaling" are present, but common variations covered in the body (logs, troubleshooting, security, uptime, production operations) are missing, fitting anchor 3 over 4.	3 / 5
Distinctiveness Conflict Risk	"Server management" is a clear niche with low conflict risk and only minor overlap with devops/deployment skills; it falls short of anchor 5 because no explicit trigger phrases are included.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/server-management/SKILL.md
Commit: 57c135b

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