handbook-validator

Name: handbook-validator
Author: girijashankarj

27stars3forks

How to install handbook-validator?

girijashankarj/cursor-handbook/handbook-validator

$npx -y skills add girijashankarj/cursor-handbook --skill handbook-validator

Installs into the current project.

Summary

Validate cursor-handbook structure, config, and component integrity. Use when the user asks to validate the setup, check for issues, or verify the handbook installation.

Files · 1

View on GitHub

SKILL.md

1	# Skill: Handbook Validator
2
3	Validate that the cursor-handbook structure is correct, configuration is present, and components are well-formed.
4
5	## Trigger
6	When the user asks to validate the handbook, check the setup, verify configuration, or troubleshoot missing components.
7
8	## Prerequisites
9	- [ ] Inside a project with `.cursor/` directory
10
11	## Usage
12
13	Run the bundled script from the project root:
14
15	```bash
16	scripts/validate.sh
17	```
18
19	## Steps
20
21	### Step 1: Run Basic Validation
22	- [ ] Execute `scripts/validate.sh` using the Shell tool
23	- [ ] Capture pass/fail output
24	- [ ] The script checks:
25	- `.cursor/` directory exists
26	- `project.json` or `project.json.template` present
27	- `hooks.json` present
28	- At least one `.mdc` rule file exists
29
30	### Step 2: Extended Validation (if basic passes)
31	- [ ] Check for unresolved `{{PLACEHOLDER}}` values in `project.json`
32	- [ ] Verify all skill folders contain a `SKILL.md`
33	- [ ] Verify all agent files have a title and description
34	- [ ] Check that hook scripts referenced in `hooks.json` exist and are executable
35	- [ ] Verify `.mdc` rule files have valid frontmatter (`description`, `globs`, or `alwaysApply`)
36
37	### Step 3: Report Results
38	- [ ] Present a summary table:
39
40	\| Check \| Status \| Details \|
41	\|-------\|--------\|---------\|
42	\| `.cursor/` exists \| PASS/FAIL \| — \|
43	\| `project.json` configured \| PASS/WARN \| Placeholder count \|
44	\| Rules present \| PASS/FAIL \| Count of `.mdc` files \|
45	\| Skills valid \| PASS/WARN \| Count with/without `SKILL.md` \|
46	\| Hooks wired \| PASS/WARN \| Missing scripts \|
47
48	### Step 4: Suggest Fixes
49	- [ ] For each FAIL/WARN, provide a specific fix action
50	- [ ] Prioritize: FAIL items first, then WARN items
51	- [ ] Offer to auto-fix simple issues (e.g., create missing `project.json` from template)
52
53	## Rules
54	- NEVER modify files without user confirmation
55	- Report all issues, don't stop at the first failure
56	- Distinguish between FAIL (blocking) and WARN (advisory)
57
58	## Completion
59	Validation report with clear pass/fail status for each check and actionable fix suggestions for any issues found.
60
61	## If a Step Fails
62	- `.cursor/` not found: Suggest running the `cursor-setup` skill to bootstrap
63	- No rules found: Suggest copying from examples or running setup
64	- Permission errors: Check file permissions with `ls -la`

People who liked this also viewed

6 picks

Type

handbook-validator

27stars3forks

View on GitHub

How to install handbook-validator?

girijashankarj/cursor-handbook/handbook-validator

$npx -y skills add girijashankarj/cursor-handbook --skill handbook-validator

Installs into the current project.

Summary

Validate cursor-handbook structure, config, and component integrity. Use when the user asks to validate the setup, check for issues, or verify the handbook installation.

Files · 1

View on GitHub

SKILL.md

1	# Skill: Handbook Validator
2
3	Validate that the cursor-handbook structure is correct, configuration is present, and components are well-formed.
4
5	## Trigger
6	When the user asks to validate the handbook, check the setup, verify configuration, or troubleshoot missing components.
7
8	## Prerequisites
9	- [ ] Inside a project with `.cursor/` directory
10
11	## Usage
12
13	Run the bundled script from the project root:
14
15	```bash
16	scripts/validate.sh
17	```
18
19	## Steps
20
21	### Step 1: Run Basic Validation
22	- [ ] Execute `scripts/validate.sh` using the Shell tool
23	- [ ] Capture pass/fail output
24	- [ ] The script checks:
25	- `.cursor/` directory exists
26	- `project.json` or `project.json.template` present
27	- `hooks.json` present
28	- At least one `.mdc` rule file exists
29
30	### Step 2: Extended Validation (if basic passes)
31	- [ ] Check for unresolved `{{PLACEHOLDER}}` values in `project.json`
32	- [ ] Verify all skill folders contain a `SKILL.md`
33	- [ ] Verify all agent files have a title and description
34	- [ ] Check that hook scripts referenced in `hooks.json` exist and are executable
35	- [ ] Verify `.mdc` rule files have valid frontmatter (`description`, `globs`, or `alwaysApply`)
36
37	### Step 3: Report Results
38	- [ ] Present a summary table:
39
40	\| Check \| Status \| Details \|
41	\|-------\|--------\|---------\|
42	\| `.cursor/` exists \| PASS/FAIL \| — \|
43	\| `project.json` configured \| PASS/WARN \| Placeholder count \|
44	\| Rules present \| PASS/FAIL \| Count of `.mdc` files \|
45	\| Skills valid \| PASS/WARN \| Count with/without `SKILL.md` \|
46	\| Hooks wired \| PASS/WARN \| Missing scripts \|
47
48	### Step 4: Suggest Fixes
49	- [ ] For each FAIL/WARN, provide a specific fix action
50	- [ ] Prioritize: FAIL items first, then WARN items
51	- [ ] Offer to auto-fix simple issues (e.g., create missing `project.json` from template)
52
53	## Rules
54	- NEVER modify files without user confirmation
55	- Report all issues, don't stop at the first failure
56	- Distinguish between FAIL (blocking) and WARN (advisory)
57
58	## Completion
59	Validation report with clear pass/fail status for each check and actionable fix suggestions for any issues found.
60
61	## If a Step Fails
62	- `.cursor/` not found: Suggest running the `cursor-setup` skill to bootstrap
63	- No rules found: Suggest copying from examples or running setup
64	- Permission errors: Check file permissions with `ls -la`

People who liked this also viewed

6 picks

Type