CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

linux

Linux administration and networking diagnostics — DNS, load balancing, VPCs, kernel tuning, and connectivity troubleshooting.

Quality

82%

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

The canonical home for this skill is linux in nitinjain999/platform-skills

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exceptionally strong operational skill: lean, fully executable commands with exact flags, values, thresholds, and expected outputs, plus per-topic validation steps, error-recovery tables, and a global validation-and-rollback mandate. Its one structural weakness is progressive disclosure: the twice-referenced references/linux-networking.md does not exist in the bundle, and heavy per-topic detail (systemd, cgroups, kernel tuning) is inlined rather than split into reference files.

Suggestions

Create references/linux-networking.md (or remove the two references to it) — the file is cited twice but is missing from the bundle, which will cause a read failure at runtime.

Move the systemd, cgroups, and kernel-tuning detail (config dumps, tables, multi-command procedures) into per-topic reference files, keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

Add inline validation examples to the lb, vpc, and security-groups sections (e.g. a curl health-check against a target) so every topic carries the same explicit checkpoint pattern as dns/process/disk/network.

DimensionReasoningScore

Conciseness

Quotes: "net.core.somaxconn = 32768 # listen() backlog per socket; default 128 is too low for busy nodes", "If throttle rate > 25%, either remove the CPU limit (preferred) or increase it" — nearly every token is a command, flag, value, or operational decision; no conceptual explanation of things Claude already knows, matching the anchor "lean and efficient; assumes Claude's competence; every token earns its place." Not 4: the inline comments carry non-obvious operational context (specific defaults, thresholds) rather than trimmable over-explanation.

5 / 5

Actionability

Quotes: "journalctl -u <service> -p err -b", "stat -f /sys/fs/cgroup # type 0x63677270 = cgroupv2", "systemd-analyze verify /etc/systemd/system/<service>.service", and complete copy-paste-ready sysctl config blocks — exact commands with placeholders and expected outputs cover the common cases, matching the anchor "fully executable; copy-paste ready code or commands." Not 4: there are no pseudocode or placeholder-only gaps; validation commands include expected results (e.g. "must return an IP").

5 / 5

Workflow Clarity

Quotes: numbered frameworks per topic ("1. Use the connectivity ladder: L3 (ping) → L4 (nc -zv) → L7 (curl -v)"), explicit validation checkpoints ("**Validation:** `ss -tulnp | grep LISTEN` — confirms ports are listening"), feedback loops (the symptom→cause→fix table for systemd failures, "systemctl status <service> confirms service is running after changes"), and a global mandate "Always end with: Validation command — Rollback", matching the anchor "clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes." Not 4: the lb/vpc/security-groups sections lack inline validation blocks, but the global validation+rollback mandate and troubleshoot checklist (steps 5–6: "Validation steps", "Rollback plan") close those gaps.

5 / 5

Progressive Disclosure

Quotes: "Read `references/linux-networking.md` before responding" and "Apply the structured checklist from `references/linux-networking.md`" — but no references/ directory exists in the bundle, so both references are broken. Meanwhile ~100 lines of systemd/cgroups/kernel detail (full config dumps, tables, multi-command procedures) that clearly belongs in separate reference files is inlined in SKILL.md, matching the anchor "content that should be separate is inline." Not 2: the body itself is well structured with clear headers and the reference, while missing on disk, is clearly signaled and one level deep — not "minimal structure" or "buried references." Not 4: the bundle structure (a missing referenced file plus monolithic 230-line body) is a real organization failure, not a minor gap.

3 / 5

Total

18

/

20

Passed

Description

66%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 names a clear domain and five concrete topic areas with natural trigger terms, but it is missing any 'Use when...' clause, which both caps completeness and weakens its routing function. It also under-represents the skill's actual scope (systemd, disk/inodes, cgroups/OOMKill, security groups are all major body sections absent from the description).

Suggestions

Add an explicit trigger clause, e.g. "Use when diagnosing DNS resolution failures, load balancer health checks, VPC connectivity, disk/inode exhaustion, OOMKills, or systemd service failures on Linux hosts."

Include trigger terms for the topics the body actually covers but the description omits: systemd, disk/inode exhaustion, OOMKill/cgroups, and security groups/NSGs.

Use action verbs ("Diagnoses...", "Tunes...") instead of noun phrases to sharpen the 'what' alongside the existing topic list.

DimensionReasoningScore

Specificity

Quotes: "Linux administration and networking diagnostics — DNS, load balancing, VPCs, kernel tuning, and connectivity troubleshooting" — five concrete capability areas are named, matching the anchor "lists several specific actions; minor gaps in coverage." Not 5: items are domain nouns rather than action verbs, and it omits body topics like systemd, disk, cgroups, and security groups. Not 3: well beyond naming just 1–2 concrete areas.

4 / 5

Completeness

The 'what' is clear ("Linux administration and networking diagnostics — DNS, load balancing, VPCs, kernel tuning, and connectivity troubleshooting"), but no 'when' appears anywhere — no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines. Not 4: there is no usage condition at all, even a weak one.

3 / 5

Trigger Term Quality

Quotes: "DNS", "load balancing", "VPCs", "kernel tuning", "connectivity troubleshooting" — natural phrases users would say when they need this skill. Not 5: the skill body covers systemd, disk/inode exhaustion, OOMKill/cgroups, and security-group debugging, none of which appear as trigger terms. Not 3: keyword coverage is good, not merely "some relevant keywords."

4 / 5

Distinctiveness Conflict Risk

Quotes: "Linux administration and networking diagnostics" combined with "DNS, load balancing, VPCs, kernel tuning" carves a fairly distinct platform-engineering niche. Not 5: "load balancing" and "VPCs" overlap with general cloud/Terraform networking skills. Not 3: the combination of Linux host-level diagnostics with these specific areas is specific enough to avoid broad conflicts.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

nitinjain999/platform-skills

Path

plugins/platform-skills/skills/linux/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.