CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-coppa-2026-pack

Audit and generate compliance documentation for the 2026 FTC COPPA Rule amendments. Use when: Classify services as child-directed or mixed audience using FTC criteria; Generate unbundled parental consent flows for third-party ad sharing; Draft mandatory written data retention and information security programs.

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-coppa-2026-pack/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

11%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 product landing page, not a skill: it promotes capabilities and answers purchase questions while explicitly acknowledging that the scripts, extension source, and templates that constitute the actual skill are not included. Claude reading it gains no ability to audit COPPA compliance or draft the required documents.

Suggestions

Replace the marketing sections ("The problem", "Why this beats prompting it yourself", the purchase/compatibility FAQ) with the actual operational content: the FTC multi-factor "totality of circumstances" criteria, the 2026 expanded personal-information definitions, and the state overlay requirements for Arkansas, Connecticut, and California.

Add a step-by-step workflow (classify audience → inventory data against 2026 definitions → assess consent flows → draft retention/security documents) with validation checkpoints, e.g. verifying a drafted parental notice against the 2026 required-elements checklist before finalizing.

Ship the advertised templates and scripts (consent-flow patterns, direct-notice drafts, retention policy and security program skeletons) in references/ or scripts/ and link them from clearly signaled sections in SKILL.md, since the body currently states they are "not in this folder".

DimensionReasoningScore

Conciseness

Noticeable padding: sections like "Why this beats prompting it yourself" and a five-question FAQ about purchase, lifetime updates, and platform compatibility ("buyers receive lifetime access to all version updates") are marketing copy that earns no instructional value. Not score 1 because it does not belabor concepts Claude already knows (there is no COPPA tutorial content); not score 3 because the majority of the body is promotional rather than operational, so it cannot be considered "mostly efficient".

2 / 5

Actionability

There is no executable guidance anywhere: the body only describes what the (absent) package does — "Triages services into child-directed, mixed, or general audience buckets", "Generates dual-layer consent flows" — with no criteria, templates, commands, or examples of how to perform them. It states "Scripts, extension source, and templates from the original package are not in this folder", so the concrete material is explicitly missing. This matches the score-1 anchor (only describes rather than instructs).

1 / 5

Workflow Clarity

No sequence of steps exists; the body is organized as problem/use-case/FAQ marketing sections rather than an audit or drafting procedure. A COPPA audit is inherently multi-step (classify audience, inventory data, generate consent flows, draft retention/security documents) but none of these are sequenced or given checkpoints, matching the score-1 anchor (steps missing, no sequence).

1 / 5

Progressive Disclosure

The skill's real content (service-triage logic, consent-flow templates, retention/security policy templates, state overlay mappings) is advertised but neither inlined nor present in any bundle file — no references/, scripts/, or assets/ directories exist — and no paths point to where it lives. Structure is minimal with the detailed material effectively unreachable, fitting the score-2 anchor; not score 1 because the body is not a monolithic wall of text or nested-reference chain, and not score 3 because there are no real references present at all to be "clearly signaled".

2 / 5

Total

6

/

20

Passed

Description

92%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: it enumerates concrete third-person capabilities, includes an explicit "Use when:" clause with concrete triggers, and carves out a distinct niche around the 2026 COPPA amendments. The only weakness is modest keyword variation — a few natural synonyms (children's privacy, under-13) are absent.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Audit and generate compliance documentation", "Classify services as child-directed or mixed audience", "Generate unbundled parental consent flows", "Draft mandatory written data retention and information security programs" — giving comprehensive coverage of the skill's functions. This matches the score-5 anchor (multiple specific concrete actions, comprehensive) rather than score 4, which expects minor gaps in coverage; each advertised capability of the pack is named.

5 / 5

Completeness

Explicitly answers both: what ("Audit and generate compliance documentation for the 2026 FTC COPPA Rule amendments") and when (an explicit "Use when:" clause with three concrete trigger conditions). This matches the score-5 anchor with concrete trigger phrases rather than score 4, whose 'when' is more generic; all verbs are third person, so no voice penalty applies.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "COPPA", "FTC", "child-directed", "parental consent", "compliance", "data retention" — terms a user with this need would plausibly say. Not score 5 because common variations like "children's privacy", "kids app", "under-13", or "privacy policy" are missing, leaving a few natural entry terms uncovered.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (2026 FTC COPPA Rule amendments) with distinct triggers (unbundled parental consent, child-directed classification) and minimal overlap with generic privacy-policy or document skills. It fits the score-5 anchor (clear niche, distinct triggers, minimal conflict risk); score 4 would require some overlap with closely related skills, which is not evident.

5 / 5

Total

19

/

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-coppa-2026-pack/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.