Retrieve and investigate API metrics and request log data from Apitally. Fetches aggregated metrics, request logs, consumers, and app metadata via the Apitally CLI, stores data in a local DuckDB database, and runs SQL queries to investigate issues or answer questions. Use when the user mentions Apitally, the Apitally CLI, API metrics, API request logs, or API consumers.
93
92%
Does it follow best practices?
Impact
92%
1.10xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Error spike investigation workflow
Apps command first
100%
100%
npx invocation
100%
100%
Metrics fetched for error overview
100%
100%
Metrics grouped by endpoint
100%
100%
DB flag used
62%
50%
SQL app_id filter
100%
0%
SQL timestamp filter
100%
0%
Request logs narrowed
100%
100%
path used for grouping
100%
100%
request-details used
100%
100%
Exception info reported
100%
100%
Consistent app_id
100%
100%
Consumer activity with header and JSON body analysis
consumers command used
100%
100%
consumer_id resolved
100%
100%
request-logs filtered by consumer_id
0%
100%
SQL JOIN on both app_id and consumer_id
100%
100%
Header list comprehension
80%
100%
JSON ->> operator used
100%
100%
JSON operator parentheses
33%
100%
SQL app_id filter
37%
100%
SQL timestamp filter
100%
100%
group column quoted
100%
100%
request_headers fetched
100%
100%
Daily performance trend report with date grouping
Apps command first
100%
100%
Default 7-day window
100%
100%
Metrics --interval day
100%
100%
Metrics --group-by endpoint
100%
100%
DB flag on metrics
100%
100%
SQL app_id filter
0%
100%
SQL time range filter
100%
100%
date_trunc with AT TIME ZONE
0%
100%
path used not url
100%
100%
Multiple metrics fetched
100%
100%
Consistent app_id throughout
40%
100%
39d01f1
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.