validating-training

Sterne1

Forks0

Aktualisiert17. Juli 2026 um 22:45

Use when the learner or a maintainer asks to verify this training package's integrity ("validate the training", "is this package intact?"), or when files seem missing, links broken, or authoritative content accidentally modified.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

hopchouinard

hopchouinard/Training-Generator

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Sonstige HochschullehrerBildungs- und Bibliotheksberufe·SOC 25-1199

SKILL.md

readonly

name	validating-training
description	Use when the learner or a maintainer asks to verify this training package's integrity ("validate the training", "is this package intact?"), or when files seem missing, links broken, or authoritative content accidentally modified.

Validating the Training Package

Run the package self-test from the repository root: node scripts/selftest.mjs It verifies structure against training-manifest.json, validates the curriculum, version, and progress-template files against their schemas in schemas/, checks that every curriculum path and relative Markdown link resolves, that identifiers are unique and stable-format, and that no template placeholders survive.
Check for accidental modification of authoritative content: git status --porcelain — anything modified outside workspace/ and state/ is suspect. Offer git checkout -- <path> to restore, after confirming the change wasn't intentional.
Report results honestly: what passed, what failed, exact messages. If the package itself is defective (not just locally modified), the fix is regeneration from the source project — this clone can't repair missing generated content.
If state/progress.json is implicated, use node scripts/progress.mjs read / recover rather than editing state by hand.

Mehr aus diesem Repository

gleiches Repository

generating-training

hopchouinard/Training-Generator

Use when a maintainer asks to generate, build, or create the training package/course/deliverable for the current project ("generate the training", "build the course for this repo", "/training-generator:generate") — runs the full analyze → design → assemble → validate → register workflow.

2026-07-171

regenerating-training

hopchouinard/Training-Generator

Use when a maintainer asks to regenerate, refresh, or update an existing training package after source changes ("regenerate the training", "the docs changed, update the course", "/training-generator:regenerate").

2026-07-171

validating-package

hopchouinard/Training-Generator

Use when a maintainer asks to validate, check, or verify a generated training package ("validate the training package", "/training-generator:validate") without regenerating it.

2026-07-171

answering-questions

hopchouinard/Training-Generator

Use when the learner asks any question — about the current lesson, a later topic, their own use case, design rationale, comparisons with other tools, or anything else during the {{PROJECT_NAME}} course.

2026-07-171

conducting-training

hopchouinard/Training-Generator

Use when the learner asks to start, begin, or continue the {{PROJECT_NAME}} training in any natural phrasing ("Let's start the training.", "Start the course.", "Continue my training.", "let's keep going") — conducts the interactive course from durable local progress.

2026-07-171

facilitating-exercises

hopchouinard/Training-Generator

Use when the current activity is an exercise, when the learner asks to try an exercise, needs a hint, wants their exercise work checked, or wants to skip an exercise.

2026-07-171

name	validating-training
description	Use when the learner or a maintainer asks to verify this training package's integrity ("validate the training", "is this package intact?"), or when files seem missing, links broken, or authoritative content accidentally modified.

Validating the Training Package

Run the package self-test from the repository root: node scripts/selftest.mjs It verifies structure against training-manifest.json, validates the curriculum, version, and progress-template files against their schemas in schemas/, checks that every curriculum path and relative Markdown link resolves, that identifiers are unique and stable-format, and that no template placeholders survive.
Check for accidental modification of authoritative content: git status --porcelain — anything modified outside workspace/ and state/ is suspect. Offer git checkout -- <path> to restore, after confirming the change wasn't intentional.
Report results honestly: what passed, what failed, exact messages. If the package itself is defective (not just locally modified), the fix is regeneration from the source project — this clone can't repair missing generated content.
If state/progress.json is implicated, use node scripts/progress.mjs read / recover rather than editing state by hand.