pytest-config

I took a look at your pytest-config skill and wanted to share some thoughts.

Links:

• GitHub
• Your skill in the SkillzWave marketplace

TL;DR

You're at 73/100, which lands you in C territory - solid fundamentals with some gaps to close. Your writing style is perfect (10/10) and your Progressive Disclosure Architecture is strong (27/30), but Spec Compliance is completely missing (0/15). That's a big opportunity - fixing the frontmatter alone could jump you to the mid-80s.

What's Working Well

• Writing is crisp - Your imperative voice and zero fluff make this easy to follow. The content is appropriately dense for Claude without being overwhelming.
• Hub-and-spoke structure is solid - Clear SKILL.md overview with detailed modules in the right depth. The navigation actually works.
• Rich examples and templates - Your conftest patterns and fixture examples are practical and ready to copy-paste. That's the kind of utility that matters.
• Strong trigger terms - "fixtures", "config", "pytest", "testing" - these hit the right keywords for discoverability.

The Big One: Frontmatter is Broken

Your YAML frontmatter is invalid and incomplete. This is tanking your Spec Compliance score (0/15) and it's an easy fix.

Current state:

---
name: pytest-config
description: |

Triggers: fixtures, config, configuration, pytest, testing
  Standardized pytest configuration...

What it should be:

---
name: pytest-config
description: Standardize pytest configuration for Claude Night Market plugins with shared fixtures and CI integration. Use when asked to "configure pytest", "pytest fixtures", "pytest config", or "setup pytest for plugins".
tags: [testing, pytest, configuration, fixtures, ci]
---

This cleans up the YAML parsing error and properly embeds your trigger phrases in the description field where the grading system expects them. +5 points right there.

Other Things Worth Fixing

1. Add a Table of Contents - Your file is 112 lines. Quick TOC at the top linking to "Quick Start", "Detailed Patterns", "Integration", "Troubleshooting" takes 2 minutes and adds clarity. +2 points.

2. Strengthen verification steps - You've got pytest -v but that's basic. Add checks for coverage metrics, marker filtering, and fixture resolution. Show developers how to validate the config actually works. +1 point.

3. Make descriptions more specific - Change "Standardized pytest configuration for plugin development" to "Standardized pytest configuration for Claude Night Market plugin testing with reusable fixtures and CI integration." Specificity helps with matching. +1 point.

Quick Wins

Here's your path forward:

• Fix frontmatter YAML (gets you +5, unblocks Spec Compliance)
• Add trigger phrases to description field (proper format for discoverability)
• Insert TOC (helps navigation on longer files)
• Expand verification steps (gives users more confidence)

You've got the core skill solid - this is mostly about format and presentation. Hit the frontmatter first and you'll see a real jump.

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