feat: improve api-patterns skill score (59% → 97%)

[yogesh-tessl]

Hey @malinskibeniamin 👋

ran your skills through tessl skill review at work and found some targeted improvements. Here's the before/after:

Skill	Before	After	Change
api-patterns	59%	97%	+38%

Changes made to api-patterns

Description improvements (biggest impact - 32% → 100%):

• Expanded from vague "Connect Query patterns for API calls" to a specific description listing concrete actions: generating query hooks from protobuf services, creating mutation handlers with cache invalidation, and wiring toast error messages
• Added an explicit "Use when..." clause with distinctive trigger terms (useQuery, useMutation, @connectrpc, protobuf services, gRPC-Web, .proto files, formatToastErrorMessage) to reduce false-positive activation and avoid overlap with generic data-fetching skills
• Wrapped description in a quoted string for standard frontmatter formatting

Content improvements (65% → 92%):

• Added a complete inline mutation workflow with explicit 4-step sequence: call mutation → handle errors with formatToastErrorMessage → invalidate cache → confirm success
• Included a copy-paste ready TSX code example showing the full pattern with proper imports from @connectrpc/connect-query and @tanstack/react-query
• Added src/utils/toast.utils.ts to key locations table for discoverability
• Updated activation conditions from generic terms to specific, actionable trigger scenarios
• Prefixed rule file references with rules/ path for clarity

---

also stress-tested your api-patterns skill against a few real-world task evals and it held up really well on mutation-with-cache-invalidation workflows. The Connect Query + formatToastErrorMessage pattern guidance was solid. Kudos for that.

quick honest disclosure. I work at https://github.com/tesslio where we build tooling around skills like these. Not a pitch, just saw room for improvement and wanted to contribute.

if you want to self-improve your skills, or define your own scenarios to pressure test, just ask your agent (Claude Code, Codex, etc.) to evaluate and optimize your skill with Tessl. Ping me @yogesh-tessl, if you hit any snags.