Analytics

Skill puukis/lstack/skills/analytics

A personal Claude Code environment. Persistent memory, loop detection, 15 skills, and lifecycle hooks. macOS, Linux, and Windows.

Install

npx -y skills add puukis/lstack --skill analytics

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Show lstack memory analytics, including structured learning health.

SKILL.md

0.8 KB, 142 tokens by cl100k_base, as published. Nobody here has run it

Analytics — memory health

Activation

Use /analytics when the user asks for memory analytics, learning counts, decay status, repeated keys, or scope breakdowns.

Commands

Overall analytics:

lstack analytics

Structured learning stats only:

lstack learn stats

Machine-readable structured stats:

lstack learn stats --json

Report

Include:

learnings by type
learnings by source
decayed learnings below useful threshold
most repeated keys
trusted vs untrusted
top project scopes
legacy observation counts when relevant

Do not infer conclusions beyond what the DB reports.

Gives 0 of the 12 instructions most analytics metrics skills give in 142 tokens

Counted across 368 of the 369 authors here whose files we hold, read 2026-08-06

read product marketing context before asking questionsin 18 of 368, across 12 files
use lowercase with underscores for event namesin 16 of 368, across 6 files
track events for decisions not vanity metricsin 15 of 368, across 5 files
use object-action format for event namesin 15 of 368, across 8 files
produce a tracking plan documentin 14 of 368, across 4 files
Call RUBE_SEARCH_TOOLS first to get current schemasin 13 of 368, across 2 files
establish consistent event naming conventions before implementingin 10 of 368, across 4 files
Verify dimension and metric compatibility before reportingin 9 of 368, across 2 files
Encrypt data at rest and in transitin 9 of 368, across 3 files
use snake_case for event namesin 9 of 368, across 5 files
monitor technical health during the testin 9 of 368, across 5 files
use consistent property namesin 8 of 368, across 4 files

Said here and by no other author read

run lstack analytics for overall analytics
run lstack learn stats for structured learning stats
include learnings by type
include decayed learnings below useful threshold
include most repeated keys
include trusted vs untrusted learnings

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.