pdk-templates

Vetted, compilable Rust templates for common Omni Gateway Policy Development Kit (PDK) features — JWT validation/generation, OAuth2 introspection, header/body manipulation, body streaming, rate limiting, spike control, CORS, IP filtering, JSON/XML validators, HTTP outbound calls, gRPC, DataWeave evaluation, caching, distributed locks, worker variables, request data, control flow, contracts, data storage, timers, logging, metadata, policy violations, stop_iteration, outbound policies, and PDK unit testing. Use whenever the user asks "how do I X in PDK?", "show me a PDK template for Y", "PDK Rust snippet for Z", "JWT template", "rate limit template", "header manipulation example", "PDK gRPC", "PDK DataWeave", or any prompt mapping to one of the 30 template files under templates/. Read the matching file and adapt it into the user's `src/lib.rs` (and companion files for multi-file features). For project scaffolding, build, and publish lifecycle, defer to `develop-pdk-policy`.

Quality

93%

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

86%Weight 40%Scale 1-5

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

A strong, highly actionable body: concrete adaptation steps, multi-file bundle mappings, and gotcha pre-emption. The gaps are minor — one duplicated bullet inflating length, and validation that is advisory ("suggest the user re-run make build") rather than an explicit failure-recovery loop.

Suggestions

Remove the duplicated "Composing multiple features into one policy" bullet — it appears verbatim under both "When to use this skill" and "When NOT to use this skill"; keep it only in the NOT-use section.

Turn step 5's build suggestion into an explicit validation checkpoint with a recovery loop, e.g. "run make build; if it fails, verify the gcl.yaml property names match the generated Config field names and that the .proto/build.rs/lib.rs module names agree, then rebuild."

In the template index, drop Summary text that merely restates the feature name (e.g. cors, logger rows) to trim tokens without losing navigation value.

Dimension	Reasoning	Score
Conciseness	The body is dense, assumes competence (no Rust/WASM primers), and every section carries load — but the "Composing multiple features into one policy" bullet appears verbatim under both "When to use" and "When NOT to use" (lines 17 and 24), a trimmable redundancy that keeps it below the every-token-earns-its-place anchor.	4 / 5
Actionability	Fully executable guidance: exact commands (make build-asset-files, make build), exact placeholder names to replace (exampleService, example-hmac-secret-with-256-bits-long), exact Cargo.toml lines (protobuf = "3.5.0"), and the three-place filename-consistency gotcha with specific sync points.	5 / 5
Workflow Clarity	Clear 5-step numbered sequence with post-edit build checkpoints and pre-emptive error guidance (older PDK → upgrade runbook), but validation is suggested rather than a hard checkpoint and there is no explicit if-build-fails recovery loop — minor validation gaps fitting the 4 anchor.	4 / 5
Progressive Disclosure	The body is a clean overview with a categorized index table pointing one level deep to the 30 templates/ files, plus explicit per-bundle file-to-destination mappings — every reference is a clearly signaled single hop with easy navigation.	5 / 5
	Total	18 / 20 Passed

Description

96%Weight 40%Scale 1-5

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

An exemplary description: comprehensive concrete capability enumeration, natural trigger phrasings, explicit what-and-when guidance, and sibling-skill deferrals. The only weakness is that a few standalone trigger terms ("JWT template") are not scoped to the PDK context and could cause minor cross-triggering.

Dimension	Reasoning	Score
Specificity	Enumerates a comprehensive list of concrete capabilities ("JWT validation/generation, OAuth2 introspection, header/body manipulation, body streaming, rate limiting, spike control, CORS, IP filtering...") plus a concrete action ("Read the matching file and adapt it into the user's src/lib.rs"), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	Explicitly answers both what ("Vetted, compilable Rust templates for common Omni Gateway PDK features") and when ("Use whenever the user asks...") with concrete trigger phrases, plus lifecycle deferral guidance; matches the 5 anchor exactly.	5 / 5
Trigger Term Quality	Includes natural phrases users would actually say — "how do I X in PDK?", "show me a PDK template for Y", "JWT template", "rate limit template", "header manipulation example", "PDK gRPC", "PDK DataWeave" — with synonym variations, satisfying the comprehensive natural-terms anchor.	5 / 5
Distinctiveness Conflict Risk	Clear PDK niche with explicit deferral to develop-pdk-policy, but unqualified trigger terms like "JWT template" and "rate limit template" could fire in non-PDK contexts — minor overlap risk with generic JWT/rate-limit skills, fitting the 4 anchor rather than the minimal-conflict 5 anchor.	4 / 5
	Total	19 / 20 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: mulesoft/mulesoft-dx
Path: skills/mule-development/pdk-templates/SKILL.md
Commit: 0606917

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