Name: target-bind
Rating: 76 (1 reviews)
Author: confighub

target-bind

Bind Units to a delivery Target — ProviderType OCI (publish Unit data to ConfigHub's OCI registry for ArgoCD/Flux to pull) or ConfigHub (apply ConfigHub/YAML config). Both are server workers, no external worker to run. Phrases: set up a target, publish to OCI, attach units to a target. Creates the Target + server worker and attaches Units via cub unit set-target; stops before apply.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

The body is highly actionable and well-sequenced with real validation checkpoints, and it is concise given the domain specificity. Its one clear defect is that two referenced bundle files do not actually exist, leaving the progressive-disclosure structure incomplete.

Suggestions

Create the missing references/cub-cli.md and references/filters-and-queries.md files referenced in the References section, or remove those citations.

Tighten the 'What a Target is' OCI paragraph slightly; the 'echoes the data back as live state' detail could move to a reference if it is not needed inline.

Consider promoting the bulk-binding --where pattern and TargetID IS NOT NULL verification into a short inline example block so the common path is self-contained.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable domain-specific detail (ConfigHub semantics Claude does not already know) and avoids generic padding; every section earns its tokens, even if the OCI explanation is prose-heavy.	3 / 3
Actionability	Provides fully executable, copy-paste-ready bash commands with concrete flags for both OCI and ConfigHub providers, single-unit and bulk attach, plus a server-worker create command.	3 / 3
Workflow Clarity	A clearly sequenced loop (preflight → ensure worker → create target → attach → hand off) backed by an explicit Verify chain and Stop conditions that validate bulk blast radius, so batch operations are not left unchecked.	3 / 3
Progressive Disclosure	Sections are well organized, but the References section cites 'references/cub-cli.md' and 'references/filters-and-queries.md', and neither file exists in the bundle — dead references keep this below 3.	2 / 3
	Total	11 / 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.

The description is specific, trigger-rich, and self-bounding: it names concrete actions, surfaces natural user phrases, and clearly delimits the skill's scope. It is written in third person with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions including 'publish Unit data to ConfigHub's OCI registry', 'apply ConfigHub/YAML config', and 'attaches Units via cub unit set-target', with a named CLI command and provider types.	3 / 3
Completeness	Clearly answers what (create Target + server worker, attach Units) and when via an explicit 'Phrases:' trigger list and the 'stops before apply' boundary, satisfying the 'Use when...' trigger requirement.	3 / 3
Trigger Term Quality	Explicitly surfaces natural user phrases — 'set up a target, publish to OCI, attach units to a target' — giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Occupies a narrow ConfigHub-specific niche (OCI/ConfigHub providers, cub unit set-target) with a crisp 'stops before apply' boundary, making conflict with other 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: 2 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.