Name: doppler
Rating: 55.2 (1 reviews)
Author: membranedev

doppler

Doppler integration. Manage data, records, and automate workflows. Use when the user wants to interact with Doppler data.

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/doppler/SKILL.md

Quality

Content

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

The content is a well-structured, mostly executable guide to driving Doppler through the Membrane CLI, with a clear connection state-machine workflow and a useful proxy flag table. Its main weaknesses are a padded introductory paragraph and a couple of broken/inconsistent step references ("Step 2", "1b").

Suggestions

Trim the opening paragraph to one line; remove the audience list ("used by developers, DevOps engineers, and security teams...") and the auth-plumbing editorializing.

Fix the broken cross-reference: either label an actual "Step 2" (e.g., the Searching for actions section) or replace "skip to Step 2" with a concrete section link.

Resolve or define the CONNECTION_ID and QUERY placeholders inline (e.g., note where the connection id comes from) so the run/list examples are fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but the opening paragraph explains what Doppler is and who uses it ("helps developers and organizations securely store... used by developers, DevOps engineers, and security teams") and lines like "so you can focus on the integration logic rather than auth plumbing" add padding Claude does not need, matching the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action list/run, and request, plus a flag table for proxying, but relies on unresolved placeholders like CONNECTION_ID and QUERY, fitting the score-4 anchor of mostly executable guidance with minor gaps.	4 / 5
Workflow Clarity	The connection setup is a clear state-machine sequence with feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll after the user acts), but it references "Step 2" which is never labeled and the "1b" sub-step numbering is inconsistent, matching the score-4 anchor of a clear sequence with minor gaps.	4 / 5
Progressive Disclosure	The body is well-organized into headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested or buried references and no bundle files needed for a CLI skill, but at ~140 lines it exceeds the simple-skill threshold and a few subsections (the connection state machine, the proxy flag table) could be split out, matching the score-4 anchor of good structure with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

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

The description correctly pairs a what and a when and anchors on a distinct named product, but its actions are vague abstractions ("manage data, records, automate workflows") and its trigger terms omit the natural vocabulary (secrets, config, environment) users actually employ.

Suggestions

Replace generic verbs with concrete Doppler capabilities, e.g. "Read and manage secrets, configs, and environments; rotate and sync secrets across projects."

Add natural trigger phrases users would say, e.g. "Use when the user wants to manage Doppler secrets, configs, or environments, or sync secrets into a project."

Drop the filler clause "automate workflows" unless a specific workflow action is meant, to avoid over-claiming.

Dimension	Reasoning	Score
Specificity	It names the domain ("Doppler integration") but the actions — "Manage data, records, and automate workflows" — are generic abstractions rather than concrete capabilities like reading secrets or rotating configs, matching the score-2 anchor of minimal/generic actions.	2 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Doppler data"), but the when is generic rather than concrete trigger phrases, fitting the score-4 anchor where both are present but when could be more specific.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Doppler data" surfaces the Doppler keyword and "data," but misses natural synonyms users would actually say (secrets, config, environment), matching the score-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Doppler gives it a clear niche with low conflict risk, but the generic "data" trigger leaves minor overlap with other data-management skills, matching the score-4 anchor of mostly distinct with minor overlap risk.	4 / 5
	Total	13 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/doppler/SKILL.md
Commit: f484c82

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