server-management
Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.
Install with Tessl CLI
npx tessl i github:lchenrique/politron-ide --skill server-managementOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
33%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description establishes a clear domain (server management) and hints at a pedagogical approach ('Teaches thinking, not commands'), but lacks the explicit trigger guidance needed for Claude to reliably select it. The capabilities listed are conceptual rather than concrete actions, and common user trigger terms are missing.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about server troubleshooting, scaling architecture, or needs help deciding between monitoring approaches'
Include natural trigger terms users would say: 'server down', 'high CPU', 'memory leak', 'horizontal vs vertical scaling', 'which metrics to monitor'
Make capabilities more concrete: instead of 'process management', specify 'deciding when to restart vs. investigate processes, choosing monitoring tools, planning capacity scaling'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (server management) and lists some actions (process management, monitoring strategy, scaling decisions), but these are still fairly abstract concepts rather than concrete actions like 'restart services' or 'configure load balancers'. | 2 / 3 |
Completeness | Describes what the skill covers (server management principles) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The rubric caps completeness at 2 for missing this, and the 'what' is also weak. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'server management', 'process management', 'monitoring', and 'scaling', but misses common variations users might say like 'server down', 'CPU usage', 'memory issues', 'load balancing', or 'DevOps'. | 2 / 3 |
Distinctiveness Conflict Risk | The phrase 'Teaches thinking, not commands' provides some distinction, and 'server management' is a specific domain, but terms like 'process management' and 'monitoring' could overlap with application monitoring or general DevOps skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at concise, principle-based guidance using efficient table formatting. However, it intentionally avoids concrete commands/code, which limits actionability for a skill that Claude would use during actual server management tasks. The content would benefit from either adding executable examples or linking to companion files with implementation details.
Suggestions
Add concrete code examples for at least one tool per category (e.g., a PM2 ecosystem config, a systemd unit file, a health check endpoint)
Include links to detailed implementation guides (e.g., 'See [PM2_SETUP.md](PM2_SETUP.md) for complete configuration')
Add a workflow with validation steps for common operations like deploying a new version or scaling horizontally
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables throughout to maximize information density. No unnecessary explanations of concepts Claude already knows. Every section delivers value without padding. | 3 / 3 |
Actionability | Provides clear decision frameworks and principles but lacks concrete, executable code examples. The skill explicitly teaches 'thinking, not commands' which is intentional, but the guidance remains at the conceptual level rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | The troubleshooting priority section provides a clear sequence, but most content is organized as reference tables rather than workflows. Missing validation checkpoints and feedback loops for operations like scaling or health check implementation. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections and tables, but entirely monolithic with no references to external files for deeper content. Topics like PM2 configuration, systemd setup, or monitoring tool integration could benefit from linked detailed guides. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.