debug-grpc-connection

Diagnose gRPC connection issues between the Bindu core and a language SDK. Use when an SDK fails to register, HandleMessages calls time out, "connection refused" on :3774, heartbeats stop arriving, or the core logs "agent silently died".

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured diagnostic skill with executable commands, a clear validated 6-step workflow, and appropriate one-level-deep references that keep the body lean. The only weakness is redundancy between the Safety and "Never do" sections, which slightly hurts token efficiency.

Suggestions

Consolidate the Safety and "Never do" sections: the generated-stubs and heartbeat prohibitions are stated twice — merge them into a single list to remove the duplication.

Keep the two genuinely new "Never do" items (running without --grpc, deploying non-localhost without mTLS) but fold them into the consolidated safety list rather than maintaining a parallel section.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence (no "what is gRPC" filler), but the Safety and "Never do" sections duplicate two prohibitions — editing generated stubs and disabling/bypassing heartbeats appear in both — so it could be tightened, matching the 2-anchor rather than the 3-anchor's "every token earns its place".	2 / 3
Actionability	It provides copy-paste-ready, fully executable commands with real flags, ports, and proto paths (e.g. "lsof -ti:3773 -ti:3774", "grpcurl -plaintext -proto proto/agent_handler.proto ... localhost:3774 list", "git log --oneline -10 -- proto/"), matching the 3-anchor; not a 2 because the guidance is complete rather than pseudocode.	3 / 3
Workflow Clarity	A 6-step Execution Contract is mirrored by 6 detailed Steps with explicit validation checkpoints and feedback loops ("list fails with connection refused → server not bound (check step 1)"; "list works but Heartbeat errors → proto mismatch"); this is read-only diagnosis rather than a destructive/batch operation, so the cap-at-2 guideline does not apply, reaching the 3-anchor.	3 / 3
Progressive Disclosure	A concise overview points to well-signaled, one-level-deep references (docs/grpc/overview.md, docs/grpc/limitations.md, sdks/typescript/src/client.ts, docs/MTLS_DEPLOYMENT_GUIDE.md) and the content is organized into clear sections with no nested-reference chains, matching the 3-anchor; no bundle files exist, so scoring is based on the references present.	3 / 3
	Total	11 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that pairs a concrete diagnostic capability with an explicit, symptom-rich Use-when trigger list and a distinctive Bindu/gRPC niche. The only soft spot is specificity, which rests on a single action verb rather than multiple distinct actions.

Dimension	Reasoning	Score
Specificity	Quotes one concrete action verb ("Diagnose gRPC connection issues between the Bindu core and a language SDK") with a well-specified domain, but unlike the 3-anchor it does not enumerate multiple distinct actions the skill performs; it is one action with several trigger scenarios, so it sits at the 2-anchor rather than 3.	2 / 3
Completeness	It explicitly answers both what ("Diagnose gRPC connection issues between the Bindu core and a language SDK") and when (an explicit "Use when..." clause with concrete triggers), satisfying the 3-anchor; the guideline capping completeness at 2 for a missing Use-when clause does not apply because the clause is present.	3 / 3
Trigger Term Quality	The "Use when" clause lists natural reportable phrases a developer would actually say — "SDK fails to register", "HandleMessages calls time out", "connection refused on :3774", "heartbeats stop arriving", "agent silently died" — giving good coverage of natural terms, matching the 3-anchor; not a 2 because common variations are not missing.	3 / 3
Distinctiveness Conflict Risk	Bindu-specific nouns and signals (port :3774, HandleMessages, "agent silently died", RegisterAgent/Heartbeat) form a clear niche with distinct triggers unlikely to fire for another skill, matching the 3-anchor; not a 2 because it would not plausibly overlap with generic skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 5 suspicious	Warning

	Total	15 / 16 Passed

Repository: GetBindu/Bindu
Path: .agents/skills/debug-grpc-connection/SKILL.md
Commit: 7b1ff75

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.