validate

Schema validation for notes. Checks against domain-specific templates. Validates required fields, enum values, description quality, and link health. Non-blocking — warns but doesn't prevent capture. Triggers on "/validate", "/validate [note]", "check schema", "validate note", "validate all".

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear, checkpointed workflow, but it is long and monolithic with some redundancy. Splitting the example output formats and handoff templates into reference files would improve both conciseness and progressive disclosure.

Suggestions

Move the single-note output format, handoff block, and task-file update templates into a separate reference file (e.g. references/output-formats.md) and link to them, reducing inline length and removing the duplicated severity-level explanation.

De-duplicate the severity-level material: keep one canonical Severity Levels table and reference it from the batch-mode section instead of restating PASS/WARN/FAIL meaning inline.

Tighten the 'How to check adds new info' block — the mechanism/scope/implication/context list is useful but could be condensed to one line per item to trim tokens.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tables of concrete checks, but ~300 lines with redundancy (severity levels explained both inline in the batch report and again in the Severity Levels section; output-format examples repeated) that could be tightened.	2 / 3
Actionability	Every check pairs a concrete Rule with a 'How to Verify' step using specific field names and patterns (e.g. 'Extract all [[...]] patterns from body'), giving copy-paste-ready guidance for an instruction-only skill.	3 / 3
Workflow Clarity	Clear sequence (Step 0 config → locate template → read note → run checks) with PASS/WARN/FAIL checkpoints and an explicit re-validation feedback loop after FAIL fixes.	3 / 3
Progressive Disclosure	Well-organized into clear sections but it is a single monolithic file over 50 lines with no bundle split; the verbose output-format and handoff templates could live in separate reference files.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is third-person, specific, and complete, covering concrete actions plus explicit natural-language triggers. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Validates required fields, enum values, description quality, and link health' — naming several specific capabilities rather than vague language.	3 / 3
Completeness	Clearly states both what it does ('Schema validation for notes... validates required fields...') and when to use it ('Triggers on "/validate", ...'), satisfying the 'what AND when' anchor.	3 / 3
Trigger Term Quality	Explicit natural triggers users would say — 'validate note', 'check schema', 'validate all', plus the /validate slash form — giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	A clear niche (schema validation of notes against domain templates) with distinct, specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: agenticnotetaking/arscontexta
Path: skill-sources/validate/SKILL.md
Commit: 2acfd5c

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.