logging-api-requests
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill logging-api-requestsMonitor and log API requests with correlation IDs, performance metrics, and security audit trails. Use when auditing API requests and responses. Trigger with phrases like "log API requests", "add API logging", or "track API calls".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill fails to deliver on its stated purpose of monitoring and logging API requests with correlation IDs, performance metrics, and security audit trails. The content is generic API development boilerplate with no specific guidance on logging implementation, no code examples, and no explanation of how to implement the key features mentioned in the description.
Suggestions
Add concrete code examples showing how to implement request logging middleware with correlation IDs (e.g., using uuid for request tracking)
Include specific examples of logging performance metrics (request duration, response size) and security audit trails
Replace generic API development steps with a focused workflow: 1) Add logging middleware, 2) Generate correlation ID, 3) Log request/response with metrics, 4) Verify logs contain required fields
Explain or demonstrate the 'Bash(api:log-*)' command that is referenced but never defined
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that doesn't teach anything specific about API request logging. Phrases like 'This skill provides automated assistance for api request logger tasks' are meaningless filler, and the prerequisites list generic development setup rather than logging-specific requirements. | 1 / 3 |
Actionability | No concrete code examples for implementing logging, correlation IDs, or performance metrics. Instructions are vague ('Add input validation', 'Integrate authentication middleware') without showing how to actually log API requests. The Bash command 'api:log-*' is referenced but never explained or demonstrated. | 1 / 3 |
Workflow Clarity | The numbered steps are disjointed and appear to be copy-pasted from a generic API development template rather than a logging-specific workflow. Steps restart numbering mid-section, there are no validation checkpoints, and the workflow doesn't address the core task of logging requests with correlation IDs and metrics. | 1 / 3 |
Progressive Disclosure | References to external files (implementation.md, errors.md, examples.md) are present and one-level deep, but the main content is so thin that it's unclear what value those references would add. The structure exists but the overview provides almost no useful content before deferring elsewhere. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities (correlation IDs, performance metrics, security audit trails), includes natural trigger phrases users would actually say, and clearly distinguishes itself as an API logging/monitoring skill. The explicit 'Use when' and 'Trigger with phrases' sections make it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Monitor and log API requests with correlation IDs, performance metrics, and security audit trails.' This describes concrete capabilities with specific technical details. | 3 / 3 |
Completeness | Clearly answers both what (monitor/log API requests with correlation IDs, metrics, audit trails) AND when (explicit 'Use when auditing API requests' plus 'Trigger with phrases' section providing concrete examples). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'log API requests', 'add API logging', 'track API calls', 'auditing API requests'. These are common phrases developers would naturally use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on API request logging/monitoring with distinct triggers. The combination of 'API', 'logging', 'correlation IDs', and 'audit trails' creates a specific domain unlikely to conflict with general logging or other API skills. | 3 / 3 |
Total | 12 / 12 Passed |
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.