session-format-validator
Validate new or changed GitHub Copilot Train-the-Trainer session directories before they are added to the curriculum. Use this skill whenever a user creates, adds, updates, reviews, or asks whether a session under sessions/session-* follows the repository's repeatable format, including required materials, catalog metadata, navigation, and lab access or fallback guidance. Use it even when the user only asks to check a session README or lab.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- session-format-validator
- description
- Validate new or changed GitHub Copilot Train-the-Trainer session directories before they are added to the curriculum. Use this skill whenever a user creates, adds, updates, reviews, or asks whether a session under sessions/session-* follows the repository's repeatable format, including required materials, catalog metadata, navigation, and lab access or fallback guidance. Use it even when the user only asks to check a session README or lab.
- compatibility
- Requires Python 3.11+ and repository access.
02 资源文件 3
- 参考文档evals/evals.json2.0 KB
- 脚本scripts/validate_session.py7.8 KB
- 脚本tests/test_validate_session.py2.4 KB
03 SKILL.md 正文
Session format validator
Use this skill to verify that a training session is ready to join the curriculum. It reports gaps. It does not create files, rewrite curriculum content, or repair metadata unless the user asks for a separate implementation task.
Validate a session
-
Identify the session directory by its full module-local ID, such as
m2-01. Find the matchingsessions/session-m2-01-*directory. If the user provides only a local number, ask which module they mean. -
Run the validator from the repository root:
python .github/skills/session-format-validator/scripts/validate_session.py \ sessions/session-mN-NN-topicAdd
--jsonwhen the result must feed another tool or a CI job. -
Read the session overview, lab, and trainer guide only for findings that need explanation. Do not invent a requirement that the validator did not find.
-
Report results under Passed checks and Needs work. Group failures by materials, metadata, navigation, or lab readiness. Include the exact file and a concrete correction for every failed check.
What the validator checks
- Required materials: overview, trainer guide, lab guide, slides, starter assets, and solution assets.
- Trainer slides: a trainer-facing deck that explains the core concepts before the lab, including an agenda, concrete examples or decision criteria, and a lab handoff. Treat a short agenda-only outline as incomplete teaching material.
- Metadata: the directory name, overview heading, shared catalog entry, and valid module, difficulty, and duration values.
- Navigation: entries in
mkdocs.yml,README.md,curriculum-plan.md, andtracks/full-mastery.md. - Lab readiness: a learner deliverable.
The repository's established template is the reference:
track-template/session-template/.
Result format
Use this structure:
## Session mN-NN — <title>
**Status:** Ready | Needs work
### Passed checks
- <short confirmation>
### Needs work
- `path:line or section` — <what is missing>. <specific correction>.
If every check passes, omit Needs work. If the directory is missing, state that first and stop. Do not claim that a session is ready when required files or curriculum navigation are missing.
Scope boundaries
- Keep existing material intact during validation.
- Do not accept a manual simulation as a replacement for required Copilot access.
- Accept another setup only when it uses the same required Copilot capability and preserves the same completion evidence.
- Do not require a live vendor tool, customer access, or a finished application.
- Use
scripts/validate-labs.shseparately when the user also asks to validate executable starter or solution files.
04 同仓库更多 Skills
release-notes
Write release notes or a CHANGELOG entry from a list of merged pull requests. Use when the user asks for release notes, a changelog entry, "what shipped", or a version summary, even if they don't name the format. Don't use for commit messages, PR descriptions, or marketing copy.
grill-me
Interview the user about a plan, idea, or design before any code is written. Use when the user says "grill me", "interview me", "stress-test this plan", or shares a rough idea and wants it pressure-tested. Do not use for questions that have a factual answer.
decision-interview
Interview a request owner about an unclear request or idea before work is planned. Use when the user says "interview me", "shape this request", or shares a vague request that needs decisions before a brief or issue. Do not use for questions that have a factual answer in the source.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
rvap-brand
Applies the RVAP (Real Value Acceleration Program) brand identity — colors, fonts, logo, and layout patterns — consistently to any GitHub Pages website. Use this skill whenever someone asks to brand, rebrand, apply RVAP/RVAS visual identity, make a site look RVAP, match the brand kit, or transform a GitHub Pages site's look and feel to match RVAP. Also trigger when the user shares an HTML/CSS/MkDocs site and says it should look consistent with other RVAP/RVAS materials, even if they don't explicitly say "brand".