Name: privacy-dynamics
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

privacy-dynamics

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

Quality

61%

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

Quality

Content

61%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 a concrete, well-structured CLI workflow with good state-handling checkpoints, but it carries some redundancy and padding and lacks validation around destructive action runs. Solid and usable, with room to tighten.

Suggestions

Add an explicit validation/verification step before and after running actions (e.g. dry-run, confirm scope, then verify the response state) to satisfy the destructive/batch feedback-loop expectation.

Remove the dangling 'Skip to Step 2' references or define a labeled Step 2 section so the sequence resolves.

Trim padded lines and deduplicate the action-discovery command shared between 'Searching for actions' and 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content, but it includes padded lines ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') and redundant repetition of the action-list command across 'Searching for actions' and 'Popular actions'.	3 / 5
Actionability	Provides concrete, copy-pasteable commands with real flags throughout (install, login, connection ensure, action run, request) plus a flag table, with only minor placeholders like CONNECTION_ID keeping it just short of fully copy-paste-ready.	4 / 5
Workflow Clarity	The connection lifecycle has a clear sequence and state-based feedback (READY/BUILDING/CLIENT_ACTION_REQUIRED with re-polling), but running actions can be destructive/batch with no validation step, and 'skip to Step 2' references a Step 2 that is never defined — the missing-validation cap applies.	3 / 5
Progressive Disclosure	Well-organized into clear section headers with no nested references and no bundle files needed for a CLI-driven skill; only minor inline material (the detailed clientAction state table) keeps it from a 5.	4 / 5
	Total	14 / 20 Passed

Description

62%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 answers both what and when and targets a clearly named platform, but its action verbs are generic and it lacks keyword synonyms. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Discover and classify sensitive data, manage privacy requests, and configure classifiers' instead of 'Manage data, records, and automate workflows'.

Broaden the trigger clause with natural synonyms users would say, e.g. 'Use when the user mentions Privacy Dynamics, privacy requests, data classification, or sensitive data discovery.'

Add a concrete trigger phrase tying the named actions to user scenarios to push completeness toward anchor 5.

Dimension	Reasoning	Score
Specificity	Names the domain ("Privacy Dynamics integration") and lists a few actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete; it sits above the single-verb anchor 2 yet below the multi-concrete-action anchor 4.	3 / 5
Completeness	Explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Privacy Dynamics data"), though the 'when' could be more specific, matching anchor 4.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Privacy Dynamics", "data", "records", "workflows") but lacks common synonyms or file/extension variations, matching the "some relevant keywords but missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific "Privacy Dynamics" platform gives a clear niche with minimal conflict risk, but the generic action phrasing keeps it just short of the fully-distinct anchor 5.	4 / 5
	Total	14 / 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/privacy-dynamics/SKILL.md
Commit: f484c82

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