render-private-services

Configures Render private services—internal-only apps that accept traffic exclusively from other Render services over the private network. Use when the user needs an internal API, microservice, gRPC server, sidecar, or any service that should not be publicly accessible. Also use when choosing between a private service and a background worker. Trigger terms: private service, pserv, internal service, internal API, microservice, gRPC, not public, private network service.

Quality

92%

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%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.

The body is strong: executable Blueprint examples, a clear decision framework for pserv vs worker, and well-signaled one-level-deep references. The only weakness is mild redundancy—port-binding content overlaps the reference file and a few bullets restate the intro.

Suggestions

Remove the duplicated port-binding guidance from SKILL.md and point to references/patterns.md (or vice versa) to avoid maintaining the same rules in two places.

Tighten the 'How Private Services Work' bullets so they don't restate the opening sentence ('identical to web services except no public URL').

Consider moving the full microservices gateway pattern into references/patterns.md and keeping a minimal pserv example inline, since the reference already covers topology and gRPC setup.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with tables and concrete code, but port-binding guidance is duplicated between SKILL.md and references/patterns.md and the 'How Private Services Work' bullets restate the intro, so it could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready Blueprint YAML (pserv config, fromService hostport wiring, a full gateway + internal microservices pattern) with specific field values rather than pseudocode.	3 / 3
Workflow Clarity	As a configuration/reference skill with no destructive multi-step operation, the single task is unambiguous: the comparison table, rule of thumb, and ordered how-to (bind 0.0.0.0, set PORT, wire fromService) give a clear sequence.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview that links to references/patterns.md via a clearly-signaled table; the reference exists and is one level deep with no nested references, and detailed patterns are appropriately split out.	3 / 3
	Total	11 / 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.

The description is well-crafted: it uses third-person voice, names concrete capabilities, provides explicit 'Use when...' triggers, includes a comprehensive trigger-term list, and distinguishes itself from sibling Render skills. It hits the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete service configurations—internal API, microservice, gRPC server, sidecar—alongside the core configuring action, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what ('Configures Render private services... over the private network') and when (two 'Use when...' clauses covering service types and the worker decision), satisfying the 'clearly answers both what AND when' anchor.	3 / 3
Trigger Term Quality	A dedicated 'Trigger terms' line gives good coverage of natural phrases users would say (private service, internal API, microservice, not public) plus the pserv technical alias, with no common variations missing.	3 / 3
Distinctiveness Conflict Risk	The internal-only/private-network niche plus the explicit contrast with background workers ('not be publicly accessible') gives it a clear niche unlikely to conflict with render-web-services or render-background-workers.	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-private-services/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.