observability

I took a look at your observability skill and wanted to share some thoughts.

Links:

• GitHub
• Your skill in the SkillzWave marketplace

The TL;DR

You're at 56/100, which puts you in F territory. This one's primarily blocked by a structural issue—no frontmatter—that tanks your spec compliance score (0/15). The good news? Your Ease of Use is solid at 20/25, and you've got real observability content here. Fix the frontmatter and trim some verbosity, and you'll jump significantly.

What's Working Well

• Clear trigger phrases - Terms like "observability," "research," "workflow" are discoverable and specific, which helps people find this when they need it
• Practical content structure - You've got QUICK-REFERENCE.md and layered specialist skills, which shows you're thinking about progressive disclosure
• Real examples - The YAML and code snippets actually help people understand what observability patterns look like
• Consistent terminology - You stick with observability language throughout, no confusing jumps between concepts

The Big One: Missing Frontmatter

This is your main blocker. Your SKILL.md needs to start with YAML frontmatter—right now there's nothing, which automatically zeros out your entire Spec Compliance score (0/15).

Here's what needs to be at the top of skills/research/observability/SKILL.md:

---
name: observability
description: Guides distributed systems observability setup and troubleshooting. Use when asked to "observability", "distributed tracing", "metrics and logging", or "monitoring strategies".
---

This one fix gets you +5 points just for valid frontmatter, then another +8 for name and description quality. That's a 13-point jump right there.

Other Things Worth Fixing

1. Trim the verbosity - Your file is 295 lines with repeated sections and Turkish text that doesn't belong. Condense to essential content, remove duplication. Target: under 200 lines. (~+5 points)

2. Add a Table of Contents - For files over 100 lines, readers need a navigation anchor at the top. Add a simple TOC linking to your main sections. (~+3 points)

3. Numbered workflow steps - Replace bullet lists with numbered step sequences for setup tasks. People following along need clarity on order. Currently it's "Use when..." bullets, but should be "Step 1, Step 2" for actual workflows. (~+2 points)

4. Tighten the language - Phrases like "Expert distributed tracing" are marketing-y. Stick to objective, instructional tone: "Implement distributed tracing with OpenTelemetry" instead. (~+1-2 points)

Quick Wins

• Add frontmatter YAML block (name + description with triggers) — +13 points
• Remove Turkish sections and condense file — +5 points
• Add TOC for navigation — +3 points
• Convert bullet checklists to numbered workflow steps — +2 points

That's 23 points of low-hanging fruit that gets you to 79/100 territory and into C-grade range.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that installs skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.