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?'
Profile →npx skills add opensquilla/opensquilla --skill history-explorer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# History Explorer Lightweight read-only view over `~/.opensquilla/logs/decisions-*.jsonl`. Aggregates `DecisionEntry.skills_invoked` (SCHEMA_VERSION 10) into co-occurrence frequencies, joins with `SkillLoader.list_meta_specs()` for meta-skill usage stats, and surfaces the `tests/test_skills/router_fixtures/` corpus. ## Usage ``` uv run python {baseDir}/scripts/explore.py \ --log-dir ~/.opensquilla/logs \ --query "Co-occurring chains for PDF workflows" \ --window-days 30 \ --include co_occurrences,meta_usage,router_fixtures \ --top-k 10 ``` ## Output JSON to stdout with keys `co_occurrences`, `meta_usage`, `router_fixtures`, and a `placeholder` string when the log is empty. ## Fallback If no decision-log exists, return an empty result with a placeholder string explaining "no history; downstream should rely on user intent only".
- Usage
- Output
- Fallback
What does the history-explorer skill do?
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?'
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill history-explorer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.