restate

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

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 76/100, solidly in C territory (70-79). This is based on Anthropic's best practices for skill architecture.

The good news: Your metadata and ease of use are solid (22/25 on EoU). Strong trigger coverage and clean terminology around ctx, durable, and handler.

The rough patch: Progressive Disclosure Architecture is dragging you down (19/30). You've got 257 lines crammed into a single file with no reference architecture, and that's eating your score.

What's Working Well

• Frontmatter is chef's kiss — Valid YAML, specific name, and a comprehensive trigger list that actually captures intent patterns (durable execution, distributed workflows, Virtual Objects)
• Consistent terminology — Using ctx, durable, and handler throughout makes it predictable for developers
• Real-world patterns — Code examples showing services, workflows, and Virtual Objects demonstrate genuine value for distributed systems problems
• Success criteria checklist — Actually helpful for validation

The Big One: Monolithic File Architecture

Severity: High | Impact: +6 points possible

Your 257-line skill violates the layered structure principle. Everything — extended patterns, research examples, detailed code — is inline, which inflates token load for simple queries.

The fix: Extract into a references directory:

• Move patterns section → references/patterns.md
• Move research section (lines 203-224) → references/research.md
• Keep SKILL.md under 150 lines for quick navigation

This is the single biggest lever for improvement. You'd jump from 19/30 to 25/30 on PDA alone.

Other Things Worth Fixing

1. Add a table of contents — Files over 100 lines need upfront navigation. Add a TOC after frontmatter with section anchors so developers can jump to what they need.

2. Trim the research examples — Your research section shows complete MCP call JSON structures (lines 203-224). Show minimal patterns inline; move verbose examples to references/research-patterns.md.

3. Verify workflow steps — After step 5 in quick start, add a verification command like curl http://localhost:9170/services to confirm registration. Small thing, but it closes the loop.

4. Fix code fence syntax — Line 192 has 4 backticks instead of 3. Easy win.

Quick Wins

1. Create references directory — Most impactful fix (6 points)
2. Add TOC — Improves navigation (2 points)
3. Trim research examples — Tighter writing (1 point)
4. Add workflow verification — Better UX (1 point)

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.