Daily Summary of Claude Code

VerifiedCaution

Generate a daily summary of Claude Code sessions: activities, time spent, and cost.

Sby Skills Guide Bot
ProductivityBeginner
7/23/2026
Claude Code
#daily-summary#usage-tracking#cost-tracking#claude-code#cli

Recommended for

Automated summary

Runs the claude-daily CLI tool to produce a daily report of Claude Code sessions covering activities, time spent, and cost.

Strengths

  • Lets the CLI handle all formatting, so output stays consistent from day to day
  • Accepts an explicit date (YYYY-MM-DD) or falls back to today
  • Handles a missing PATH entry by trying ~/.local/bin/claude-daily directly
  • Explicitly stops after the tool output, avoiding redundant commentary

Limitations

  • Fully dependent on the claude-daily tool being installed and working
  • Only covers Claude Code sessions, not other agents or editors
  • Default language is Portuguese; English requires passing --lang en
When to use it

When you want a quick numeric recap of your Claude Code activity and spend for a given day.

When not to use it

When claude-daily is not installed, or when you need multi-day aggregate analysis or data from sources other than Claude Code.

Security analysis

Caution
Quality score74/100

The skill contains no destructive commands, no network exfiltration, no obfuscation, and no attempts to disable safety. Its only real risk is that it delegates all behavior to an unspecified local CLI that reads session logs, so trust depends on that binary. That fits 'caution' rather than 'risky'.

Findings
  • •Runs an external binary `claude-daily` resolved from PATH (or ~/.local/bin) whose contents are not included, so actual behavior is unverifiable from the skill alone.
  • •The tool reads/reports on local Claude Code session history, which may contain sensitive project data that then gets surfaced into the conversation transcript.
  • •Uses the Bash tool for execution despite no allowed-tools being declared.
How this analysis is made

Examples

Today's report
/daily
Specific date
/daily 2026-03-15
English output
/daily --lang en

name: daily description: Generate a daily summary of Claude Code sessions - activities, time spent, and cost. Use with optional date argument (YYYY-MM-DD). user-invocable: true

Run the claude-daily CLI tool. The tool generates the full formatted report — you just run it and stop.

Instructions

  1. Determine the arguments:

    • If the user provided a date (e.g., /daily 2026-03-15), use that date
    • If no date was provided, use today's date
    • If the user asked for English output (e.g., /daily --lang en), add --lang en
    • Default language is Portuguese (--lang pt)
  2. Run the command using Bash:

    claude-daily [DATE] [--lang pt|en]
    
  3. If claude-daily is not found in PATH, try running it directly:

    ~/.local/bin/claude-daily [DATE] [--lang pt|en]
    
  4. CRITICAL: After the Bash tool returns, you are DONE. Do NOT write ANY text after the tool output. No summary, no commentary, no "here's your report", no "would you like details?", no reformatting. The CLI output IS the response. Say absolutely nothing.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/daily-summary-of-claude-code-mrx3xy5i/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/daily-summary-of-claude-code-mrx3xy5i' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/daily-summary-of-claude-code-mrx3xy5i/download' --output '.skill-downloads/daily-summary-of-claude-code-mrx3xy5i/SKILL.md.part' && mv '.skill-downloads/daily-summary-of-claude-code-mrx3xy5i/SKILL.md.part' '.skill-downloads/daily-summary-of-claude-code-mrx3xy5i/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/daily-summary-of-claude-code-mrx3xy5i/SKILL.md' && test -s '.skill-downloads/daily-summary-of-claude-code-mrx3xy5i/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/daily' && cp -R '.skill-downloads/daily-summary-of-claude-code-mrx3xy5i' '.claude/skills/daily'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/daily-summary-of-claude-code-mrx3xy5i'

openskills read 'daily-summary-of-claude-code-mrx3xy5i'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/daily-summary-of-claude-code-mrx3xy5i/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills