How do I install the Ccusage Docs skill?

Run npx skillmds@latest add tuyv/ccusage-docs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ccusage Docs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ccusage Docs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ccusage Docs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ccusage Docs?

tuyv (@tuyv) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ccusage Docs by tuyv — Agent Skill

Name: Ccusage Docs
Author: tuyv

File contents

ccusage Docs

The docs package is a VitePress site under docs/.

Commands

pnpm --filter docs dev
pnpm --filter docs build
pnpm --filter docs preview
pnpm --filter docs format
pnpm --filter docs typecheck

The docs build copies apps/ccusage/config-schema.json to docs/public/config-schema.json before running VitePress.

Structure

README.md and apps/ccusage/README.md - package entrypoints for supported sources, common commands, features, and installation examples
docs/guide/ - user guides and tutorials
docs/public/ - screenshots, static assets, and generated config schema
docs/.vitepress/ - VitePress configuration and theme customization

Content Rules

When adding or changing a user-facing agent, command, option, report mode, or example, audit and update the root README.md, apps/ccusage/README.md, relevant docs/guide/ pages, related cross-links, and VitePress navigation before finishing.
Prefer the unified command form in new or edited docs: ccusage codex ..., ccusage opencode ..., ccusage amp ..., and ccusage pi ....
Standalone wrapper commands such as ccusage-codex, ccusage-opencode, ccusage-amp, and ccusage-pi have been removed. Do not promote or reintroduce them in docs.
Place screenshots immediately after the page H1 when a guide has a primary screenshot.
Use relative image paths such as /screenshot.png for files in docs/public/.
Always include descriptive alt text for screenshots and images.
Lead with visual context when a guide has an established screenshot pattern.
Cross-link related guides and JSON output documentation where useful.
For markdown code blocks that ESLint should skip, put  before the block.

Known screenshot-led guides include:

docs/guide/index.md
docs/guide/daily-reports.md
docs/guide/live-monitoring.md

---name: ccusage-docsdescription: Guides ccusage VitePress documentation work. Use when editing docs, screenshots, accessibility, schema-copy behavior, markdown linting, or user-facing guides.---# ccusage DocsThe docs package is a VitePress site under `docs/`.## Commands```shpnpm --filter docs devpnpm --filter docs buildpnpm --filter docs previewpnpm --filter docs formatpnpm --filter docs typecheck```The docs build copies `apps/ccusage/config-schema.json` to `docs/public/config-schema.json` before running VitePress.## Structure- `README.md` and `apps/ccusage/README.md` - package entrypoints for supported sources, common commands, features, and installation examples- `docs/guide/` - user guides and tutorials- `docs/public/` - screenshots, static assets, and generated config schema- `docs/.vitepress/` - VitePress configuration and theme customization## Content Rules- When adding or changing a user-facing agent, command, option, report mode, or example, audit and update the root `README.md`, `apps/ccusage/README.md`, relevant `docs/guide/` pages, related cross-links, and VitePress navigation before finishing.- Prefer the unified command form in new or edited docs: `ccusage codex ...`, `ccusage opencode ...`, `ccusage amp ...`, and `ccusage pi ...`.- Standalone wrapper commands such as `ccusage-codex`, `ccusage-opencode`, `ccusage-amp`, and `ccusage-pi` have been removed. Do not promote or reintroduce them in docs.- Place screenshots immediately after the page H1 when a guide has a primary screenshot.- Use relative image paths such as `/screenshot.png` for files in `docs/public/`.- Always include descriptive alt text for screenshots and images.- Lead with visual context when a guide has an established screenshot pattern.- Cross-link related guides and JSON output documentation where useful.- For markdown code blocks that ESLint should skip, put `` before the block.Known screenshot-led guides include:- `docs/guide/index.md`- `docs/guide/daily-reports.md`- `docs/guide/live-monitoring.md`

Frequently asked questions

Ccusage Docs