skills.rest
GoogleDevRelExplorations
GoogleDevRelExplorationsOFFICIAL
Explore all skills by this author →
GitHub

cercano-submit-usage

Submit cloud token usage data to Cercano with input and output token counts.

Updated Mar 20, 2026
Search Tags:#metrics#telemetry#token#submit#cloud-usage#local-vs-cloud
One-click install
npx skills add https://github.com/GoogleDevRelExplorations/cercano --skill cercano-submit-usage-googledevrelexplorations
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cercano-submit-usage
Source: https://github.com/GoogleDevRelExplorations/cercano/tree/main/.agents/skills/cercano-submit-usage
Command: npx skills add https://github.com/GoogleDevRelExplorations/cercano --skill cercano-submit-usage-googledevrelexplorations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool allows opt-in submission of cloud token usage to Cercano to enable accurate local-vs-cloud usage analysis and comparison.

Core Features & Use Cases

  • Manual or programmatic submission of cloud usage metrics via the cercano_submit_usage tool.
  • Supports cloud_input_tokens and cloud_output_tokens with optional cloud_provider and cloud_model for richer context.
  • PostToolUse hook can automate submissions in common setups; use manually when needed for custom telemetry workflows.

Quick Start

Submit cloud usage data by calling cercano_submit_usage with cloud_input_tokens, cloud_output_tokens, and optional cloud_provider and cloud_model.

Frequently Asked Questions about cercano-submit-usage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit cloud token usage data for local-vs-cloud analysis?▼

To submit cloud token usage data for local-vs-cloud analysis, call the cercano_submit_usage tool with mandatory cloud_input_tokens and cloud_output_tokens, and optionally include cloud_provider and cloud_model for richer context.

What fields are required when reporting cloud input and output tokens?▼

When reporting cloud input and output tokens, the mandatory fields are cloud_input_tokens and cloud_output_tokens, while cloud_provider and cloud_model are optional fields for adding provider and model context.

Can I automate cloud usage telemetry submission in my workflow?▼

You can automate cloud usage telemetry submission by using the PostToolUse hook for common setups, or call cercano_submit_usage manually to support custom telemetry workflows.

Does cloud usage submission support tracking multiple cloud providers and models?▼

Cloud usage submission supports tracking multiple cloud providers and models by accepting the optional cloud_provider and cloud_model fields to provide richer context for local-vs-cloud comparison.

When should I manually submit cloud usage metrics instead of using automation?▼

You should manually submit cloud usage metrics when you have custom telemetry workflows that fall outside the scope of standard PostToolUse hook automation setups.

Related Skills

Explore More Software Engineering Skills→
chambear2809chambear2809
36

splunk-github-ta-setup

Render Splunk Add-on for GitHub inputs and validation guidance.

Community
Advanced
bryancostanichbryancostanich
8

cercano-submit-usage

Submit cloud token usage data to Cercano for telemetry analytics.

Community
Basic
microsoftmicrosoft
242

azure-observability

Automate Azure observability workflows for monitoring and diagnosing cloud workloads.

Official
Advanced
kmshihab7878kmshihab7878
6

cost-optimization

Analyze cloud and AI consumption costs across Terraform, AWS, and Claude Code usage.

Community
Intermediate