github-actions

I was poking around your GitHub Actions skill and noticed you've got solid foundational coverage—the workflow structure is clean and the examples are practical—but there's some room to tighten up the explanations for developers hitting the more nuanced edge cases.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 75/100, which lands you in C territory (adequate, but has gaps). This is based on Anthropic's best practices for agentic skills. Your strongest area is Spec Compliance (12/15)—the YAML frontmatter and naming conventions are spot-on. The weakness is Progressive Disclosure Architecture (18/30)—a 103-line file without a table of contents makes it harder to navigate, and there's some padding in the Tips section that could tighten up token usage.

What's Working Well

• Solid trigger coverage: Your description nails the discovery phase with "CI/CD, testing, building, npm"—developers looking for GitHub Actions workflows will find this
• Practical code examples: The Quick Start template and Common Patterns section (matrix testing, npm publishing) give real, copy-paste-ready configurations
• Clean terminology: You're consistent throughout with GitHub Actions vocab—no confusing the reader with misaligned terms

The Big One

Missing table of contents for a 103-line file. Once skills cross 100 lines, readers need a navigation landmark. Right now someone skimming has to read linearly. Add this after the frontmatter:

## Contents
- [Quick Start](#quick-start)
- [Common Patterns](#common-patterns)
- [Triggers](#triggers)
- [Key Features](#key-features)
- [Tips](#tips)

This is a +5 point swing and solves the Progressive Disclosure score immediately.

Other Things Worth Fixing

1. **No verification/troubleshooting...