Skip to content
Skills Library
Data & analytics · Conversion & formats

prepare-usage-export

/prepare-usage-export

Shape a raw usage export into the CSV the adoption scorecard reads, without personal data. Use when the user has admin analytics or usage data that is not yet in the scorecard's column layout.

Licence
MIT
Last repository change
07.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Shape a raw usage export into the CSV the adoption scorecard reads, without personal data. Use when the user has admin analytics or usage data that is not yet in the scorecard's column layout.

Original author description

Shape a raw usage export into the CSV the adoption scorecard reads, without personal data. Use when the user has admin analytics or usage data that is not yet in the scorecard's column layout.

How it works

  1. Trigger
  2. Workflow
  3. Rules
  4. Output
Original SKILL.md headings · 35 lines, 264 words
SKILL.md preview
---
name: prepare-usage-export
description: Shape a raw usage export into the CSV the adoption scorecard reads, without personal data. Use when the user has admin analytics or usage data that is not yet in the scorecard's column layout.
---

# Prepare a usage export

## Trigger

The user has raw usage data and needs the scorecard's CSV layout, or the scorecard rejected rows.

## Workflow

1. Ask where the data comes from. What an admin export contains depends on the plan and product, so verify against current Cursor docs. Do not assume a column exists.
2. Map the source fields to the scorecard columns: `user_id`, `team`, `licensed_date`, `last_active_date`, `active_days_last_28`, `agent_sessions_last_28`, `accepted_suggestions_last_28`, and optionally `active_weeks_last_4`.
3. Remove names and emails. Replace them with a stable id such as `u001`. Keep the mapping file out of the repo and out of the report.
4. Check each row:
   - dates are `YYYY-MM-DD`
   - counts are whole numbers, never negative
   - `active_days_last_28` is 0 to 28
   - `active_weeks_last_4` is 0 to 4 if present
   - `last_active_date` is not before `licensed_date`
   - no duplicate ids
5. Write the CSV. List every row you changed or dropped, with the reason.

## Rules

- Never invent a value. An empty `last_active_date` is allowed and means the person never used the tool. Any other missing value means the row is dropped and listed.
- If a column is not in the source, say so. Do not estimate it.
- Do not combine teams to hide small groups. Tell the user that small teams are noisy.
- Do not write personal data into any file in the repository.

## Output

1. The CSV path.
2. The number of rows kept and dropped.
3. The reasons for any dropped rows.
4. Any column that is missing from the source, and what that limits.

Versions

The database has no other skills named prepare-usage-export.

Database snapshot: 13.11.2026 · package version bd8f2b1d2397 (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

  • 100read-adoption-report
    Run the adoption scorecard on a per-user usage CSV and explain the result without overclaiming. Use when the user has an AI coding tool usage export, or a scorecard report, to interpret.
  • 100scenario-admin-analytics
    Use when answering Scenario admin analytics questions about Creative Unit consumption, most-used models, usage by user or project, AI adoption observability, cached usage data, CSV exports, enterprise PDF reports with charts, or a local analytics dashboard. Keywords: usage API,…
  • 100export-data
    Use when the user wants to export session data — e.g. 'export my sessions', 'download data', 'export to CSV', 'get my data
  • 100csv-manual-export
    CSV Manual Export: a UTF-8 CSV template from a confirmed field list, empty by default, with no invented columns or values. Use for an import, staging or handoff file.
  • 100csv-manual-export
    CSV Manual Export: a UTF-8 CSV template from a confirmed field list, empty by default, with no invented columns or values. Use for an import, staging or handoff file.
  • 100cursor-usage-analytics
    Track and analyze Cursor usage metrics. Triggers on "cursor analytics", "cursor usage", "cursor metrics", "cursor reporting", "cursor dashboard". Use when working with cursor usage analytics functionality. Trigger with phrases like "cursor usage analytics", "cursor analytics", "cursor".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.