CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-us-privacy-multistate

Automated US multi-state privacy compliance engine for threshold mapping, policy generation, and DSR workflows. Use when: Map business data to 20+ state-specific legal thresholds automatically; Generate state-keyed privacy policies with California-specific disclosure blocks; Create DSR workflows that handle GPC signals and 45-day response windows.

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/nex-us-privacy-multistate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

15%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 reads as a product landing page rather than an operational skill: capability marketing, an FAQ, and promotional links, with zero executable guidance, workflows, or local reference files. As a result it adds almost nothing Claude can act on, and its claimed logic engine and templates are missing from the bundle entirely.

Suggestions

Replace the descriptive capability bullets with an actual procedure: numbered steps for determining applicability (e.g., collect per-state resident counts and revenue, check thresholds against a bundled table), for generating a policy from a template file, and for running a DSR intake.

Bundle the promised materials locally (threshold table, policy templates, Delete Act checklist, compliance calendar) as one-level-deep reference files in references/ and link to them from clearly signaled sections, instead of pointing to an external storefront.

Cut the marketing sections ('The problem', 'Why this beats prompting it yourself', 'Questions') and add validation checkpoints such as verifying a generated policy covers all triggered states or that a DSR response is issued within the 45-day window.

DimensionReasoningScore

Conciseness

The body is noticeably padded with marketing copy Claude does not need: "Why this beats prompting it yourself", "Free skill by Nex AI", an FAQ section that restates "What it does" and "Known limitations", and closing promo links. It only lightly explains background concepts ("SMBs selling across the US face a fragmented landscape of 20+ state privacy laws"), so it is not at the severely-verbose level of anchor 1, but well below the mostly-efficient level of anchor 3.

2 / 5

Actionability

The body only describes capabilities ("Determines legal applicability... Generates multi-state privacy policies... Builds Data Subject Request (DSR) workflows") with no commands, code, file paths, or concrete procedures — the one example is a sample Q&A, not an instruction. This matches anchor 1 ('only describes rather than instructs') and is above no lower anchor; anchor 2's 'high-level hints with missing specific steps' would require at least directional guidance toward execution.

1 / 5

Workflow Clarity

There is no sequenced process anywhere: no numbered steps for threshold mapping, policy generation, or DSR intake, and no validation checkpoints (e.g., verifying a generated policy or a DSR response window). Anchor 1 ('steps missing or incoherent; no sequence') fits; anchor 2 requires at least a rough sequence, which is absent.

1 / 5

Progressive Disclosure

Sections are well-organized (## headers, one example, limitations) and the body is ~70 lines, but the actual materials the skill promises ("the full multi-state logic engine, a suite of policy generation templates, automated DSR intake workflows") are explicitly absent — "Scripts, extension source, and templates from the original package are not in this folder" — and the only reference is to an external website, not local files. This fits anchor 3 ('some structure but could be better organized; references present but not clearly signaled') better than anchor 4, which requires appropriately placed content and clear references.

3 / 5

Total

7

/

20

Passed

Description

87%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 is strong: third-person, specific about capabilities, with an explicit multi-part 'Use when' trigger clause and a well-defined niche. Its only gaps are a few high-value trigger terms (CCPA/CPRA, 'data subject request' spelled out) and omission of some advertised capabilities like the compliance calendar and Delete Act checklist.

DimensionReasoningScore

Specificity

The description lists several specific actions — "threshold mapping, policy generation, and DSR workflows", "state-keyed privacy policies with California-specific disclosure blocks", "handle GPC signals and 45-day response windows" — in third person. It falls short of anchor 5's comprehensiveness because it omits capabilities the skill claims (Delete Act checklist, data broker registration audit, compliance calendar) and 'engine' is borderline abstract.

4 / 5

Completeness

It clearly answers 'what' ("Automated US multi-state privacy compliance engine for threshold mapping, policy generation, and DSR workflows") and 'when' with an explicit "Use when:" clause containing three concrete trigger scenarios. This matches anchor 5; the 'when' items are phrased as use cases rather than 'the user mentions X', which is a style nuance, not a missing element.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "privacy compliance", "privacy policies", "DSR workflows", "state-specific legal thresholds", "GPC signals" are phrases a user working on compliance would say. A few common terms are missing — most notably CCPA/CPRA (the phrase users most often use), spelled-out 'data subject requests', and generic 'state privacy law' — which keeps it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

"US multi-state privacy compliance" with specific triggers (state thresholds, GPC, DSR, California disclosure blocks) carves out a clear niche with minimal overlap risk against other skills. Anchor 5 fits; there is little chance this triggers for the wrong skill.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

skills/nex-us-privacy-multistate/SKILL.md

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.