C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Manages the absolute right to object to direct marketing under GDPR Article 21(2)-(3), covering immediate cessation of all direct marketing processing, suppression list management, cross-channel…
Install Marketing Objection
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill marketing-objection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills marketing-objection --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/marketing-objection .claude/skills/marketing-objection && 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 "marketing-objection" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/marketing-objection into .claude/skills/marketing-objection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-objection", 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/marketing-objectionType 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 marketing-objection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills marketing-objection --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/marketing-objection .agents/skills/marketing-objection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "marketing-objection" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/marketing-objection into .agents/skills/marketing-objection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-objection", 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 marketing-objection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills marketing-objection --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/marketing-objection .cursor/skills/marketing-objection && 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 "marketing-objection" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/marketing-objection into .cursor/skills/marketing-objection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-objection", 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/marketing-objection--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 marketing-objection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills marketing-objection --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/marketing-objection .gemini/skills/marketing-objection && 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 "marketing-objection" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/marketing-objection into .gemini/skills/marketing-objection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-objection", 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 marketing-objectionInstalls 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 marketing-objection -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/marketing-objection .github/skills/marketing-objection && 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 "marketing-objection" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/marketing-objection into .github/skills/marketing-objection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-objection", 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 marketing-objection -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 marketing-objection --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/marketing-objection .opencode/skills/marketing-objection && 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 "marketing-objection" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/marketing-objection into .opencode/skills/marketing-objection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-objection", 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
marketing-objection- GitHub stars
- 301
- Token cost
- ~2.1k tokens
- SKILL.md length
- 1,016 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Manages the absolute right to object to direct marketing under GDPR Article 21(2)-(3), covering immediate cessation of all direct marketing processing, suppression list management, cross-channel…
- Works in 8 steps: Receive the Objection → Determine the Scope → Immediate Cessation → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Legal Foundation and Direct Marketing Objection…
- Runs Python scripts from its folder
What it does
Marketing Objection is an agent skill from mukul975/Privacy-Data-Protection-Skills. Manages the absolute right to object to direct marketing under GDPR Article 21(2)-(3), covering immediate cessation of all direct marketing processing, suppression list management, cross-channel enforcement, and profiling for marketing purposes. Activate for marketing opt-out, unsubscribe, Art. 21(2), direct marketing objection queries.
Its SKILL.md is about 2.1k 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 marketing-objection skill to manage the absolute right to object to direct marketing under GDPR Article 21(2)-(3), covering immediate…”
- “/marketing-objection”
Requirements
- Python 3
Workflow steps
8 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
Marketing Objection loads about 2.1k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 1,016 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). 1,016 words, ~2,077 tokens.
Download SKILL.mdSave it as
.claude/skills/marketing-objection/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- marketing-objection
- description
- Manages the absolute right to object to direct marketing under GDPR Article 21(2)-(3), covering immediate cessation of all direct marketing processing, suppression list management, cross-channel enforcement, and profiling for marketing purposes. Activate for marketing opt-out, unsubscribe, Art. 21(2), direct marketing objection queries.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-subject-rights
- metadata.tags
- direct-marketing-objection, gdpr-article-21, suppression-list, marketing-opt-out, unsubscribe
Managing Direct Marketing Objection
Overview
The right to object to direct marketing under GDPR Article 21(2)-(3) is an absolute right — there is no balancing test, no compelling grounds exception, and no basis on which the controller can refuse. When a data subject objects to processing for direct marketing purposes, the controller must cease that processing immediately. This skill provides the complete operational procedure for handling marketing objections across all channels.
Legal Foundation
GDPR Article 21(2)-(3) — Direct Marketing Objection
Art. 21(2) — Where personal data are processed for direct marketing purposes, the data subject has the right to object at any time to processing of personal data concerning them for such marketing, which includes profiling to the extent that it is related to such direct marketing.
Art. 21(3) — Where the data subject objects to processing for direct marketing purposes, the personal data shall no longer be processed for such purposes.
Key Characteristics
- Absolute right: No balancing test. No compelling grounds exception. No fee. No refusal possible.
- Immediate effect: Processing for direct marketing must cease as soon as the objection is received.
- Scope: Covers ALL forms of direct marketing including email, SMS, telephone, postal mail, targeted online advertising, and profiling for marketing segmentation.
- Includes profiling: Any profiling conducted for the purpose of direct marketing must also cease.
Privacy and Electronic Communications Regulations 2003 (PECR)
- Regulation 22 — Unsolicited communications by electronic mail: requires prior consent for marketing emails to individuals (unless soft opt-in exception applies).
- Regulation 21 — Unsolicited calls for direct marketing: requires compliance with the Telephone Preference Service (TPS).
ePrivacy Directive 2002/58/EC (as amended by 2009/136/EC)
- Article 13 — Unsolicited communications: consent required for electronic marketing communications, with limited exception for existing customer relationships.
Direct Marketing Objection Workflow
Step 1: Receive the Objection
Objections may arrive through any channel:
| Channel | Example | Handling |
|---|---|---|
| Email unsubscribe link | Click on "Unsubscribe" in marketing email | Automated processing within 24 hours |
| Reply to marketing email | "Please stop emailing me" | Manual triage, process within 24 hours |
| Web form | Privacy preference centre opt-out | Automated processing immediately |
| Telephone | "Take me off your mailing list" | Agent records objection, process within 24 hours |
| Written letter | "I object to you using my data for marketing" | Process within 48 hours of receipt |
| Social media message | Direct message requesting marketing cessation | Process within 48 hours of receipt |
| Verbal (in-person) | "Stop sending me marketing" | Staff member records objection, process within 24 hours |
- Log with reference MKT-YYYY-NNNN.
- Record the channel, timestamp, and scope of the objection.
- No identity verification is required beyond confirming the identity matches the marketing recipient (e.g., the email address matches the unsubscribe request).
Step 2: Determine the Scope
- Full opt-out: Data subject objects to ALL direct marketing — cease all marketing processing.
- Partial opt-out: Data subject objects to specific channels only (e.g., "stop calling me but email is fine") — cease the specified channels.
- If unclear: Treat as a full opt-out. Contact the data subject to clarify preferences only after cessation.
Step 3: Immediate Cessation
Within 24 hours of receiving the objection:
- Email marketing: Remove from all active email marketing lists, suppress email address.
- SMS marketing: Remove from SMS distribution lists, suppress mobile number.
- Telephone marketing: Add to internal do-not-call list, register with Telephone Preference Service (TPS) if applicable.
- Postal marketing: Remove from postal mailing lists, add to internal do-not-mail list.
- Online targeted advertising: Remove from remarketing audiences, customer match lists, and lookalike audience seed lists.
- Profiling for marketing: Cease all profiling activities related to marketing segmentation for this individual. Remove from marketing segments.
Show full SKILL.md (425 more words)Show less
Step 4: Suppression List Management
A suppression list is essential to prevent re-subscription or re-targeting:
- Add the data subject's identifiers to the marketing suppression list:
- Email address (store as SHA-256 hash for matching against future lists)
- Phone number (store as SHA-256 hash)
- Postal address (store normalised address components)
- Customer ID
- The suppression list entry must be retained indefinitely (or until the data subject explicitly consents to marketing again) to prevent re-contact.
- The suppression list must be checked before every marketing campaign distribution:
- Email campaigns: check suppression list before send
- SMS campaigns: check suppression list before send
- Postal campaigns: check suppression list before print/dispatch
- Online advertising: exclude suppression list from audience uploads
- New data imports must be screened against the suppression list before any marketing processing.
Step 5: Cross-Channel Enforcement
Ensure the objection is enforced across ALL marketing channels and systems:
| System | Action | Owner |
|---|---|---|
| Email platform (Mailchimp) | Unsubscribe + add to suppression segment | Marketing Operations |
| SMS platform | Opt-out + add to suppression list | Marketing Operations |
| CRM (Salesforce) | Set marketing_opt_out = TRUE, update consent record | CRM Administrator |
| Advertising platforms (Google Ads, Meta Ads) | Remove from customer match and remarketing audiences | Digital Marketing |
| Analytics platform | Exclude from marketing attribution and segment analysis | Data Analytics |
| Data warehouse | Update marketing consent flag, trigger downstream sync | Data Engineering |
| Third-party data brokers | Issue suppression notification | Data Partnerships |
Step 6: Third-Party Notification
- Identify all third parties who process the data subject's data for direct marketing purposes on behalf of Meridian Analytics Ltd (e.g., marketing agencies, advertising platforms, data enrichment providers).
- Send suppression instructions to each third party within 48 hours.
- Request confirmation of suppression within 14 calendar days.
- Log all notifications and confirmations.
Step 7: Confirm to the Data Subject
Send confirmation within 14 calendar days (best practice, well within the 30-day Art. 12 deadline):
- Confirm that all direct marketing processing has ceased.
- Specify the channels suppressed.
- Confirm that a suppression record has been created.
- If any non-marketing processing continues under a different legal basis, inform the data subject.
- Provide contact details for further enquiries.
Step 8: Ongoing Compliance
- Pre-campaign check: Before every marketing campaign, the suppression list must be applied.
- New data imports: All new customer data must be screened against the suppression list before any marketing processing.
- Quarterly audit: Review suppression list completeness and effectiveness. Test that suppressed individuals do not receive marketing communications.
- Staff training: All marketing team members must be trained on the absolute nature of the Art. 21(2) right and the suppression list process.
© 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/marketing-objection 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
Marketing Objection 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 |
|---|---|---|---|---|---|---|
| Marketing Objection this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.1k | 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 | 587 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 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 Marketing Objection
What does Marketing Objection do?
Manages the absolute right to object to direct marketing under GDPR Article 21(2)-(3), covering immediate cessation of all direct marketing processing, suppression list management, cross-channel…. Marketing Objection is an agent skill from mukul975/Privacy-Data-Protection-Skills. Manages the absolute right to object to direct marketing under GDPR Article 21(2)-(3), covering immediate cessation of all direct marketing processing, suppression list management, cross-channel enforcement, and profiling for marketing purposes.
When should I use Marketing Objection?
Marketing Objection fits situations like: tasks that involve Privacy and GDPR.
How do I install Marketing Objection in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill marketing-objection -a claude-code`. Or copy the skill folder (skills/privacy/marketing-objection in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/marketing-objection in your project. Claude Code loads it when a task matches its description.
How do I install Marketing Objection in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill marketing-objection -a codex`. Or copy the skill folder (skills/privacy/marketing-objection in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/marketing-objection in your project. Codex loads it when a task matches its description.
Can I use Marketing Objection 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 marketing-objection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/marketing-objection, .gemini/skills/marketing-objection, .github/skills/marketing-objection and .opencode/skills/marketing-objection in your project.
What does Marketing Objection need to run?
Going by SKILL.md and its folder, Marketing Objection needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Marketing Objection 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 Marketing Objection 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 Marketing Objection use?
Marketing Objection 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 Marketing Objection use?
About 2.1k tokens (SKILL.md is roughly 8.3k 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.3k tokens, read only when the agent opens those files.
What are the alternatives to Marketing Objection?
Skills that share tags, products or a category with Marketing Objection: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 587 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Marketing Objection?
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 301 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.