homelab-topology-mapper

Maps Proxmox cluster topology including nodes, VMs, containers, storage, and network layout.

Quality

65%

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 ./skills/homelab-topology-mapper/SKILL.md

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.

A well-organized, lean instruction body for a read-only enumeration skill, with a clear step sequence and output schema. Its main weaknesses are missing validation/feedback steps in the workflow and reliance on a referenced file that does not exist in the bundle, which weaken actionability and workflow clarity.

Suggestions

Add validation checkpoints to the workflow (e.g., after Connect, verify authentication succeeded before enumerating; after enumeration, confirm every node responded before rendering).

Replace or substantiate the `mcp/proxmox-mcp.json` reference with the actual MCP tool names/commands to invoke, since that file is absent from the bundle.

Provide at least one concrete API/MCP call example (e.g., the tool to list nodes and its expected response fields) so the guidance is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations or padding, and well-organized sections earn their place; the intro paragraph slightly restates the component list already in the frontmatter description and could be trimmed.	4 / 5
Actionability	Provides concrete enumeration targets with specific fields ("ID, name, status, CPU, RAM") and a defined output schema, but gives no executable API/MCP tool calls and references `mcp/proxmox-mcp.json`, which is absent from the bundle, leaving key details missing.	3 / 5
Workflow Clarity	Eight steps are clearly sequenced (Connect → List nodes/VMs/containers/storage/networks → Output → Store), but there are no validation checkpoints (e.g., verify API connectivity or confirm all nodes responded), and batch enumeration caps this dimension at 3.	3 / 5
Progressive Disclosure	Well-structured with clear sections and one-level-deep external references (Proxmox API wiki, proxmox-mcp repo); minor gap is the dangling internal reference to `mcp/proxmox-mcp.json` which is not present in the bundle.	4 / 5
	Total	14 / 20 Passed

Description

70%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 clear, domain-specific description that concretely enumerates the topology components it maps, but it omits any "Use when" trigger guidance, which limits its completeness. Distinctiveness is strong with negligible conflict risk.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when preparing a change to the Proxmox cluster or when the user asks for a current topology/inventory snapshot') to lift completeness.

Include synonyms a user might say ('QEMU', 'LXC', 'virtual machines') to improve trigger-term coverage.

Name the concrete action(s) more precisely (e.g., 'Enumerates and renders') instead of the single verb 'Maps'.

Dimension	Reasoning	Score
Specificity	Names the domain ("Proxmox cluster topology") and enumerates several concrete components ("nodes, VMs, containers, storage, and network layout"), but uses a single action verb ("Maps") rather than multiple distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	Clearly answers the "what" (maps cluster topology across named component types) but provides no "Use when..." clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Strong natural keywords a homelab user would say ("Proxmox", "cluster", "topology", "VMs", "containers", "network layout"), though it omits common synonyms like "QEMU", "LXC", or "virtual machines" found in the body.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Proxmox cluster topology mapping) with distinct, domain-specific triggers and minimal overlap risk; companion skills target change-planning and safety, not read-only enumeration.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: pvnkmnk/AgenticSelfHostSkills
Path: skills/homelab-topology-mapper/SKILL.md
Commit: 0f62e6b

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