CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

consent-registry

Use when the user asks to "log this subscriber's opt-in", record unsubscribes/complaints, or query lawful basis; curates pseudonymous consent facts through the append-only consent stream and applies suppression/erasure tombstones immediately. Not for SEND scoring — use email-quality-auditor; not for building segments — use list-segment-builder. 订阅同意台账/实时退订抑制/合法性依据登记

Quality

74%

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 ./protocol/consent-registry/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 well-structured with a clear unit/read/write contract and a sequenced procedure containing real validation checkpoints, but it is held back by a missing bundle (all referenced protocol files and the registry script are absent), no concrete examples for the core append/suppress/erase mutations, and over-dense run-on steps that need tightening. As shipped, the skill is not executable end-to-end because every mutation path is defined in files that are not present.

Suggestions

Ship the bundle: add references/registry-event-protocol.md, references/runtime-invocation.md, and scripts/registry-events.py (or remove/inline the dependency), since the Procedure and Quick Start are unusable without them and progressive_disclosure currently scores 2.

Add copy-paste-ready invocation examples for the core mutations — an `upsert`, a `suppress`, and a `safety-append consent` erase — showing the actual command and a minimal valid request payload, mirroring the existing is-suppressed example.

Split Procedure step 4 into sub-steps (complete request → append now vs. prepare immediate-suppress-handoff → host sequence → required user disclosures) to eliminate the ~180-word run-on paragraph and improve both conciseness and workflow clarity.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and is information-dense, but step 4 of the Procedure is a ~180-word run-on paragraph packing many rules, edge cases, and field lists into one block, and the Skill Contract paragraph similarly over-stuffs. It could be tightened substantially, matching the 'mostly efficient but could be tightened' anchor rather than the minor-trim 4 anchor.

3 / 5

Actionability

One fully executable command is given ('python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" is-suppressed <subject-id>') plus an env-resolution snippet, but the core mutation paths (upsert, suppress, erase, safety-append) are never shown as concrete invocations or payloads — only as capability names and field lists, i.e., high-level hints missing the specific steps to execute. This sits between the incomplete-guidance 3 anchor and the mostly-executable 4 anchor, noticeably below the midpoint.

3 / 5

Workflow Clarity

The 8-step Procedure is clearly sequenced with explicit validation checkpoints ('verify the registry script, event schema, and system catalog before invoking', '`verify consent` and re-run `is-suppressed` for changed subjects') and a degraded-path branch when the root runtime is unavailable. It falls short of 5 because there is no explicit error-recovery loop if `verify consent` fails, and step 4's branching conditions are buried in prose.

4 / 5

Progressive Disclosure

The body signals one-level-deep references clearly (Registry event protocol, runtime-invocation, SEND benchmark) and is well-sectioned, but the referenced files do not exist in the bundle: there is no references/, scripts/, or assets/ directory, so registry-event-protocol.md, runtime-invocation.md, and scripts/registry-events.py — which the entire procedure depends on — are dangling. Scored against the actual (empty) bundle structure, the skill delegates its core content to nonexistent files, which is a broken disclosure structure worse than the merely-could-be-better-organized 3 anchor.

2 / 5

Total

12

/

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.

A strong description with an explicit 'Use when...' trigger clause, concrete capability statements, and unusually good sibling-skill disambiguation via negative boundaries. Main weaknesses are a few missing natural synonyms (opt-out, GDPR/erasure-request) and slightly abstract phrasing around 'curates pseudonymous consent facts'.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('record unsubscribes/complaints', 'query lawful basis', 'applies suppression/erasure tombstones immediately') tied to a concrete mechanism ('the append-only consent stream'). It falls short of 5 because coverage has gaps (e.g., restore and re-subscription are absent) and 'curates pseudonymous consent facts' is semi-abstract; it exceeds 3 because more than 1-2 specific actions are named.

4 / 5

Completeness

It explicitly answers both what ('curates pseudonymous consent facts through the append-only consent stream and applies suppression/erasure tombstones immediately') and when ('Use when the user asks to "log this subscriber's opt-in", record unsubscribes/complaints, or query lawful basis') with concrete trigger phrases, matching the 5 anchor. Third-person voice is used correctly.

5 / 5

Trigger Term Quality

Natural user phrasing is present, including a quoted trigger ('log this subscriber's opt-in') plus 'record unsubscribes/complaints' and 'query lawful basis'. A few natural synonyms are missing (opt-out, GDPR/right-to-erasure, suppression list, do-not-email), which keeps it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (consent evidence and live suppression) with explicit negative boundaries ('Not for SEND scoring — use email-quality-auditor; not for building segments — use list-segment-builder'), giving minimal conflict risk and matching the 5 anchor.

5 / 5

Total

18

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 10 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

protocol/consent-registry/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.