Compute Claude Code token usage by model for any date range from local session transcripts. Use this whenever the user asks how many tokens they used, their Claude Code / Claude subscription usage, usage for a month or week or day, a "usage report", per-model token breakdown, or "how much did I spend/use" over some period — including phrasings like "first week of June", "last 7 days", "June 2026", or "yesterday". This is the right tool on the subscription plan, where console.anthropic.com does NOT show usage. Trigger even when the user just names a period and the word "usage" without saying "tokens".
WalkInto.in virtual tour platform and helpdesk — authenticate, view profile, manage 360 tours, search the knowledge base, and run the support ticket lifecycle. Use this skill whenever the user mentions 'walkinto', a WalkInto account, virtual/360 tours, panorama uploads, tour analytics, OR the WalkInto helpdesk: support tickets, customer questions, knowledge-base/KB articles, replying to or triaging tickets, ticket status/priority/tags, or 'who am I on walkinto'.
Evaluate whether the lean-ctx MCP is saving more context tokens than it costs, for the current project, using that project's Claude Code session transcripts. Measures ctx_read with a per-call counterfactual vs native Read, compares ctx_shell against native Bash observationally, nets out the per-session instruction+schema tax, and reports a token ledger. Use when asked to eval lean-ctx, measure context-compression savings, audit token usage of an MCP, or decide if lean-ctx earns its seat.
Inspect a project and recommend developer tooling (LSP, AST, test runners, debuggers, linters) that would make Claude Code most effective. Provides exact install commands and a verify mode to confirm each tool works.
In-browser annotation overlay for HTML, Markdown, and plain-text documents. Use when a user wants to annotate a document, run a structured review pass with severities (typo / edit / rewrite), or apply review comments back into source files via Claude Code.
Use when a model emits multiple tool calls in a single turn and the harness must execute them in parallel safely, or when subagents/forks run concurrently and share state. Apply when designing the concurrency model for tool dispatch. Covers parallel tool execution, ordering guarantees, cancellation propagation, race detection on shared resources (filesystem, db), partial-failure semantics, and result aggregation.
Use when an agent harness needs user- or admin-configurable interception points — before/after tool calls, on prompt submit, on stop, on session start. Apply when designing the event/hook architecture that lets operators inject policy, logging, or transformation without modifying core harness code. Covers event taxonomy, blocking vs non-blocking hooks, hook contract (stdin/stdout/exit-code), failure modes, and security implications.
Use when an agent's conversation or working memory grows past the model's context window, or when long sessions accumulate stale tool output, repeated reads, and verbose traces that crowd out signal. Apply when designing how a harness summarizes, prunes, tiers (hot/warm/cold), or evicts history without losing load-bearing facts. Covers compaction triggers, summarization strategies, lossy vs lossless tradeoffs, and recovery from over-compaction.