segment-usage
/segment-usage
Report Segment Monthly Tracked Users (MTU) and API call usage for a month, for the whole workspace and per source, with the top contributors. Use when the user asks about Segment MTUs, usage, billing drivers, or which sources send the most.
- Author
- csangani ↗
- Repository
- segment-cli ↗
- Licence
- MIT
- Last repository change
- 06.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Report Segment Monthly Tracked Users (MTU) and API call usage for a month, for the whole workspace and per source, with the top contributors. Use when the user asks about Segment MTUs, usage, billing drivers, or which sources send the most.
Original author description
Report Segment Monthly Tracked Users (MTU) and API call usage for a month, for the whole workspace and per source, with the top contributors. Use when the user asks about Segment MTUs, usage, billing drivers, or which sources send the most.
How it works
- Period
- Collect
- Report
SKILL.md preview
--- name: segment-usage description: Report Segment Monthly Tracked Users (MTU) and API call usage for a month, for the whole workspace and per source, with the top contributors. Use when the user asks about Segment MTUs, usage, billing drivers, or which sources send the most. license: MIT compatibility: Requires the segment CLI (npm install -g csangani/segment-cli), logged in. See the segment-setup skill. allowed-tools: Bash(segment read *) Bash(segment describe *) Bash(segment auth status) Bash(segment auth status *) --- # Segment usage report Read-only. Report MTU and API call usage for one usage month with the `segment` CLI. If the user names a workspace profile, add `--profile NAME` to every command. ## Period The API's `period` parameter is the first day of the usage month, for example `2026-11-01`. Use the month the user asked about (`2026-10`, `October 2026`, `last month`). Otherwise use the current month. If the workspace's billing cycle doesn't start on the 1st and the API rejects or returns nothing for the period, say so and ask for the cycle start date. ## Collect Run these with your shell tool (they can run in parallel). Replace `P` with the period: ``` segment read getDailyWorkspaceMTUUsage period=P --all segment read getDailyPerSourceMTUUsage period=P --all segment read getDailyWorkspaceAPICallsUsage period=P --all segment read getDailyPerSourceAPICallsUsage period=P --all segment read listSources --all --fields id,name,slug ``` Count values (`identified`, `anonymous`, `anonymousIdentified`, `neverIdentified`, `apiCalls`) are bigint strings, so convert them before adding. The API describes these rows as daily cumulative counts, so the latest `timestamp` is the month-to-date figure; don't add daily rows together. Per-source responses can be large. If one is saved to a file, process it with a short `node -e` script rather than reading it all. ## Report 1. **Workspace totals:** month-to-date MTU (identified + anonymous, with the breakdown) and API calls, as of the latest snapshot timestamp. 2. **Trend:** how the cumulative figures grew over the month. Weekly checkpoints are enough. 3. **Top sources:** top 10 by MTU and top 10 by API calls, by name, with each source's share of the total. 4. **Notable:** sources with high anonymous-to-identified ratios, sources with API calls but near-zero MTU, and sudden jumps between snapshots. Note that these figures come from the Public API's usage endpoints, and that the Segment app's billing page is authoritative for invoicing.
Versions
The database has no other skills named segment-usage.
Database snapshot: 13.11.2026 · package version 3367aa911d6a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100segment-api
Read or change a Twilio Segment workspace through the Segment Public API using the `segment` CLI (github.com/csangani/segment-cli). Use when the user mentions Segment, their Segment workspace, sources, destinations, warehouses, write keys, tracking plans or Protocols, Engage… - 100segment-setup
Install the segment CLI (github.com/csangani/segment-cli) if it's missing, guide the user through logging in to their Segment workspace, and verify the token, region, and permissions. Use when `segment` isn't found, is older than 0.3.0, or reports "Not logged in" or a rejected… - 100segment
Skill for working with Twilio Segment as an event-tracking ingestion source. Activates when the user mentions Segment, the Segment Public API, tracking plans, sources, destinations, or event taxonomy in the Segment sense. Uses the Segment Public API directly (no MCP server) — bearer-token REST. - 85segment-cdp
Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance best practices. Use when: segment, analytics.js, customer data platform, cdp, tracking plan. - 90esp32-ble-mtu-throughput-budget
Use when designing, reviewing, debugging or validating ble mtu throughput budget for ESP32 firmware; apply target-specific constraints, failure analysis and measurable verification before release. - 100network-mtu-mss-path-discovery
Use this skill when diagnosing packet fragmentation, Path MTU black holes, and configuring TCP MSS clamping on routers.