render-networking

Connects Render services over the private network—internal DNS, service discovery, and cross-service communication. Use when the user needs to wire services together, resolve internal hostnames, troubleshoot connectivity between services, configure environment isolation, or understand which services can reach each other.

Quality

100%

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

100%Weight 40%Scale 1-3

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

A well-organized, concise reference body that assumes Claude's competence, supplies concrete configuration specifics, embeds diagnostic checkpoints, and cleanly offloads detailed patterns to two verified one-level-deep reference files. No verbosity or redundancy detracts from its usefulness.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — terse tables, specific port numbers, and hostname patterns with no padding explaining basic networking concepts; every section earns its place.	3 / 3
Actionability	Provides concrete, usable specifics — exact reserved ports (10000, 18012, 18013, 19099), max 75 ports, URL shape 'http://[internal-hostname]:[port]/path', discovery pattern '[hostname]-discovery', and the RENDER_DISCOVERY_SERVICE env var — which is actionable for an instruction/config skill.	3 / 3
Workflow Clarity	Well-sequenced reference sections with embedded diagnostic checkpoints ('verify the target is listening on the expected port', 'check workspace environment isolation settings before assuming DNS or app bugs') serving as feedback loops for troubleshooting.	3 / 3
Progressive Disclosure	A clear overview signals one-level-deep references explicitly ('see references/communication-patterns.md', 'see references/troubleshooting.md'), both verified to exist, with a references table summarizing each file's purpose and content appropriately split between the overview and the bundle.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, well-scoped description that concretely lists capabilities and provides an explicit 'Use when' trigger clause with natural language a user would actually say. Third person voice is used throughout with no vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'internal DNS', 'service discovery', 'cross-service communication', 'resolve internal hostnames', 'configure environment isolation' — in third person voice, matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly states both what it does ('Connects Render services over the private network...') and when to use it via an explicit 'Use when the user needs to...' clause with multiple triggers.	3 / 3
Trigger Term Quality	Natural phrasings a user would say appear in the 'Use when' clause: 'wire services together', 'troubleshoot connectivity between services', 'understand which services can reach each other', giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to 'Render services over the private network' with distinct, platform-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/render/skills/render-networking/SKILL.md
Commit: 11c74d6

Reviewed: 17 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.