CtrlK
BlogDocsLog inGet started
Tessl Logo

provider-ephemeral-resources

Implement Terraform provider ephemeral resources with the Plugin Framework: the Open/Renew/Close lifecycle, ephemeral schema design, registration via EphemeralResources, renewal for expiring credentials, and how ephemeral values flow into write-only attributes and provider configuration. Use when adding an ephemeral resource, exposing secrets/tokens/certificates that must never persist in state or plan, deciding between an ephemeral resource and a data source, or wiring short-lived credentials from one provider into another.

78

Quality

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 tight, executable, well-sequenced body that teaches the ephemeral resource lifecycle with complete code and a validating checklist. Its only soft spot is progressive disclosure: everything is inlined in one file, which is reasonable for a self-contained code skill but leaves no layered reference structure.

DimensionReasoningScore

Conciseness

Lean throughout: it assumes Claude knows Terraform and the Plugin Framework, and spends its tokens only on non-obvious ephemeral semantics (renew cannot return a new result, Private bytes forwarding, no state) and executable code rather than padding or introductory concept explanation.

5 / 5

Actionability

Provides complete, copy-paste-ready Go covering Metadata, Schema, Open, Renew, Close, type assertions, and EphemeralResources() registration, plus concrete Design Rules (Sensitive: true, RenewAt margin, skip Close if not revocable) that are directly applicable.

5 / 5

Workflow Clarity

Clear sequenced sections (When to Use → Lifecycle → Implementation → Registration → Design Rules → Testing → Documentation) culminating in an explicit Checklist, with the Testing section providing validation guidance (echo-provider tests, version gating) for verifying the result.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with appropriately signaled one-level references (sibling skills 'if available', official docs link), but the skill is fully self-contained with no bundle files, so there is no progressive file split to navigate — slightly below the anchor that emphasizes appropriately split content.

4 / 5

Total

19

/

20

Passed

Description

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

A strong, third-person description that states concrete capabilities and gives explicit 'Use when...' triggers with natural phrasing and synonyms. It cleanly separates what the skill does from when to invoke it, with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'the Open/Renew/Close lifecycle, ephemeral schema design, registration via EphemeralResources, renewal for expiring credentials, and how ephemeral values flow into write-only attributes and provider configuration' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both 'what' (implement lifecycle/schema/registration/renewal/value flow) and 'when' ('Use when adding an ephemeral resource, exposing secrets... deciding between an ephemeral resource and a data source, or wiring short-lived credentials') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say are present with synonyms — 'adding an ephemeral resource', 'exposing secrets/tokens/certificates that must never persist in state or plan', 'wiring short-lived credentials from one provider into another' — covering the common ways this need is expressed.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Terraform Plugin Framework ephemeral resources) with triggers specific enough — ephemeral vs data source, write-only attributes, short-lived credentials — to avoid firing for unrelated provider skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
hashicorp/agent-skills
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.