What is segment-analysis?

An analysis tool for customer segments and website conversion data from Noibu. It compares results across channels, devices, countries, and other customer groups.

Finding the strongest traffic channels, comparing mobile with desktop, checking country performance, understanding traffic sources, and identifying underperforming customer segments.

Conversion data can hide important differences between groups, making it hard to see where customers convert well or where performance is weak. This organizes those comparisons and highlights the best and worst-performing segments.

segment-analysis — Skill for Claude Code by Noibu/ai-plugin

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Noibu/ai-plugin --skill segment-analysis

Clone the repo

git clone --depth 1 https://github.com/Noibu/ai-plugin

Made for: Claude Code.

Or install noibu, the plugin that ships this one along with the rest of its 9 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/noibu/ai-plugin/segment-analysis/github.svg)](https://agentmods.dev/skills/noibu/ai-plugin/segment-analysis)

Your own site

<a href="https://agentmods.dev/skills/noibu/ai-plugin/segment-analysis"><img src="https://agentmods.dev/badge/skills/noibu/ai-plugin/segment-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/noibu/ai-plugin/segment-analysis"><img src="https://agentmods.dev/badge/skills/noibu/ai-plugin/segment-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 927 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00061	$0.00927
Opus 5.5	$0.00024	$0.00371
Sonnet 5.5	$0.00012	$0.00185
Haiku 4.5	$0.00006	$0.00093

Measured 1mo ago against content hash 832cd194ca21, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

segment-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/skills/segment-analysis/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Noibu Segment Conversion Analysis

Call metadata: on every noibu_* call this skill drives, pass skill: "segment-analysis" and a short skillStep (see the querying-noibu-data skill).

How it works

Quick answer (focused question) → run 1–2 queries, answer directly, offer to go deeper.
Full analysis (broad request, bare invocation, or "yes" to the offer) → the workflow below.

Setup — before any query

Work quietly. The first thing the user sees is the triage board widget — no "let me…" commentary before it.

Resolve the domain first. Use what the user gave (name or UUID). If nothing, ask via AskUserQuestion — don't ask about anything else. If exactly one domain, skip the question.
Call list_scheduled_tasks now — store whether a task already exists for this domain. This sets the action bar button label at render time ("Edit schedule" vs "Schedule Insights") without blocking queries.
Confirm every field name by role before using it. Reference files name fields by role, never hard-coded column names.
Default window: last 30 days unless the user specifies otherwise.
If the dataset is near-zero (total sessions 0 or a handful), say plainly that the domain has no traffic in this window and offer to widen the range.

Quick answer

For focused questions ("which channel converts best?", "how does mobile compare to desktop?", "which countries are underperforming?"):

Run only the 1–2 queries needed and answer directly.
Offer full analysis via AskUserQuestion (not prose):
- "Yes — survey device, country, and channel, then dig into anomalies"
- "No thanks"

Don't load the triage-board or scheduling references for a quick answer.

Full analysis

Loading reference files: Use the Read tool. All files live in a references/ subdirectory next to this SKILL.md — derive the base path from wherever this file was loaded from.

Read references/queries.md AND references/triage-board.md now, before running any queries.
Run the workflow from queries.md.
Render the overview card, priority cards, and action bar as one show_widget using triage-board.md.

Read the full file on GitHub · 85 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed · +2 lines 832cd194ca21
2mo ago First seen · 83 lines · 61 tokens per session scan A df2f03fcd2c7

Subscribe to this mod's changes

segment-analysis is a skill published in the GitHub repository Noibu/ai-plugin (5 stars, last pushed 13d ago), licensed MIT. It adds 61 tokens to every session and 927 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Analytics and metrics Marketing and SEO

segment-analysis next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
segment-analysisNoibu/ai-plugin	Skill	5	13d ago	MIT	A	61	Claude Code
imagegenopenai/codex	Skill	135k	today	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	316k	8d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code