- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/oliver-kriska/claude-elixir-phoenix/tree/HEAD/.claude/skills/session-trendsDe l'éditeur
Analyze trends from the metrics ledger. Computes windowed aggregates, fingerprint distributions, and compares against MEMORY.md baselines.
Requires .claude/session-metrics/metrics.jsonl from /session-scan.
/session-trends # All windows (7d, 30d, all)
/session-trends --window 30d # Specific window only
/session-trends --project enaia # Filter by project
/session-trends --compare MEMORY.md # Compare against memory baseline
/session-trends --html out.html # Write HTML report with ASCII bars
For pure context-window stats (max prompt tokens, ctx %, compaction rate)
across raw Claude Code JSONL files, see the --scan-jsonl mode of
compute-metrics.py (inspired by badlogic / earendil-works/pi).
Extract from $ARGUMENTS:
--window WINDOW: Time window — 7d, 30d, or all (default: show all three)--project NAME: Filter metrics by project name--compare PATH: Path to MEMORY.md for baseline comparison
(default: auto-detect from .claude/ project memory)Read .claude/session-metrics/metrics.jsonl.
If empty or missing:
No metrics found. Run
/session-scanfirst.
If --project specified, filter entries by project field.
python3 .claude/skills/session-scan/references/compute-metrics.py \
--trends .claude/session-metrics/metrics.jsonl \
--memory {MEMORY_PATH}
Capture the JSON output.
Format the JSON output as a readable report:
Total sessions: {N} ({backfilled} backfilled from v1)
Date range: {earliest} to {latest}
| Metric | 7 days | 30 days | All time |
|-------------------------|--------|---------|----------|
| Sessions | 12 | 45 | 165 |
| Avg friction | 0.28 | 0.24 | 0.22 |
| Max friction | 0.72 | 0.72 | 0.89 |
| Avg opportunity | 0.35 | 0.30 | 0.28 |
| Tier 2 eligible | 40% | 33% | 30% |
| Plugin adoption | 12% | 10% | 8% |
| Type | 7d | 30d | All |
|---------------|-----|-----|------|
| bug-fix | 4 | 15 | 52 |
| feature | 3 | 12 | 48 |
| exploration | 2 | 8 | 30 |
| maintenance | 1 | 5 | 18 |
| review | 1 | 3 | 10 |
| refactoring | 1 | 2 | 7 |
Compare measured values against MEMORY.md claims:
| MEMORY.md Claim | Measured | Match? |
|------------------------------|-------------|--------|
| Plugin adoption: 8-12% | 10.2% | Yes |
| Minimal friction in 40+ of 74| 68% smooth | Yes |
Write computed trends to .claude/session-metrics/trends.json.
Based on trends:
/session-deep-dive --from-scan to investigate"See references/trend-queries.md for interpreting specific trend patterns.
The HTML report layout (preformatted text + ASCII bar charts via █/░)
and per-model + threshold-bucket breakdown (>=80%, >=90%, >=100%,
compaction_rate) were borrowed from
badlogic / earendil-works/pi session-context-stats.mjs.
Our pipeline's qualitative metrics (friction, fingerprint, plugin
opportunity, skill effectiveness) are additive on top.
Analyze trends across session metrics. Computes windowed aggregates, deltas, and compares against MEMORY.md findings. Use periodically for progress tracking.
---name: session-trendsdescription: Analyze trends across session metrics. Computes windowed aggregates, deltas, and compares against MEMORY.md…---# .claude/skills/session-trends/SKILL.mdFAQ
Téléchargez .claude/skills/session-trends/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/oliver-kriska/claude-elixir-phoenix.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.