validate-chalk

Validate chalk.json schema and PROFILE docs for completeness and consistency.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/GeneralJerel/chalk-skills --skill validate-chalk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-chalk
Source: https://github.com/GeneralJerel/chalk-skills/tree/main/skills/validate-chalk
Command: npx skills add https://github.com/GeneralJerel/chalk-skills --skill validate-chalk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate chalk.json schema and PROFILE docs are complete and consistent, ensuring project context is sufficient for skills to operate.

Core Features & Use Cases

  • Validate chalk.json structure and required fields exist (version, project.name)
  • Verify recommended fields presence and value sanity (project.description, project.language, project.framework, project.type, dev.command, dev.port, dev.url, test.command, build.command, routes, sourceLayout.root)
  • Confirm presence and adequacy of PROFILE docs under .chalk/docs (product/PROFILE.md, engineering/PROFILE.md, engineering/coding-style.md, ai/PROFILE.md, design/PROFILE.md)
  • Detect legacy v1 migration files and report gaps
  • Produce a structured validation report and optionally guide auto-fixes

Quick Start

Run the skill at the project root to audit chalk.json and PROFILE docs for completeness and consistency.

Frequently Asked Questions about validate-chalk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate chalk.json schema and required fields in my project?▼

To validate chalk.json schema, run the audit at your project root to check required fields like version and project.name, verify recommended fields for sanity, and output a structured validation report flagging any gaps.

What PROFILE docs are required under the .chalk/docs directory?▼

Required PROFILE docs include product/PROFILE.md, engineering/PROFILE.md, engineering/coding-style.md, ai/PROFILE.md, and design/PROFILE.md. The validation audit confirms their presence and adequacy to ensure sufficient project context.

Can I use this validation audit in CI pipelines to catch project context gaps?▼

Yes, you can apply this validation audit during CI pipelines and pre-run checks to enforce schema rules, detect legacy v1 migration files, and catch context gaps before skill execution.

How do I detect legacy v1 migration files in a Chalk project setup?▼

To detect legacy v1 migration files, run the validation audit at the project root. It identifies outdated files, reports inconsistencies alongside missing chalk.json fields, and optionally guides auto-fixes.

What's the best way to ensure completeness of project context before skill execution?▼

The best way to ensure project context completeness is running a validation audit that checks chalk.json structure, verifies recommended fields like dev.command and routes, and confirms PROFILE docs exist under .chalk/docs.