validate
/validate
Validate a routine .md file's structure without calling the API. Checks frontmatter, cron schedule rules, model field, allowed_tools, sources, mcp_connections, and prompt body. Invoke when the user says "validate <file>", "lint <file>", or "validate" (no file = validate everything in the workspace).
- Author
- hamzafer ↗
- Repository
- claude-routines ↗
- Licence
- MIT
- Last repository change
- 18.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 18.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Validate a routine .md file's structure without calling the API. Checks frontmatter, cron schedule rules, model field, allowed_tools, sources, mcp_connections, and prompt body. Invoke when the user says "validate <file>", "lint <file>", or "validate" (no file = validate everything in the workspace).
Triggers from the description
Original author description
Validate a routine .md file's structure without calling the API. Checks frontmatter, cron schedule rules, model field, allowed_tools, sources, mcp_connections, and prompt body. Invoke when the user says "validate <file>", "lint <file>", or "validate" (no file = validate everything in the workspace).
How it works
- Per-file checks
- Output format
- See also
SKILL.md preview
---
name: validate
description: Validate a routine .md file's structure without calling the API. Checks frontmatter, cron schedule rules, model field, allowed_tools, sources, mcp_connections, and prompt body. Invoke when the user says "validate <file>", "lint <file>", or "validate" (no file = validate everything in the workspace).
---
# claude-routines:validate
Lint a routine file before deploying. Never calls the API. Run this whenever you're about to `deploy`.
## Per-file checks
Run these in order. Stop the file at the first error; collect all warnings.
### 1. Frontmatter parses
Must be valid YAML between the opening and closing `---`. If parsing fails, report the YAML error and stop.
### 2. Required fields
- `name` (string, non-empty)
- `env_id` (string starting with `env_`)
- Exactly one of `cron` (string) or `run_once_at` (RFC3339 UTC timestamp). Both present is an error (`conflicting fields`). Neither present is an error (`missing trigger`).
### 3. Cron rules
When `cron` is set:
- Standard 5-field cron in UTC.
- Minimum interval is 1 hour. The minute field must be a single literal value (e.g. `0` or `30`). Reject patterns like `*/30 * * * *` or comma-lists like `0,30 * * * *` (under 1h gap).
- Hour field may use lists or ranges; that's fine since gaps are at least 1h.
### 4. run_once_at rules
Must be a future RFC3339 UTC timestamp like `2027-01-01T00:00:00Z`. Past timestamps are a warning (the API still accepts them; they fire immediately).
### 5. enabled
Must be a bool if present. Default `true`.
### 6. model
If set, must be one of: `claude-opus-4-7`, `claude-opus-4-7[1m]`, `claude-sonnet-4-6`, `claude-haiku-4-5`. Anything else is an error.
### 7. allowed_tools
Must be a list of strings. Warn if empty (inherits nothing). Warn loudly if it contains every default write-tool (`Bash`, `Write`, `Edit`, `NotebookEdit` all present): that's the silent-expansion default-set; suggest an explicit trim.
### 8. sources
If present, must be a list of objects with `url` (string starting `https://github.com/`) and optional `allow_unrestricted_git_push` (bool).
### 9. mcp_connections
If present, must be a list of objects with `connector_uuid` (lowercase v4 UUID), `name`, `url`, and optional `permitted_tools`.
### 10. Snippet includes (optional feature)
If the prompt body contains `{{include <path>}}` lines: the file at `<path>` must exist relative to the routine file's directory or the workspace root. Included files must NOT themselves contain `{{include}}` directives (no nesting).
### 11. Prompt body
Must be non-empty after stripping whitespace.
## Output format
```
OK personal/morning-brain-digest.md
ERR personal/oslo-apartment-hunter.md
- error: cron "*/30 * * * *" violates minimum 1-hour interval
- warning: allowed_tools includes Bash, Write, Edit, NotebookEdit (full default-set). Consider trimming.
```
When called without a file argument, validate every `.md` file under common routine locations (`routines/`, `personal/`, or anywhere with frontmatter). Skip READMEs. Print a one-line summary per file.
Final line: `N files OK | M files with errors | W warnings`.
## See also
- `dry-run deploy <file>` to preview the API payload after validation passes
- `deploy <file>` to actually ship
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · hamzafer/claude-routines | 100 | MIT |
| DiogoHSM/driver | 100 | MIT |
| boshu2/agentops | 100 | Apache-2.0 |
| RemiPelloux/kill-my-idea | 100 | MIT |
| lalitmaganti/syntaqlite | 100 | Apache-2.0 |
| zanderadam/engy | 100 | MIT |
| hirogakatageri/hirokata-claude-marketplace | 100 | MIT |
| fabricio21x/fbs | 100 | MIT |
| Kiran-980/1ml | 100 | MIT |
Database snapshot: 13.11.2026 · package version ca7951eb0d85 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100validate-cc-md
Validates CLAUDE.md files for size, imports, and structure. Use when user asks to "check my CLAUDE.md", "why is my CLAUDE.md too long", "validate imports", or "fix CLAUDE.md errors". Checks file size limits (30KB warning, 50KB error), @import directives, frontmatter in… - 100create
Create a new Claude Code routine from a local .md file. Invoke when the user says "create <file>" or when called as a sub-skill of deploy. The file's frontmatter must NOT contain a trigger_id. - 100lint-skills
Use when running the package's skill linter against all skills and rules to validate frontmatter, required sections, and execution metadata. - 90creating-claude-agents
Use when creating or improving Claude Code agents. Expert guidance on agent file structure, frontmatter, persona definition, tool access, model selection, and validation against schema. - 100curator
Use when ingesting memory into the wiki, running wiki_curator.py (run/report/validate/lint/search), or linting wiki structure. - 100validate-plugin
Validate a Claude Code plugin directory against the official Anthropic spec and Intent Solutions enterprise standard. Runs structural validation (plugin.json fields, file references, permissions) and content validation (SKILL.md grading, command/agent frontmatter). Use when…