CtrlK
BlogDocsLog inGet started
Tessl Logo

vault-audit

Full 7-phase vault audit: structural scan, duplicate detection, link integrity, frontmatter audit, MOC review, cross-agent integration check, and health report. Triggers: EN: "weekly review", "check the vault", "vault audit", "full audit", "vault health". IT: "revisione settimanale", "controlla il vault", "audit del vault", "salute del vault". FR: "audit du vault", "vérifier le vault". ES: "auditoría del vault", "revisar el vault". DE: "Vault-Audit", "Vault überprüfen". PT: "auditoria do vault", "verificar o vault".

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

A comprehensive, highly actionable 7-phase audit workflow with concrete paths, thresholds, and templates. It is somewhat verbose with minor redundancy and lacks an explicit verify-after-fix feedback loop, and it keeps all detail inline rather than progressive-disclosing it via bundle files.

Suggestions

Add an explicit verify-after-fix step (e.g., re-run the link-integrity and duplicate checks after applying fixes) to close the validate→fix→retry loop for batch and destructive operations.

Move the full health-report template and per-phase detail into reference files (e.g., references/report-template.md, references/phases.md) so SKILL.md reads as an overview.

Deduplicate the legacy agent-messages cleanup instruction, which currently appears in both 'Inter-Agent Coordination' and 'Phase 6: Cross-Agent Integration'.

DimensionReasoningScore

Conciseness

It avoids explaining concepts Claude already knows (no definitions of wikilinks/MOCs/frontmatter), but at ~320 lines it includes minor redundancy (legacy agent-messages cleanup is stated twice) and a verbose report template that could be tightened — 'mostly efficient but could be tightened.'

2 / 3

Actionability

Concrete file paths ('Meta/vault-map.md', '{{meta}}/user-profile.md'), specific thresholds ('>70% content overlap'), exact filename variants ('Note (updated).md', 'Note (conflict).md'), and copy-ready report/fix templates give fully executable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

A clear 7-phase sequence with user-confirmation checkpoints ('Ask the user for confirmation before merging or deleting', 'Apply all / Let me review each / Skip'), but no explicit post-fix verification/re-run step for batch and destructive operations, which caps clarity at 2 per the rubric's feedback-loop guideline.

2 / 3

Progressive Disclosure

Well-organized single file with clearly signaled one-level references ('.platform/references/agent-orchestration.md', '.platform/references/agents-registry.md'), but the full workflow and the large health-report template are inline with no bundle files to split detail into — 'content that should be separate is inline.'

2 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 description: concrete multi-action capability statement paired with explicit, natural trigger phrases in six languages, all in third person. It clearly answers both what the skill does and when to use it with low conflict risk.

DimensionReasoningScore

Specificity

Lists seven concrete actions verbatim — 'structural scan, duplicate detection, link integrity, frontmatter audit, MOC review, cross-agent integration check, and health report' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ('Full 7-phase vault audit' with the named phases) and when (an explicit 'Triggers:' clause with concrete phrases), matching the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Natural user phrases across six languages ('weekly review', 'check the vault', 'vault audit', 'vault health' plus IT/FR/ES/DE/PT equivalents) give good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

A clear niche (Obsidian vault auditing) with vault-specific triggers makes it unlikely to fire for unrelated skills; the one generic phrase ('weekly review') is paired with vault context.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
gnekt/My-Brain-Is-Full-Crew
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.