CtrlK
BlogDocsLog inGet started
Tessl Logo

health

Run condition-based vault health diagnostics. 8 categories — schema compliance, orphan detection, link health, description quality, three-space boundaries, processing throughput, stale notes, MOC coherence. 3 modes — quick (schema+orphans+links), full (all 8), three-space (boundary violations only). Returns actionable FAIL/WARN/PASS report with specific fixes ranked by impact. Triggers on "/health", "check vault health", "maintenance report", "what needs fixing".

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A thorough, highly actionable diagnostic skill with executable code and clear sequencing. Its weakness is monolithic structure and mild verbosity — the eight category specs could be split into reference files and the editorial rationale trimmed.

Suggestions

Move the 8 detailed diagnostic-category specs (detection code, thresholds, output formats) into references/ files and keep SKILL.md as an overview with one-level-deep, clearly signaled links.

Trim editorial rationale such as 'Dangling links are broken promises... erodes trust in the graph' and the repeated per-category Output Format blocks (already covered by the master Output Format section).

Consolidate the duplicated threshold tables where a single table per category suffices to reduce token overhead.

DimensionReasoningScore

Conciseness

Dense with concrete, useful detail, but ~750 lines include editorial prose (e.g. 'Dangling links are broken promises... erodes trust in the graph') and per-category output blocks duplicated against a master Output Format section that could be tightened.

2 / 3

Actionability

Each of the 8 categories ships executable bash detection code, explicit threshold tables, and concrete output-format examples — copy-paste ready guidance throughout.

3 / 3

Workflow Clarity

Clear numbered sequence (detect mode → scan → run categories 1-8 → classify PASS/WARN/FAIL → surface signals → generate report → write file) with threshold/checklist checkpoints and a dedicated Edge Cases section.

3 / 3

Progressive Disclosure

Well-organized into sections, but the body is a monolithic ~750-line file with no bundle reference files; the detailed per-category specs and detection code that could be offloaded to references/ are all inline.

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.

A strong, specific description: third-person voice, concrete capabilities, explicit when-to-use triggers, and a distinct niche. It does lean long by enumerating all 8 categories, but every term earns its place.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across 8 named categories, 3 modes, and a specific FAIL/WARN/PASS report output — far beyond vague language.

3 / 3

Completeness

Clearly answers both what (condition-based vault diagnostics across 8 categories/3 modes returning a ranked report) and when (explicit 'Triggers on...' clause).

3 / 3

Trigger Term Quality

Explicit triggers ("/health", "check vault health", "maintenance report", "what needs fixing") are natural phrasings a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (vault health diagnostics) with distinct triggers unlikely to collide with other skills.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (761 lines); consider splitting into references/ and linking

Warning

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

13

/

16

Passed

Repository
agenticnotetaking/arscontexta
Reviewed

Table of Contents

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.