.claude/skills/<skill-name>1 structural issue
- error: The fixed release did not provide readable SKILL.md content.
SKILL.md
Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Add observability and instrumentation to applications �� metrics, logs, traces, and dashboards
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/<skill-name>SKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/<skill-name>SKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/<skill-name>SKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @paudyyin/observability-and-instrumentationclawhub inspect @paudyyin/observability-and-instrumentation --version 1.0.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
content unavailableThis is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:a94c058ccbf734bc1b883b8719fdff654e305737042f9ad3b02cdb36b2c70453skill-card.mdSKILL.mdObservability and Instrumentation skill v1.0.0 – initial release: - Provides clear, step-by-step guidance on adding observability and instrumentation (metrics, logs, traces, dashboards) to applications. - Emphasizes problem-driven telemetry, structured logging practices, and use of unique request IDs. - Details best practices for metrics (RED/USE methods, low-cardinality labels), distributed tracing (OpenTelemetry), and actionable, symptom-based alerting. - Includes verification checklists, common mistakes and red flags, and integration tips with related skills.