status-code-recommender

Quick Review

The skill has a clean structure but severely lacks substance. The description is extremely vague and repetitive ('status code recommender' appears 8+ times without defining what it actually does). There's no concrete task knowledge—no decision logic, no HTTP status code mappings, no recommendation rules, and no actual implementation guidance. A CLI agent would not know HOW to recommend status codes based on this documentation. The novelty score reflects that status code recommendation (choosing appropriate HTTP codes for API responses) is a genuine need that could reduce token usage, but the current implementation provides no evidence of delivering this value. To improve: define clear inputs (API operation types, success/error scenarios), provide a mapping/decision tree of status codes, and include concrete examples of recommendations.