Agent skill

Session Trends

by oliver-kriska in oliver-kriska/claude-elixir-phoenix

Analyze trends across session metrics. An agent skill from oliver-kriska/claude-elixir-phoenix.

MITAuto-check passed

Install Session Trends

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix session-trends --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/session-trends .claude/skills/session-trends && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "session-trends" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/session-trends into .claude/skills/session-trends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-trends", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/session-trends

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix session-trends --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/session-trends .agents/skills/session-trends && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "session-trends" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/session-trends into .agents/skills/session-trends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-trends", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix session-trends --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/session-trends .cursor/skills/session-trends && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "session-trends" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/session-trends into .cursor/skills/session-trends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-trends", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/oliver-kriska/claude-elixir-phoenix.git --path .claude/skills/session-trends

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix session-trends --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/session-trends .gemini/skills/session-trends && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "session-trends" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/session-trends into .gemini/skills/session-trends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-trends", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix session-trends

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/session-trends .github/skills/session-trends && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "session-trends" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/session-trends into .github/skills/session-trends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-trends", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix session-trends --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/session-trends .opencode/skills/session-trends && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "session-trends" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/.claude/skills/session-trends into .opencode/skills/session-trends/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-trends", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: session-trends
GitHub stars: 565
Token cost: ~1.1k tokens
SKILL.md length: 288 words
Files: 2 (incl. references)
Skills in repo: 109
Repo updated: Oct 5, 2026
First seen: Oct 9, 2026
Licence: MIT

At a glance

Analyze trends across session metrics. An agent skill from oliver-kriska/claude-elixir-phoenix.

Works in 6 steps: Parse Arguments → Read Metrics Ledger → Compute Trends via Python → …
SKILL.md covers Requirements, Usage, Pipeline and Output Files, plus 3 more sections
Calls python3

What it does

Session Trends is an agent skill from oliver-kriska/claude-elixir-phoenix. Analyze trends across session metrics. Computes windowed aggregates, deltas, and compares against MEMORY.md findings. Use periodically for progress tracking.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/trend-queries.md`).

The repository describes itself as: Claude Code plugin for Elixir/Phoenix/LiveView — 26 specialist agents, Iron Laws enforcement, and Tidewave MCP integration. Plan features with parallel research agents, execute… The licence is MIT.

Example prompts

“/session-trends”

Requirements

Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Parse Arguments
Read Metrics Ledger
Compute Trends via Python
Display Trend Report
Write trends.json
Suggest Actions

What it can do on your machine

Read from SKILL.md and the folder at commit 9767a82. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Session Trends loads about 1.1k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 43 tokens; SKILL.md has 288 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~43
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from oliver-kriska/claude-elixir-phoenix at commit 9767a82, republished under its MIT licence (© oliver-kriska). 288 words, ~1,138 tokens.

Download SKILL.mdSave it as .claude/skills/session-trends/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: session-trends
description: Analyze trends across session metrics. Computes windowed aggregates, deltas, and compares against MEMORY.md findings. Use periodically for progress tracking.
argument-hint: [--window 7d|30d|all] [--project NAME] [--compare MEMORY.md]
disable-model-invocation: true

Session Trends

Analyze trends from the metrics ledger. Computes windowed aggregates, fingerprint distributions, and compares against MEMORY.md baselines.

Requirements

Requires .claude/session-metrics/metrics.jsonl from /session-scan.

Usage

/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).

Pipeline

Step 1: Parse Arguments

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)

Step 2: Read Metrics Ledger

Read .claude/session-metrics/metrics.jsonl.

If empty or missing:

No metrics found. Run /session-scan first.

If --project specified, filter entries by project field.

Step 3: Compute Trends via Python

bash

python3 .claude/skills/session-scan/references/compute-metrics.py \
  --trends .claude/session-metrics/metrics.jsonl \
  --memory {MEMORY_PATH}

Capture the JSON output.

Step 4: Display Trend Report

Format the JSON output as a readable report:

Overview

Total sessions: {N} ({backfilled} backfilled from v1)
Date range: {earliest} to {latest}

Window Comparison

| 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%       |

Fingerprint Distribution

| 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    |

MEMORY.md Comparison (if --compare)

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    |

Step 5: Write trends.json

Write computed trends to .claude/session-metrics/trends.json.

Step 6: Suggest Actions

Based on trends:

If friction is increasing: "Friction trending up — run /session-deep-dive --from-scan to investigate"
If plugin adoption is growing: "Plugin adoption growing — check which commands drive value"
If many Tier 2 eligible: "{N} sessions need deep analysis"

Output Files

File	Purpose
`.claude/session-metrics/trends.json`	Computed trend data

Common Queries

See references/trend-queries.md for interpreting specific trend patterns.

Iron Laws

ALWAYS use Python for computation — no manual aggregation
NEVER modify metrics.jsonl — read-only for trends
ALWAYS show window comparison — single numbers lack context

Acknowledgements

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.

Files

SKILL.md and 1 other file (references) in .claude/skills/session-trends of oliver-kriska/claude-elixir-phoenix.

SKILL.md
references/trend-queries.md

Open the folder on GitHubat commit 9767a82

Compare with similar skills

Session Trends next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Session Trends compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Session Trends this skilloliver-kriska/claude-elixir-phoenix	565	—	~1.1k	Automated safety check: Pass	MIT	4 days ago
Aggregating Performance Metricsjeremylongshore/tons-of-skills-marketplace	2.8k	—	~1.2k	Automated safety check: Pass	MIT	today
Ito Computeaffaan-m/ECC	276k	1 repos	~1.7k	Automated safety check: Pass	MIT	today
Observe Metricsruvnet/ruflo	74k	—	~592	Automated safety check: Notes	MIT	today
North Star Metricphuryn/pm-skills	27k	—	~1k	Automated safety check: Pass	MIT	today
Investigate MetricPostHog/posthog	40k	—	~1.9k	Automated safety check: Pass	Custom licence	today

Similar skills

Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
2.8k GitHub stars~1.2k tokensUpdated today
Business, Finance & HRAuto-check passed
Ito Compute
affaan-m/ECC
Query live GPU inventory, submit an authenticated Itô fixed-rate RFQ, inspect RFQ or procurement status, revoke device credentials, and run explicitly gated node qualification through the separately…
276k GitHub starsUsed in 1 repo~1.7k tokens
Business, Finance & HRAuto-check passed
Observe Metrics
ruvnet/ruflo
Aggregate and display system metrics with anomaly detection for a time period
74k GitHub stars~592 tokensUpdated today
Data & AnalyticsAuto-check: notes
North Star Metric
phuryn/pm-skills
Define a North Star Metric and 3-5 supporting input metrics that form a metrics constellation.
27k GitHub stars~1k tokensUpdated today
Product & Project ManagementAuto-check passed
Investigate Metric
PostHog/posthog
Official
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
40k GitHub stars~1.9k tokensUpdated today
Product & Project ManagementAuto-check passed
Windows Desktop E2E
affaan-m/ECC
E2E testing for Windows native desktop apps (WPF, WinForms, Win32/MFC, Qt) using pywinauto and Windows UI Automation.
276k GitHub starsUsed in 1 repo~7.6k tokens
Testing & QAAuto-check passed

Questions about Session Trends

What does Session Trends do?

Analyze trends across session metrics. An agent skill from oliver-kriska/claude-elixir-phoenix. Session Trends is an agent skill from oliver-kriska/claude-elixir-phoenix. Analyze trends across session metrics.

How do I install Session Trends in Claude Code?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a claude-code`. Or copy the skill folder (.claude/skills/session-trends in oliver-kriska/claude-elixir-phoenix) into .claude/skills/session-trends in your project. Claude Code loads it when a task matches its description.

How do I install Session Trends in Codex?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a codex`. Or copy the skill folder (.claude/skills/session-trends in oliver-kriska/claude-elixir-phoenix) into .agents/skills/session-trends in your project. Codex loads it when a task matches its description.

Can I use Session Trends in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add oliver-kriska/claude-elixir-phoenix --skill session-trends -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/session-trends, .gemini/skills/session-trends, .github/skills/session-trends and .opencode/skills/session-trends in your project.

What does Session Trends need to run?

Going by SKILL.md and its folder, Session Trends needs the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Session Trends access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Session Trends safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Session Trends use?

Session Trends is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Session Trends use?

About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Session Trends?

Skills that share tags, products or a category with Session Trends: Aggregating Performance Metrics (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Ito Compute (affaan-m/ECC, 276k stars), Observe Metrics (ruvnet/ruflo, 74k stars) and North Star Metric (phuryn/pm-skills, 27k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Session Trends?

oliver-kriska (a GitHub user) maintains it in oliver-kriska/claude-elixir-phoenix, which has 565 GitHub stars. The repository holds 109 skills in this directory. The repository was last updated on October 5, 2026.

Source: oliver-kriska/claude-elixir-phoenix on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Session Trends

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Session Trends

Requirements

Usage

Pipeline

Step 1: Parse Arguments

Step 2: Read Metrics Ledger

Step 3: Compute Trends via Python

Step 4: Display Trend Report

Overview

Window Comparison

Fingerprint Distribution

MEMORY.md Comparison (if --compare)

Step 5: Write trends.json

Step 6: Suggest Actions

Output Files

Common Queries

Iron Laws

Acknowledgements

Files

Compare with similar skills

Similar skills

More from oliver-kriska/claude-elixir-phoenix

Questions about Session Trends