nextjs-16

I looked at your nextjs-16 skill and noticed you're tackling the async component patterns that most devs still find confusing in App Router—the streaming and Suspense integration feels like it actually accounts for real-world complexity rather than glossing over it, which is probably why you landed at an 87.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 87/100, solid B territory. This skill is grounded in Anthropic's best practices for agentic skill design. Your strongest area is Progressive Disclosure Architecture (27/30)—you've got the layering right with references tucked away cleanly. Weakest spot is Spec Compliance (11/15), mostly because your description is missing trigger phrases that help agents discover and activate the skill.

What's Working Well

• Progressive Disclosure nailed it: You're not dumping everything into one massive wall of text. The SKILL.md uses ~719 lines efficiently with practical examples and clear separation into references (httpOnly-cookie-proxy.md, better-auth-integration.md). Token economy is excellent.

• Triggering is thoughtful: Your activation keywords ("pages", "layouts", "middleware", "proxy.ts", "upgrading") are specific enough that an agent knows exactly when to reach for this skill, not generic buzzwords.

• Real-world patterns over theory: You're showing actual httpOnly cookie forwarding, async params gotchas, and the migration checklist—the stuff devs actually need when upgrading, not just "here's what changed."

• Consistent terminology: "proxy" (not middleware), "async params", "cacheComponents"—you stick to the actual Next.js 16 API names, which makes it grep-friendly and reduces confusion.

The Big One: Add Trigger Phrases to Your Description

...