Name: dapr
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

dapr

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

Quality

70%

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/dapr/SKILL.md

Quality

Content

75%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 body is highly actionable with concrete, copy-paste-ready Membrane commands and a well-validated connection workflow, but it opens with conceptual padding about what Dapr is and has a dangling "Step 2" cross-reference. Trimming the conceptual intro and fixing the step references would improve conciseness and workflow clarity.

Suggestions

Remove or drastically shorten the opening paragraph ("Dapr is a portable, event-driven runtime...") and the "Dapr Overview" concept bullet list, since Claude already knows what Dapr is; lead instead with the Membrane integration purpose.

Fix the dangling "skip to Step 2" reference by explicitly numbering the workflow steps (e.g. label "Searching for actions" as Step 2) so the cross-reference resolves.

Add a brief validation/check step after running actions (e.g. check the `output` field for errors before proceeding) to close the workflow loop, especially for non-QUERY (mutating) actions.

Dimension	Reasoning	Score
Conciseness	The operational command content is lean, but the opening paragraph ("Dapr is a portable, event-driven runtime...") and the "Dapr Overview" concept list explain concepts Claude already knows, fitting anchor 3's "mostly efficient but includes some unnecessary explanation."	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run with --input JSON, request with a flags table) that cover the common cases, matching anchor 5's "fully executable; copy-paste ready."	5 / 5
Workflow Clarity	The connect workflow has clear state-based validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll→action→re-poll feedback loop, but the dangling "skip to Step 2" reference and the absence of a post-run validation checkpoint keep it at anchor 4.	4 / 5
Progressive Disclosure	No bundle files exist; the single ~140-line file is organized into clear, well-ordered sections for a cohesive CLI workflow, fitting anchor 4's "good structure; most content appropriately placed; minor organization gaps."	4 / 5
	Total	16 / 20 Passed

Description

66%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 cleanly covers both what and when with a distinctive, low-conflict Dapr trigger, but its action language is generic ("manage") and its keyword/trigger coverage is limited to a single domain term. Tightening verbs and adding concrete Dapr-specific triggers (state stores, pub/sub, actors) would lift specificity and completeness.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Dapr-specific actions such as "read and write state stores, publish/subscribe to topics, invoke actors, and trigger bindings".

Expand the "Use when" clause with concrete trigger phrases users would say, e.g. "Use when the user wants to manage Dapr state stores, pub/sub topics, actors, secrets, or bindings."

Add natural keyword variations/synonyms (e.g. "Dapr runtime", "Dapr sidecar", "Dapr resources") to broaden trigger term coverage beyond the single word "Dapr".

Dimension	Reasoning	Score
Specificity	Names the Dapr domain plus three action areas ("Manage data, records, and automate workflows"), but the verbs are generic ("manage") rather than concrete like extract/fill/merge, so it sits at anchor 3 rather than 4.	3 / 5
Completeness	It explicitly states both what ("Dapr integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with Dapr data."), but the when clause is a single narrow trigger rather than comprehensive, fitting anchor 4.	4 / 5
Trigger Term Quality	The natural trigger keyword is essentially a single domain term ("Dapr", "interact with Dapr data") with no synonyms or variations, matching anchor 3's "some relevant keywords but missing common variations."	3 / 5
Distinctiveness Conflict Risk	Dapr is a uniquely named platform and the triggers ("Dapr integration", "interact with Dapr data") carve a clear niche with minimal overlap risk, matching anchor 5.	5 / 5
	Total	15 / 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/dapr/SKILL.md
Commit: f484c82

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