CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

selfhosted-env-doctor

Safe, read-only diagnostic tool for troubleshooting self-hosted stacks, port conflicts, and service failures. Use when: Identify port conflicts between Docker containers and host services; Debug Cloudflare Tunnel configuration and credential path issues; Detect Nginx default_server collisions and syntax errors.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/selfhosted-env-doctor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%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 marketing landing page rather than an operational skill document: it promotes the skill's benefits and purchase terms but provides no executable diagnostic commands, no ordered workflow, and no bundle files — the diagnostic engine itself is explicitly not included. As a result, an agent reading this file could not actually perform the advertised diagnosis.

Suggestions

Add a concrete diagnostic workflow with the actual commands to run (e.g., `ss -tulpn | grep :80` for port conflicts, `nginx -t` for config syntax, `journalctl -u <service> -p err` for systemd failures), in an ordered sequence with a validation step before reporting root causes.

Replace the 'Questions' FAQ and 'Why use this skill' sections (purchase terms, 'lifetime access', time-savings pitch) with operational content — checklists of failure patterns per service and expected output interpretation.

Either include the diagnostic scripts/modules the description advertises (e.g., a `scripts/` directory referenced from the body) or rewrite the body to be self-contained, since the file currently states the original package's logic 'are not in this folder', leaving the advertised capabilities unactionable.

DimensionReasoningScore

Conciseness

Noticeably verbose with padded sections aimed at a human buyer rather than Claude: 'Why use this skill' ('Manually debugging a broken home lab or production server is time-consuming'), a five-question FAQ including 'What exactly is included with my purchase of the selfhosted-env-doctor skill?' and 'lifetime access', plus promotional footer links. It is not 1 because it does not explain concepts Claude already knows — the marketing padding, not concept tutoring, is the problem — and roughly half the body ('What it does', 'How it works', 'Known limitations') is on-topic.

2 / 5

Actionability

Minimal concrete guidance: the body names the tools checked ('Systemd, Netstat/SS, df/du') and what it looks for ('default_server collisions', '.env file permission risks'), but never gives the commands to execute a diagnosis (no 'nginx -t', 'ss -tulpn', 'journalctl -u <unit>', 'systemctl status'), and the only real command shown is inside example output ('sudo systemctl stop apache2...'), not an instruction. This matches 'high-level hints but missing the specific steps to execute'; it is above 1 only because concrete tools, checks, and a worked example are at least named.

2 / 5

Workflow Clarity

No sequence of diagnostic steps exists anywhere in the body — 'How it works' describes outcomes ('checks systemd unit health, validates Nginx configuration syntax, audits listening sockets') in prose without any ordered procedure, and the file admits the actual logic is absent ('Scripts, extension source, and templates from the original package are not in this folder'). This matches the 1 anchor 'steps missing or incoherent; no sequence'; the simple-skill exception does not apply because the single action (run the diagnostic) is not unambiguous — it is unspecified.

1 / 5

Progressive Disclosure

The body has clear section headers ('What it does', 'How it works', 'When to use', 'Known limitations') but no bundle files exist and no references point to the deeper material that clearly exists elsewhere, while ~35% of the content (purchase FAQ, marketing links) belongs in a sales page, not a skill document. This fits 'some structure but could be better organized'; it is above 2 because structure is genuinely present (eight labeled sections), and below 4 because most content is not appropriately placed for an operational skill.

3 / 5

Total

8

/

20

Passed

Description

87%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 is strong: it explicitly states what the skill does and when to use it, with three concrete, natural trigger scenarios in a niche domain. Minor gaps in capability coverage (systemd, database, .env audits claimed in the body are missing from the description) and a few absent user phrasings keep specificity and trigger term quality at 4 rather than 5.

DimensionReasoningScore

Specificity

The 'Use when' clause lists several concrete actions — 'Identify port conflicts between Docker containers and host services', 'Debug Cloudflare Tunnel configuration and credential path issues', 'Detect Nginx default_server collisions and syntax errors' — which matches the 'several specific actions; minor gaps in coverage' anchor. It is not 5 because capabilities the body claims (systemd/journald audits, PostgreSQL authentication, .env permission checks) are absent, and the opening 'diagnostic tool for troubleshooting... service failures' is somewhat generic; it is not 3 because it goes well beyond naming 1-2 actions.

4 / 5

Completeness

Both parts are explicit: 'what' is 'Safe, read-only diagnostic tool for troubleshooting self-hosted stacks, port conflicts, and service failures' and 'when' is the 'Use when:' clause with three concrete trigger scenarios. This clearly matches the anchor 'clearly and explicitly answers both what AND when with concrete trigger phrases'; the 'when' is explicit and specific, so it exceeds the 4 anchor where 'when could be more explicit or specific'.

5 / 5

Trigger Term Quality

Natural terms users would actually say are present — 'port conflicts', 'Docker containers', 'Cloudflare Tunnel', 'Nginx', 'default_server collisions', 'syntax errors', 'self-hosted' — giving good keyword coverage. It falls short of the 5 anchor because common variations users say in this scenario are missing (e.g., 'home lab'/'homelab', 'Raspberry Pi', 'service won't start', '502 bad gateway').

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — read-only diagnostics for self-hosted Linux stacks (Nginx, Cloudflare Tunnel, Docker port conflicts, systemd) — with distinct triggers that would rarely collide with other skills. Voice is third-person/infinitive ('Identify...', 'Detect...'), so no voice penalty applies.

5 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

skills/selfhosted-env-doctor/SKILL.md

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.