tos-decoder
Decode a terms of service or privacy policy into what you're actually agreeing to, ranked by real-world impact. Use when someone asks 'what am I agreeing to', 'decode this privacy policy', 'is this ToS bad', or 'should I click accept'. Produces a ranked findings table with a 'should I care?' verdict per finding, covering data resale, arbitration and class-action waivers, unilateral changes, content licenses, and what deletion really means.
npx skills add mohitagw15856/pm-claude-skills --skill tos-decoder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ToS Decoder Skill Nobody reads the terms — that's the business model. This skill reads them and answers the only question that matters per clause: *should you actually care?* Most of a ToS is defensive boilerplate; the value is finding the three clauses that aren't. ## What This Skill Produces - Findings ranked by real-world impact, not document order - A plain-English "what you're agreeing to" per finding, with a "should I care?" verdict - The accept / accept-with-eyes-open / avoid bottom line - What you can actually do about the bad parts (settings, opt-outs, alternatives) ## Required Inputs Ask for these only if they aren't already provided: - **The ToS / privacy policy text** — pasted in full or in sections. With excerpts, decode what's there and list which high-impact topics (arbitration, data sharing, licenses, deletion) are missing from what was shared. - **What the service is** and how they'll use it (casually vs. for business, uploading original work, storing sensitive data). - **What they're most worried about**, if anything specific. ## Framework: Severity Scale Rank findings by what happens to a real person, worst first: - 🔴 **Can cost you real money or rights** — bi
- What This Skill Produces
- Required Inputs
- Framework: Severity Scale
- Output Format
- ToS Decode: [service name]
- Quality Checks
- Anti-Patterns
- Based On
What does the tos-decoder skill do?
Decode a terms of service or privacy policy into what you're actually agreeing to, ranked by real-world impact. Use when someone asks 'what am I agreeing to', 'decode this privacy policy', 'is this ToS bad', or 'should I click accept'. Produces a ranked findings table with a 'should I care?' verdict per finding, covering data resale, arbitration and class-action waivers, unilateral changes, content licenses, and what deletion really means.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill tos-decoder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.