C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Handles GDPR Article 21 right to object to processing, including compelling legitimate grounds assessment, ceasing processing obligations, documentation requirements, and the relationship with…
Install Right To Object
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill right-to-object -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills right-to-object --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/right-to-object .claude/skills/right-to-object && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "right-to-object" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/right-to-object into .claude/skills/right-to-object/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-object", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/right-to-objectType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill right-to-object -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills right-to-object --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/right-to-object .agents/skills/right-to-object && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "right-to-object" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/right-to-object into .agents/skills/right-to-object/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-object", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill right-to-object -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills right-to-object --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/right-to-object .cursor/skills/right-to-object && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "right-to-object" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/right-to-object into .cursor/skills/right-to-object/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-object", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/right-to-object--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill right-to-object -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills right-to-object --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/right-to-object .gemini/skills/right-to-object && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "right-to-object" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/right-to-object into .gemini/skills/right-to-object/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-object", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mukul975/Privacy-Data-Protection-Skills right-to-objectInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill right-to-object -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/right-to-object .github/skills/right-to-object && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "right-to-object" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/right-to-object into .github/skills/right-to-object/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-object", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill right-to-object -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills right-to-object --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/right-to-object .opencode/skills/right-to-object && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "right-to-object" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/right-to-object into .opencode/skills/right-to-object/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "right-to-object", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
right-to-object- GitHub stars
- 297
- Token cost
- ~1.8k tokens
- SKILL.md length
- 947 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Handles GDPR Article 21 right to object to processing, including compelling legitimate grounds assessment, ceasing processing obligations, documentation requirements, and the relationship with…
- Works in 5 steps: Receive and Log the Objection → Identify the Processing and Its Legal… → Compelling Legitimate Grounds Assessment → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Legal Foundation, Objection Processing Workflow and Response Timeline
- Runs Python scripts from its folder
What it does
Right To Object is an agent skill from mukul975/Privacy-Data-Protection-Skills. Handles GDPR Article 21 right to object to processing, including compelling legitimate grounds assessment, ceasing processing obligations, documentation requirements, and the relationship with erasure under Article 17(1)(c). Activate for right to object, Art. 21, objection to processing, legitimate interest queries.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).
It sits in Legal & Compliance, covering Privacy and GDPR. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Privacy and GDPR
Example prompts
- “Use the right-to-object skill to handle GDPR Article 21 right to object to processing, including compelling legitimate grounds assessment, ceasing…”
- “/right-to-object”
Requirements
- Python 3
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Right To Object loads about 1.8k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 947 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 947 words, ~1,843 tokens.
Download SKILL.mdSave it as
.claude/skills/right-to-object/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- right-to-object
- description
- Handles GDPR Article 21 right to object to processing, including compelling legitimate grounds assessment, ceasing processing obligations, documentation requirements, and the relationship with erasure under Article 17(1)(c). Activate for right to object, Art. 21, objection to processing, legitimate interest queries.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-subject-rights
- metadata.tags
- right-to-object, gdpr-article-21, legitimate-interest, objection-processing, cease-processing
Handling Right to Object to Processing
Overview
The right to object under GDPR Article 21(1) allows data subjects to object to processing based on legitimate interests (Art. 6(1)(f)) or public interest/official authority (Art. 6(1)(e)), including profiling based on those provisions. Upon objection, the controller must cease processing unless it demonstrates compelling legitimate grounds that override the interests, rights, and freedoms of the data subject, or processing is necessary for legal claims.
Legal Foundation
GDPR Article 21 — Right to Object
Art. 21(1) — The data subject has the right to object, on grounds relating to their particular situation, to processing based on Art. 6(1)(e) (public interest) or Art. 6(1)(f) (legitimate interests), including profiling based on those provisions. The controller shall no longer process the personal data unless it demonstrates compelling legitimate grounds for the processing which override the interests, rights, and freedoms of the data subject, or for the establishment, exercise, or defence of legal claims.
Art. 21(2)-(3) — [Covered separately in managing-direct-marketing-objection skill]
Art. 21(4) — At the latest at the time of the first communication with the data subject, the right to object shall be explicitly brought to the attention of the data subject and shall be presented clearly and separately from any other information.
Art. 21(5) — In the context of the use of information society services, the data subject may exercise their right to object by automated means using technical specifications.
Art. 21(6) — Where personal data are processed for scientific or historical research purposes or statistical purposes under Art. 89(1), the data subject has the right to object unless the processing is necessary for the performance of a task carried out for reasons of public interest.
Relationship with Art. 17(1)(c) — Erasure Following Objection
Where the data subject successfully objects and there are no overriding legitimate grounds, the data subject also has the right to erasure under Art. 17(1)(c).
Objection Processing Workflow
Step 1: Receive and Log the Objection
- Log with reference OBJ-YYYY-NNNN.
- Record the specific processing activities objected to.
- Record the data subject's particular situation and grounds.
- Acknowledge receipt within 3 business days.
- Verify identity.
- Immediately cease the objected-to processing pending the compelling grounds assessment (apply restriction under Art. 18(1)(d)).
Step 2: Identify the Processing and Its Legal Basis
- Identify all processing activities covered by the objection.
- Confirm that the legal basis for each activity is either:
- Art. 6(1)(e) — Public interest / official authority, or
- Art. 6(1)(f) — Legitimate interests
- If the processing is based on a different legal basis (consent, contract, legal obligation), the right to object under Art. 21(1) does not apply. Inform the data subject of the applicable basis and suggest the appropriate right (e.g., withdrawal of consent under Art. 7(3)).
Step 3: Compelling Legitimate Grounds Assessment
The controller must demonstrate that its legitimate grounds for processing are compelling and override the data subject's interests, rights, and freedoms. This is a higher bar than the standard legitimate interest assessment under Art. 6(1)(f).
Assessment Framework
| Factor | Controller's Position | Data Subject's Position |
|---|---|---|
| Nature of the data | What categories? How sensitive? | Privacy impact of continued processing |
| Processing purpose | How critical is this processing to the controller's operations? | Alternative means available to the controller? |
| Impact on data subject | Minimal, moderate, or significant? | What specific harm or distress does the subject describe? |
| Number of affected individuals | Does cessation affect only this subject or others? | Individual circumstances cited by the subject |
| Safeguards in place | What measures mitigate the impact on the subject? | Are safeguards sufficient from the subject's perspective? |
| Vulnerability | N/A | Is the data subject in a vulnerable situation (child, employee, patient)? |
| Legal claims | Is the data needed for establishment, exercise, or defence of legal claims? | Is the subject's objection related to a legal dispute? |
Show full SKILL.md (324 more words)Show less
Decision Criteria
- Compelling grounds established: The controller can continue processing, but must document the assessment in full and inform the data subject of the outcome and their right to complain.
- Compelling grounds NOT established: The controller must cease processing and inform the data subject. The data subject may also request erasure under Art. 17(1)(c).
- Legal claims exception: Processing may continue if necessary for legal claims, even without compelling grounds for the main processing purpose.
Step 4: Implement the Decision
If Objection Upheld (No Compelling Grounds)
- Cease all objected-to processing activities immediately.
- Remove data from processing pipelines, analytics, and any automated systems.
- Retain data only in restricted storage (if needed for legal compliance or other valid legal bases).
- Notify third-party recipients under Art. 19.
- Inform the data subject of their right to request erasure under Art. 17(1)(c).
- Update privacy notices and records of processing to reflect the change.
If Objection Overridden (Compelling Grounds)
- Resume the objected-to processing (or confirm it was never ceased, if the assessment was completed within the initial processing cycle).
- Document the compelling legitimate grounds assessment in full.
- Notify the data subject:
- The specific compelling grounds identified
- Why those grounds override the data subject's interests
- The data subject's right to lodge a complaint with the supervisory authority (Art. 77)
- The data subject's right to a judicial remedy (Art. 79)
Step 5: Document and Close
- Record the full assessment in the objection register.
- Retain the record for 3 years.
- If the objection is upheld, ensure all downstream systems reflect the cessation of processing.
- Feed findings into the legitimate interest assessment register to inform future Art. 6(1)(f) reliance.
Response Timeline
- Standard deadline: 30 calendar days from receipt.
- Extension: Up to 60 additional days for complex cases.
- Processing cessation: Must be implemented immediately upon receipt of the objection, pending the compelling grounds assessment. Processing may only resume if compelling grounds are demonstrated.
© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/right-to-object of mukul975/Privacy-Data-Protection-Skills.
- SKILL.md
- assets/template.md
- references/standards.md
- references/workflows.md
- scripts/process.py
Open the folder on GitHubat commit 9b2ef9e
Compare with similar skills
Right To Object next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Right To Object this skillmukul975/Privacy-Data-Protection-Skills | 297 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Korean Privacy Termskimlawtech/korean-privacy-terms | 586 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 943 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 943 | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Korean Privacy Terms
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
Gdpr Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing…
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Pii Contract Analyze
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
More from mukul975/Privacy-Data-Protection-Skills
All 280 skills in this repoAge Gating Services
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
AI Data Retention
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
AI Dpia
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
Dpia Mitigation Plan
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
Gdpr Accountability
mukul975/Privacy-Data-Protection-Skills
Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.
Pia Threshold Screening
mukul975/Privacy-Data-Protection-Skills
Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.
Related
Categories
Questions about Right To Object
What does Right To Object do?
Handles GDPR Article 21 right to object to processing, including compelling legitimate grounds assessment, ceasing processing obligations, documentation requirements, and the relationship with…. Right To Object is an agent skill from mukul975/Privacy-Data-Protection-Skills. Handles GDPR Article 21 right to object to processing, including compelling legitimate grounds assessment, ceasing processing obligations, documentation requirements, and the relationship with erasure under Article 17(1)(c).
When should I use Right To Object?
Right To Object fits situations like: tasks that involve Privacy and GDPR.
How do I install Right To Object in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill right-to-object -a claude-code`. Or copy the skill folder (skills/privacy/right-to-object in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/right-to-object in your project. Claude Code loads it when a task matches its description.
How do I install Right To Object in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill right-to-object -a codex`. Or copy the skill folder (skills/privacy/right-to-object in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/right-to-object in your project. Codex loads it when a task matches its description.
Can I use Right To Object in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill right-to-object -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/right-to-object, .gemini/skills/right-to-object, .github/skills/right-to-object and .opencode/skills/right-to-object in your project.
What does Right To Object need to run?
Going by SKILL.md and its folder, Right To Object needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Right To Object access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Right To Object safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Right To Object use?
Right To Object is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Right To Object use?
About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Right To Object?
Skills that share tags, products or a category with Right To Object: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 586 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 943 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Right To Object?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 297 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.
Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.