stats

Show vault statistics and knowledge graph metrics. Provides a shareable snapshot of vault health, growth, and progress. Triggers on "/stats", "vault stats", "show metrics", "how big is my vault".

Quality

83%

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 complete executable bash and a well-sequenced, edge-case-aware workflow, but it carries a small amount of motivational prose and is monolithic with no progressive disclosure to external reference files despite its length.

Suggestions

Trim the Philosophy section to a single line or remove it; the metrics' value is self-evident to Claude.

Move the detailed Step 1 metric-collection bash blocks and the interpretation-notes table into a references/ file (e.g. METRICS.md), keeping SKILL.md as an overview that points one level deep.

The 'generated_from: arscontexta-v1.6' / 'Generated by Ars Contexta v1.6' version strings are time-sensitive; if they age, consider isolating them in a version/deprecated section to protect conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, executable bash, but the Philosophy section ("Make the invisible visible. The knowledge graph grows silently... Metrics are evidence, not judgment...") explains motivation Claude could infer, matching the score-2 anchor of mostly efficient with some unnecessary explanation; it is not a verbose score-1 wall of concept exposition.	2 / 3
Actionability	Each metric section provides complete, copy-paste-ready bash with real commands (grep, find, bc, date fallbacks) and a fully specified output template, matching the score-3 fully-executable anchor.	3 / 3
Workflow Clarity	Clear sequence (Step 0 config → Step 1 metric collection with parallel sub-steps 1a–1e → Step 2 format → Step 3 share → Step 4 trend) with robust edge-case handling (missing dirs report N/A, platform date fallbacks, large-vault heuristic); the operation is read-only so the destructive/batch validation cap does not apply.	3 / 3
Progressive Disclosure	No bundle files exist (no references/scripts/assets) and the skill is a single ~370-line file with well-organized sections, but content such as the detailed metric-collection scripts and the interpretation-notes table is all inline with no offloading to one-level-deep reference files; the simple-skill exception (under 50 lines) does not apply, matching the score-2 anchor of content that should be separate kept inline.	2 / 3
	Total	10 / 12 Passed

Description

90%

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, concise, and clearly answers both what the skill does and when to use it with natural trigger terms. Its only weakness is that the stated actions are slightly high-level rather than enumerating multiple concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain clearly ("vault statistics and knowledge graph metrics") and two actions ("Show vault statistics", "Provides a shareable snapshot"), but the actions are high-level rather than a list of multiple distinct concrete operations, matching the score-2 anchor "Processes PDF files and extracts content" more than the score-3 multi-action example.	2 / 3
Completeness	Answers both what ("Show vault statistics and knowledge graph metrics. Provides a shareable snapshot of vault health, growth, and progress.") and when ("Triggers on ..."), the latter being an explicit trigger clause equivalent to a 'Use when...' guide, so it is not capped at 2.	3 / 3
Trigger Term Quality	Explicit natural triggers — "Triggers on \"/stats\", \"vault stats\", \"show metrics\", \"how big is my vault\"" — give good coverage of phrasings a user would actually say, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The vault/knowledge-graph niche plus distinctive triggers like "/stats" and "how big is my vault" make it unlikely to fire for the wrong skill, matching the score-3 clear-niche anchor.	3 / 3
	Total	11 / 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/stats/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.