codex-wrapped
Codex Wrapped
Use this skill whenever the user wants a Codex Wrapped report or usage insights. Render text-only output (no image generation).
The report must be year-agnostic and should highlight last 30 days and last 7 days, while still calling out all-time focus hours.
Quick Commands (run in order)
- Compute stats
python3 .codex/skills/codex-wrapped/scripts/get_codex_stats.py \
--output /tmp/wrapped_stats.json
(Defaults to the system timezone; override --timezone only if the user requests it.)
- Render text report
.codex/skills/codex-wrapped/scripts/report.sh \
--stats-file /tmp/wrapped_stats.json
This prints the report directly to stdout.
Files
scripts/get_codex_stats.py-- computes rolling-window stats to/tmp/wrapped_stats.json.scripts/report.sh-- text report renderer.
Responding to the user
- Paste the report text exactly as printed, wrapped in triple backticks (```), to preserve spacing/box drawing.
- If something fails, state what you ran and the error.
Notes
- Keep
/tmp/wrapped_stats.jsonunless sensitive; rerun stats if outdated. - The report adapts to terminal width. Set
WRAPPED_WIDTH=120(or similar) to force a wider layout. - Layout options: default is
columns(two-column). Use--layout table(orWRAPPED_LAYOUT=table) to switch back to the compact grid.
More from aleister1102/skills
codeql
>-
26brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
24prompt-optimizer
Transform vague prompts into precise, well-structured specifications using EARS (Easy Approach to Requirements Syntax) methodology. This skill should be used when users provide loose requirements, ambiguous feature descriptions, or need to enhance prompts for AI-generated code, products, or documents. Triggers include requests to "optimize my prompt", "improve this requirement", "make this more specific", or when raw requirements lack detail and structure.
24update-docs
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
22docs-cleaner
Dedupe and consolidate redundant docs (multiple sources of truth, overlapping guides, or docs over 500 lines). Use when merging/splitting to a canonical doc. Do not use for typo-only edits, code-driven doc updates (run update-docs first), or when archives must be preserved without change.
20gh-address-comments
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
20