Output preview skills-validate.preview

---
name: skills:validate
description: Validate skill files meet the standard format and naming conventions Skills operate on either sa…
category: other
runtime: no special runtime
---

# skills:validate output preview

## PART A: Task fit
- Use case: Validate skill files meet the standard format and naming conventions Skills operate on either sandbox (safe) or management (requires approval) targets: | Type | Target | Auto-approve? | Command format | |------|--------|---------------|----------------| | Sandbox | Local Kind cluster, custom HyperShift hosted cluster | YES | Single commands, one per step ….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Use / Validation Checks / Required” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Validate skill files meet the standard format and naming conventions Skills operate on either sandbox (safe) or management (requires approval) targets: | Type | Target | Auto-approve? | Command format | |------|--------|---------------|----------------| | Sandbox | Local Kind cluster, custom HyperShift hosted cluster | YES | Single commands, one per step …”.
- **02** When the source has headings, the agent prioritizes “When to Use / Validation Checks / Required” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

Choose the trigger

The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.

Provide inputs and boundaries

Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.

Validate with a small run

Start with a small task and check whether the result follows “When to Use / Validation Checks / Required”. Inspect diffs, logs, previews, or tests before expanding scope.

Review before delivery

Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.

SKILL.md SKILL.md

---
name: skills:validate
description: Validate skill files meet the standard format and naming conventions Skills operate on either sa…
category: other
source: kagenti/kagenti
---

# skills:validate

## When to use
- Validate skill files meet the standard format and naming conventions Skills operate on either sandbox (safe) or manage…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “When to Use / Validation Checks / Required” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "skills:validate" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> When to Use / Validation Checks / Required
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Command prefix	settings.json pattern
`kubectl get`	`Bash(kubectl get:*)`
`kubectl describe`	`Bash(kubectl describe:*)`
`kubectl logs`	`Bash(kubectl logs:*)`
`helm list`	`Bash(helm list:*)`
`KUBECONFIG=~/clusters/hcp/... kubectl`	`Bash(KUBECONFIG=/clusters/hcp/kagenti-hypershift-custom-/auth/kubeconfig kubectl:*)`
`uv run pytest`	`Bash(uv run pytest:*)`

skills:validate

Decide Fit First

Design Intent

How To Use It

Boundaries And Review

Validate Skill

When to Use

Validation Checks

Required

Command Format (Required)

Recommended

Sandbox vs Management Classification

Sandbox skills (auto-approved)

BAD (chained commands won't match auto-approve patterns)

All Skills

Check Command Format (sandbox skills)

Check Mermaid Diagram Presence

Verify settings.json Coverage

Task Tracking

Discussion

Type	Target	Auto-approve?	Command format
Sandbox	Local Kind cluster, custom HyperShift hosted cluster	YES	Single commands, one per step
Management	Management cluster, AWS resources, git push, destructive ops	NO	Can chain commands (user approves anyway)