Name: kubernetes-resources
Rating: 71.2 (1 reviews)
Author: confighub

kubernetes-resources

Author a specific Kubernetes resource type as literal YAML in a ConfigHub Unit with best-practice defaults. Use for "create a StatefulSet", "add an Ingress", "set up NetworkPolicy", "I need a CronJob", "add RBAC for my app", "set up autoscaling", "add a PDB". Not for AppConfig-based ConfigMaps (use app-config).

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced skill body with strong validation checkpoints. The main weaknesses are minor verbosity (a repeated time-sensitive note) and progressive disclosure that references bundle files which are not actually present in the bundle.

Suggestions

Add the missing references/yaml-patterns.md, references/functions-catalog.md, and references/cub-cli.md files (or remove the References section) so the disclosed references are real.

State the ingress-nginx retirement guidance once in a single "Deprecated/old patterns" note instead of repeating it in both step 1 and step 3, which would also address the time-sensitive-content conciseness penalty.

Tighten prose explanations of function behavior (e.g. the /me endpoint detail, set-container-volume-mount-path mechanics) since the command examples already convey the action.

Dimension	Reasoning	Score
Conciseness	Mostly lean with concrete commands, but the ingress-nginx retirement note with time-sensitive URLs is stated twice (steps 1 and 3) and several passages over-explain function behavior in prose (e.g. "contacts the server's /me endpoint to confirm the token is still valid (not just local login state)"). It is not a 1 because it is not padded with concepts Claude already knows; it is not a 3 because of the repetition and explanatory prose that could be trimmed.	2 / 3
Actionability	Provides exact, copy-paste-ready `cub` commands with specific flags, named functions (set-container-resources-defaults, ensure-namespaces, vet-schemas), and precise rules (restartPolicy: Never, DNS egress port 53). It is not a 2 because the guidance is fully executable rather than pseudocode or incomplete.	3 / 3
Workflow Clarity	A clear 7-step "loop" with an explicit Validate step (vet-schemas/vet-placeholders/vet-format), plus a Verify chain, Stop conditions, and Preflight gates giving feedback loops for the mutating unit-creation operations. It is not a 2 because validation checkpoints are explicit and present, not missing or implicit.	3 / 3
Progressive Disclosure	The References section is clearly signaled and one-level-deep (yaml-patterns.md, functions-catalog.md, cub-cli.md), but those bundle files do not actually exist in the skill bundle, so the disclosure is aspirational and some detail that belongs in them is inline. It is not a 3 because the referenced files are missing; it is not a 1 because the body is well-sectioned and references are not deeply nested.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 strong description: third-person voice, concrete capabilities, natural trigger phrasings, and explicit use/non-use guidance with disambiguation against a sibling skill. No meaningful gaps; the only nit is that it leans slightly long.

Dimension	Reasoning	Score
Specificity	Lists concrete actions — "Author a specific Kubernetes resource type as literal YAML in a ConfigHub Unit with best-practice defaults" — and enumerates specific resource types (StatefulSet, Ingress, NetworkPolicy, CronJob, RBAC, PDB). It is not a 2 because it names multiple specific concrete actions rather than only a domain and partial actions.	3 / 3
Completeness	Explicitly answers both "what" (author a K8s resource type as literal YAML in a ConfigHub Unit with best-practice defaults) and "when" ("Use for ..." triggers), plus negative guidance ("Not for AppConfig-based ConfigMaps"). It is not a 2 because the when-clause is explicit rather than missing or only implied.	3 / 3
Trigger Term Quality	Embeds verbatim natural user phrasings — "create a StatefulSet", "add an Ingress", "set up NetworkPolicy", "I need a CronJob", "add RBAC for my app", "set up autoscaling", "add a PDB" — giving strong coverage of terms users would actually say. It is not a 2 because common variations are well covered rather than partially present.	3 / 3
Distinctiveness Conflict Risk	Clear niche — ConfigHub Units for specific Kubernetes resource types — with distinct triggers and an explicit disambiguator ("Not for AppConfig-based ConfigMaps (use app-config)"). It is not a 2 because the explicit "Not for" routing makes overlap with sibling skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 6 missing	Warning

	Total	13 / 16 Passed

Repository: confighub/confighub-skills
Commit: 82d0282

Reviewed: 1 day 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.