CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

unbroker

Remove your info from data-broker sites, by name or phone.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/security/unbroker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 an exceptionally actionable, well-sequenced operational manual with real validation gates and feedback loops for destructive operations, backed by a genuine one-level reference bundle. Its weaknesses are repetition of a few critical rules across sections and a handful of bundle files that the entry point never points to.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific operational detail and wastes no tokens explaining concepts Claude already knows, but it is noticeably repetitive: the PeopleConnect delete-wipes-suppression rule, the CAPTCHA policy, and "subagent reports are self-reports - the parent re-verifies" each appear two or three times across Prerequisites, Batch operation, Procedure, and Pitfalls. That duplication could be collapsed by pointing once to references/methods.md, fitting anchor 3 ("mostly efficient but... could be tightened") better than 4.

3 / 5

Actionability

Guidance is fully executable and copy-paste ready: the Quick Reference table gives exact `$PDD` commands with flags, `record` invocations include the evidence JSON shape, the CDP launch command is spelled out (`chrome --remote-debugging-port=9222 --user-data-dir="$HOME/.hermes/chrome-debug"`), and a dry-run verification snippet is provided. This matches anchor 5 ("fully executable; copy-paste ready code or commands; specific examples cover the common cases").

5 / 5

Workflow Clarity

The 8-step Procedure is an explicitly sequenced loop with strong validation checkpoints and feedback loops: `confirmed_removed` only after a verifying re-scan, `doctor` readiness before starting, blocked cases re-scanned and re-queued through the stealth-browser pass, and Pitfalls prescribing error recovery (record `blocked`, flag the broker file for re-verification). Destructive/batch operations are well guarded, matching anchor 5.

5 / 5

Progressive Disclosure

Good structure: SKILL.md is an overview with clearly signaled, one-level-deep references ("references/methods.md -> 'Browser backends: scan vs execute'", site-playbooks.md, brokers/<id>.json, legal/drop.md) that all exist in the bundle. Minor gaps keep it below 5: references/state-machine.md, references/legal/ccpa.md, and references/legal/gdpr.md are never referenced from SKILL.md (state-machine.md is orphaned entirely), and sizable inline detail (CDP setup, per-method opt-out lanes, per-site exceptions) belongs in the reference files.

4 / 5

Total

17

/

20

Passed

Description

53%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 concise and names a clear, distinctive niche, but it is minimal: one action, no trigger guidance, and none of the natural vocabulary ("opt out", "people-search", broker names) users employ for this task. It reads as a competent label rather than an activation surface.

Suggestions

Add a trigger clause with concrete phrases, e.g. "Use when the user wants to opt out of people-search sites, remove their data from brokers like Spokeo/Whitepages, clean up after doxxing, or stop spam calls by scrubbing their number."

Include the domain's natural synonyms users actually say - "opt out", "people-search sites", "data broker removal" - alongside "data-broker sites".

Briefly surface the additional concrete capabilities the skill has (finding where info is exposed, recurring re-scan monitoring, FTC Do Not Call registration) so specificity reflects actual coverage.

DimensionReasoningScore

Specificity

"Remove your info from data-broker sites, by name or phone" names the domain and one concrete action with two lookup keys, but stops at a single action - no mention of scanning, recurring re-checks, or registry filings. This matches anchor 3 ("names domain and 1-2 concrete actions, but not comprehensive"), not 4, which requires several specific listed actions.

3 / 5

Completeness

The "what" is clear (remove personal info from data-broker sites, searchable by name or phone), but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description. Per the judging guidelines, a missing trigger clause caps completeness at 3, which is exactly the anchor: clear what, when missing or only weakly implied.

3 / 5

Trigger Term Quality

"data-broker sites" and "remove your info" are relevant natural terms, but the description misses the domain's most common user phrasings: "opt out", "people-search sites", and specific broker names (Spokeo, Whitepages) users actually say. Anchor 3 ("some relevant keywords but missing common variations or synonyms") is the best fit; it is above 2 (which would need only generic keywords) but well below the synonym- and name-rich coverage of 5.

3 / 5

Distinctiveness Conflict Risk

"data-broker sites" carves out a clear niche with distinct triggers and low conflict risk, but the bare phrase "remove your info" could lightly overlap adjacent deletion/privacy skills (account deletion, search-result removal). Mostly distinct with minor overlap risk fits anchor 4; it lacks the explicit distinct trigger phrases that would justify 5.

4 / 5

Total

13

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

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

referenced_paths_exist

Referenced path issues: 1 missing, 2 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/security/unbroker/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.