grpc-microservices
Comprehensive gRPC microservices skill covering protobuf schemas, service definitions, streaming patterns, interceptors, load balancing, and production gRPC architecture
48
37%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/luxor-backend-toolkit/skills/grpc-microservices/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description reads like a topic list or course syllabus rather than an actionable skill description. While it establishes the gRPC domain clearly, it fails to specify concrete actions Claude can perform and completely lacks trigger guidance for when to select this skill. The passive, noun-heavy phrasing ('comprehensive skill covering...') doesn't help Claude understand what it should actually do.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about gRPC services, .proto files, protocol buffers, or RPC communication'
Replace topic categories with concrete actions using verbs: 'Generates protobuf schemas, implements streaming RPCs, configures interceptors for authentication/logging'
Include common user phrasings and file extensions: '.proto', 'protocol buffers', 'bidirectional streaming', 'gRPC client/server'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (gRPC microservices) and lists several technical areas (protobuf schemas, service definitions, streaming patterns, interceptors, load balancing), but these are categories rather than concrete actions. No verbs describing what the skill actually does. | 2 / 3 |
Completeness | Describes what areas it covers but lacks any 'Use when...' clause or explicit trigger guidance. The 'when' is completely missing, which per the rubric should cap this at 2, but since the 'what' is also weak (listing topics rather than capabilities), this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'gRPC', 'protobuf', 'microservices', 'streaming', 'interceptors' that users might mention, but missing common variations like '.proto files', 'RPC', 'protocol buffers', or action-oriented phrases users would say. | 2 / 3 |
Distinctiveness Conflict Risk | The gRPC focus provides some distinctiveness from general coding skills, but 'microservices' and 'load balancing' could overlap with other architecture or infrastructure skills. The lack of explicit triggers increases conflict risk. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent, actionable code examples covering gRPC comprehensively, but suffers from severe verbosity and poor organization. It explains fundamental concepts Claude already knows and presents everything in a single massive document rather than using progressive disclosure. The content would be significantly more effective at 20-30% of its current length with proper file splitting.
Suggestions
Remove explanatory sections about what gRPC/protobuf are and their advantages - Claude knows this. Start directly with schema design patterns and code examples.
Split into multiple files: SKILL.md (overview + quick start), STREAMING.md, INTERCEPTORS.md, DEPLOYMENT.md, ERROR_HANDLING.md with clear navigation links.
Add explicit validation checkpoints to multi-step workflows, especially for deployment (e.g., 'Verify pod is running: kubectl get pods | grep grpc-service').
Condense the 'When to Use This Skill' section to 2-3 bullet points - the current 12 items are redundant and verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~1500+ lines. Explains concepts Claude already knows (what gRPC is, what Protocol Buffers are, HTTP/2 characteristics). Contains extensive background information and explanations that don't add actionable value. | 1 / 3 |
Actionability | Provides fully executable code examples throughout - complete Go implementations for interceptors, streaming patterns, error handling, and deployment configurations. Code is copy-paste ready with proper imports and context. | 3 / 3 |
Workflow Clarity | Steps are listed for various patterns but lack explicit validation checkpoints. For example, deployment sections show configs but don't include verification steps. The graceful shutdown example is good, but most multi-step processes lack feedback loops. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline despite being comprehensive enough to warrant splitting into separate reference documents (e.g., INTERCEPTORS.md, STREAMING.md, DEPLOYMENT.md). | 1 / 3 |
Total | 7 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1508 lines); consider splitting into references/ and linking | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 12 / 16 Passed | |
- Repository
- manutej/luxor-claude-marketplace
- Commit
1861cc9
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.