history-explorer

Query the per-turn DecisionEntry log for skill co-occurrence patterns, meta-skill usage stats, and the router fixture corpus. Returns a JSON summary suitable for downstream LLM consumption. Used by meta-skill-creator's harvest step but also useful standalone for 'which skills did I use most this week?'

Quality

81%

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

100%Weight 40%Scale 1-5

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

The body is an exemplary lean skill: a single executable command, clear output contract, and an explicit fallback, with no padding and well-organized sections suited to a simple single-purpose tool.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — Overview, a single executable command, output keys, and a fallback — with no explanation of concepts Claude already knows, matching the anchor 5 'every token earns its place'.	5 / 5
Actionability	The Usage block gives a copy-paste ready 'uv run python {baseDir}/scripts/explore.py' command with concrete flags and example values, matching the anchor 5 for fully executable guidance.	5 / 5
Workflow Clarity	This is a simple single-action read-only skill, and the action is unambiguous with a clearly specified Fallback path for the empty-log case, so it qualifies for the simple-skill exception to score 5.	5 / 5
Progressive Disclosure	Under 50 lines, well-organized into four labeled sections, and the only referenced artifact (scripts/explore.py) is a real one-level-deep bundle file, matching the simple-skill allowance for scoring 5 with well-organized sections.	5 / 5
	Total	20 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 specific and occupies a distinct niche, but it leans on internal terminology and phrases its trigger guidance as a use-case rather than an explicit 'Use when…' clause, which limits completeness and natural keyword coverage.

Suggestions

Add an explicit 'Use when…' clause with natural trigger phrases (e.g., 'Use when you want to analyze which skills you used most, find skill co-occurrences, or inspect router fixture decisions').

Surface the common user-facing synonyms alongside internal terms — e.g., 'skill usage history', 'most-used skills', 'skill stats' — so natural queries trigger the skill.

Lead with the user-facing capability before naming the internal DecisionEntry/SCHEMA_VERSION machinery, keeping the jargon as supporting detail.

Dimension	Reasoning	Score
Specificity	Quotes 'co-occurrence patterns, meta-skill usage stats, and the router fixture corpus' — three concrete capabilities on a named domain (DecisionEntry log), matching the anchor listing several specific actions with minor gaps; not a 5 because coverage of what 'querying' entails is implied rather than exhaustively enumerated.	4 / 5
Completeness	A clear 'what' is present (query log into a JSON summary of three aggregates), but the 'when' is given only as a use-case scenario rather than an explicit 'Use when…' clause, which the guidelines cap at 3.	3 / 5
Trigger Term Quality	The natural phrase 'which skills did I use most this week?' is a genuine user trigger, but the rest is internal jargon (DecisionEntry, router fixture corpus, SCHEMA_VERSION), so keyword coverage is partial with common variations missing — closest to anchor 3.	3 / 5
Distinctiveness Conflict Risk	The skill targets a clear niche (opensquilla DecisionEntry log, meta-skill-creator harvest, router fixtures) with distinct triggers and minimal overlap risk with unrelated skills, matching the anchor 5 example.	5 / 5
	Total	15 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/bundled/history-explorer/SKILL.md
Commit: 94ac35e

Reviewed: 4 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.