daily-cost
openbooklet.com/s/daily-costopenbooklet.com/s/daily-cost@1.0.0GET /api/v1/skills/daily-costUse when the user asks about cost, spending, or budget â e.g. 'how much did I spend today', 'daily cost', 'cost report', 'what's my spend'
Use when the user asks about improving their Claude Code usage, coaching rules, or best practices â e.g. 'how can I improve', 'coaching tips', 'my coaching rules', 'add a coaching rule'
Use when the user wants to export session data â e.g. 'export my sessions', 'download data', 'export to CSV', 'get my data'
Use when the user asks about patterns, insights, or behavioral analysis â e.g. 'what patterns do you see', 'insights', 'how am I doing', 'behavioral analysis'
Use when the user asks about running sessions, agent status, what needs attention â e.g. 'what's running', 'live status', 'which sessions need me', 'agent status', 'check on my agents', 'are my sessions done', 'anything stuck'
Use when the user asks to recap, summarize, or review a Claude Code session â e.g. 'recap my last session', 'what happened in that session', 'session summary'
Use when the user asks about team activity, team status, or what the team is doing â e.g. 'team status', 'what's the team doing', 'team activity', 'who's active'
Use when the user asks about usage analytics, statistics, token usage, or cost summary â e.g. 'usage stats', 'token usage', 'how many sessions this week', 'show me my numbers', 'cost summary', 'usage report'
Auto-indexed from tombelieber/claude-view
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.