Name: observability-stack-setup
Rating: 59.2 (1 reviews)
Author: fernandezbaptiste

observability-stack-setup

Automated LGTM + Alloy observability stack deployment using Docker Compose. Use when setting up Claude Code observability infrastructure locally.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/observability-stack-setup/SKILL.md

The canonical home for this skill is observability-stack-setup in fernandezbaptiste/Skrillz

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and largely actionable with concrete commands and a clear sequenced workflow, but it is somewhat verbose (including time-sensitive version info) and several referenced bundle files are missing or misnamed, which hurts navigation.

Suggestions

Fix or remove broken references: rename 'references/dashboards/' to the actual 'references/grafana-dashboards/', and either create 'references/troubleshooting.md' and 'scripts/import-dashboards.sh' or drop them from the list.

Move the pinned component versions out of the main body or into a version-lock note in docker-compose-full.yml; the 'latest as of 2025-11-22' framing is time-sensitive and penalized by the conciseness rubric.

Tighten the dashboard description bullet lists (lines 73-101) by moving per-dashboard panel detail into the dashboard JSON files or a references doc, keeping only a one-line summary in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Largely efficient operational content, but includes verbose dashboard bullet lists (lines 73-101) that could live in references, plus a time-sensitive 'Version Information' section dated '2025-11-22' with pinned versions not placed in a deprecated/old-patterns section, which the rubric penalizes.	3 / 5
Actionability	Provides concrete, executable commands (docker version checks, 'docker compose up -d', health URLs, lsof/kill, curl dashboard import, 'docker compose down -v') with only minor gaps; the 'Deploy Stack' step itself delegates to a script rather than showing inline commands.	4 / 5
Workflow Clarity	A clear 7-step workflow with a Step 5 health-check validation checkpoint; however, the workflow lacks an explicit validate→fix→retry feedback loop, with error recovery relegated to a separate Troubleshooting section.	4 / 5
Progressive Disclosure	Good section structure with a dedicated References and Scripts section, but 3 of the cited bundle paths are broken or misnamed: 'references/dashboards/' (actual dir is 'grafana-dashboards/'), 'references/troubleshooting.md', and 'scripts/import-dashboards.sh' do not exist, undermining navigation.	3 / 5
	Total	14 / 20 Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A solid, third-person description that clearly states what the skill does and when to use it, with a distinct niche and good trigger keywords. It could be strengthened by listing more concrete actions and additional trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain (LGTM + Alloy observability stack) and one concrete action ('deployment using Docker Compose'), but does not enumerate multiple specific actions like configuration, dashboard import, or health verification in the description itself.	3 / 5
Completeness	Explicitly answers both what ('Automated LGTM + Alloy observability stack deployment using Docker Compose') and when ('Use when setting up Claude Code observability infrastructure locally'), but the 'when' is a single trigger scenario rather than multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural terms ('observability stack', 'Docker Compose', 'Claude Code observability infrastructure', 'setting up ... locally') a user would say, but omits common synonyms like 'monitoring', 'telemetry', 'LGTM', or component names (Grafana/Loki).	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Claude Code observability stack via Docker Compose) with distinct, specific triggers; minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: .claude/skills/observability-stack-setup/SKILL.md
Commit: 93ed392

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.