Unbroker — Autonomously remove your info from data-broker sites
Unbroker — Autonomously remove your info from data-broker sites
Start with meaning, then move to detail.
This lesson explains Unbroker — Autonomously remove your info from data-broker sites as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Autonomy contract, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Unbroker — Autonomously remove your info from data-broker sites without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Autonomously remove your info from data-broker sites
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Autonomy contract
Read this after the foundation, then connect it to the previous step.
- 04When to Use
Read this after the foundation, then connect it to the previous step.
- 05Prerequisites
Read this after the foundation, then connect it to the previous step.
- 06How to Run
Read this after the foundation, then connect it to the previous step.
- 07Quick Reference
Read this after the foundation, then connect it to the previous step.
- 08Batch operation (two-phase: crawl-all, then delete)
Read this after the foundation, then connect it to the previous step.
- 09Procedure (the autonomous loop)
Read this after the foundation, then connect it to the previous step.
- 10Pitfalls
Finish here to verify the result and special cases.
Copy only after you understand the effect.
PDD="python3 scripts/pdd.py"while true:
q = $PDD next <subject>
if q.actions is empty: break
execute EVERY action in order; record each outcome via $PDD recordRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.