apitally-cli
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
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly communicates what the skill does, how it works (via CLI and DuckDB), and when to use it. It uses third person voice consistently, includes specific trigger terms, and has a clear niche that distinguishes it from other skills. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: retrieve/investigate API metrics, fetch aggregated metrics, request logs, consumers, app metadata, store data in DuckDB, run SQL queries to investigate issues. | 3 / 3 |
Completeness | Clearly answers both 'what' (fetches metrics, logs, consumers, stores in DuckDB, runs SQL queries) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Apitally', 'Apitally CLI', 'API metrics', 'API request logs', 'API consumers', 'DuckDB'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Apitally' and the unique combination of DuckDB storage with API metrics retrieval. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides comprehensive, actionable guidance for using the Apitally CLI to investigate API metrics and request logs. The workflow is clearly structured with explicit steps, validation warnings, and concrete executable examples. Minor verbosity in the Key Concepts section and some investigation patterns could be tightened, but overall the content is well-organized with excellent progressive disclosure to reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally efficient and avoids explaining basic concepts Claude already knows, but some sections are slightly verbose—e.g., the Key Concepts section explains things like 'path vs URL' and 'consumer' in more detail than necessary. The investigation patterns section is thorough but lengthy; some of the SQL examples could be more tightly presented. | 2 / 3 |
Actionability | Excellent actionability throughout. Every command is fully executable with concrete flags and arguments. SQL queries are copy-paste ready with clear placeholders. The investigation patterns provide complete, real-world examples covering error investigation, consumer tracing, header querying, JSON body querying, and date handling. | 3 / 3 |
Workflow Clarity | The investigation workflow is clearly sequenced (identify app → determine time range → fetch supporting data → fetch data → query DuckDB → iterate). It includes critical validation warnings (e.g., the bold warning about DuckDB persistence requiring WHERE filters), error handling guidance (exit code 3 → ask user to authenticate), and an explicit iteration step for refinement. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with a command quick reference, then points to well-signaled one-level-deep references for full command details (references/commands.md), DuckDB schemas (references/duckdb_tables.md), and JSON functions (references/duckdb_json_functions.md). The main content is appropriately scoped as an overview with investigation patterns, while detailed specs are deferred to reference files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- apitally/cli
- Commit
39d01f1
- Reviewed
Table of Contents
Is this your skill?
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.