C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Builds a multi-channel DSAR intake system supporting web form, email, phone, and in-person requests with identity verification tiers, automated routing logic, SLA tracking, and response generation.
Install Dsar Intake System
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill dsar-intake-system -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills dsar-intake-system --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/dsar-intake-system .claude/skills/dsar-intake-system && 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 "dsar-intake-system" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/dsar-intake-system into .claude/skills/dsar-intake-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsar-intake-system", 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/dsar-intake-systemType 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 dsar-intake-system -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills dsar-intake-system --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/dsar-intake-system .agents/skills/dsar-intake-system && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dsar-intake-system" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/dsar-intake-system into .agents/skills/dsar-intake-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsar-intake-system", 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 dsar-intake-system -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills dsar-intake-system --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/dsar-intake-system .cursor/skills/dsar-intake-system && 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 "dsar-intake-system" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/dsar-intake-system into .cursor/skills/dsar-intake-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsar-intake-system", 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/dsar-intake-system--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 dsar-intake-system -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills dsar-intake-system --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/dsar-intake-system .gemini/skills/dsar-intake-system && 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 "dsar-intake-system" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/dsar-intake-system into .gemini/skills/dsar-intake-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsar-intake-system", 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 dsar-intake-systemInstalls 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 dsar-intake-system -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/dsar-intake-system .github/skills/dsar-intake-system && 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 "dsar-intake-system" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/dsar-intake-system into .github/skills/dsar-intake-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsar-intake-system", 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 dsar-intake-system -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 dsar-intake-system --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/dsar-intake-system .opencode/skills/dsar-intake-system && 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 "dsar-intake-system" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/dsar-intake-system into .opencode/skills/dsar-intake-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsar-intake-system", 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
dsar-intake-system- GitHub stars
- 297
- Token cost
- ~2.4k tokens
- SKILL.md length
- 952 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Builds a multi-channel DSAR intake system supporting web form, email, phone, and in-person requests with identity verification tiers, automated routing logic, SLA tracking, and response generation.
- Works in 3 steps: Request type (extracted from web form… → Complexity assessment → Jurisdiction detection
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, System Architecture, Identity Verification Framework and Routing Logic, plus 2 more sections
- Runs Python scripts from its folder
What it does
Dsar Intake System is an agent skill from mukul975/Privacy-Data-Protection-Skills. Builds a multi-channel DSAR intake system supporting web form, email, phone, and in-person requests with identity verification tiers, automated routing logic, SLA tracking, and response generation. Activate for DSAR intake, rights request portal, multi-channel intake, SLA tracking, request management queries.
Its SKILL.md is about 2.4k 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 dsar-intake-system skill to build a multi-channel DSAR intake system supporting web form, email, phone, and in-person requests with identity…”
- “/dsar-intake-system”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Request type (extracted from web form selection or email keywords)
- Complexity assessment
- Jurisdiction detection
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
Dsar Intake System loads about 2.4k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 952 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). 952 words, ~2,365 tokens.
Download SKILL.mdSave it as
.claude/skills/dsar-intake-system/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- dsar-intake-system
- description
- Builds a multi-channel DSAR intake system supporting web form, email, phone, and in-person requests with identity verification tiers, automated routing logic, SLA tracking, and response generation. Activate for DSAR intake, rights request portal, multi-channel intake, SLA tracking, request management queries.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-subject-rights
- metadata.tags
- dsar-intake, multi-channel, identity-verification, sla-tracking, request-management
Building a Universal DSAR Intake System
Overview
A universal DSAR intake system centralises the receipt, verification, routing, and tracking of all data subject rights requests across multiple channels. This skill provides the architectural design, identity verification framework, routing logic, SLA management, and response generation capabilities needed to operate a compliant and efficient rights request management programme.
System Architecture
Multi-Channel Intake
The intake system must accept requests from all channels through which data subjects may contact the organisation:
| Channel | Intake Method | Processing |
|---|---|---|
| Web form | Dedicated privacy rights portal at meridiananalytics.co.uk/privacy/rights | Automated capture, structured data, immediate acknowledgement |
| dsar@meridiananalytics.co.uk (dedicated monitored inbox) | Semi-automated: email parser extracts key fields, manual triage | |
| Telephone | Privacy hotline: +44 20 7946 0958 (staffed Mon-Fri 09:00-17:00 GMT) | Agent-assisted: agent completes intake form during call |
| Postal mail | Data Protection Office, 47 Canary Wharf Tower, London E14 5AB | Manual: scanned, digitised, entered into system within 2 business days |
| In-person | Reception desk at registered office | Agent-assisted: staff member completes intake form |
| Social media | Direct messages on official channels | Redirect to formal channel; do not process rights requests via social media |
Central Request Register
All requests from all channels feed into a single central register with the following record structure:
| Field | Description |
|---|---|
| Reference | Auto-generated: [TYPE]-YYYY-NNNN (e.g., DSAR-2026-0142) |
| Receipt date | UTC timestamp of initial receipt |
| Channel | Source channel |
| Request type | Access (Art. 15), Erasure (Art. 17), Portability (Art. 20), Restriction (Art. 18), Rectification (Art. 16), Object (Art. 21), Marketing opt-out (Art. 21(2)), Automated decision (Art. 22), CCPA know, CCPA delete, CCPA opt-out |
| Data subject name | As provided by requester |
| Data subject identifiers | Email, account number, other identifiers provided |
| Verification status | Pending / Verified / Failed |
| Verification tier | Low / Medium / High |
| Assignee | Privacy team member responsible |
| Priority | Standard / Complex / Urgent |
| Status | Received / Acknowledged / Verifying / Processing / QA Review / Delivered / Closed |
| Deadline | Calculated response deadline |
| Extension | Whether extension has been applied |
| Notes | Free text for processing notes |
Identity Verification Framework
Tiered Verification
| Tier | When Applied | Requirements | Clock Behaviour |
|---|---|---|---|
| Tier 1 — Low Risk | Request from authenticated account (logged-in portal, verified email) | Confirm account ownership via existing authentication | Clock starts immediately |
| Tier 2 — Medium Risk | Request from known email address (matches records) but not authenticated | Provide 2 of: date of birth, account number, postal code, last 4 digits of payment method | Clock starts on verification |
| Tier 3 — High Risk | Request from unknown channel, or request on behalf of another person | Government-issued photo ID + one additional identifier. Third-party requests: signed authorisation from data subject + ID for both | Clock starts on verification |
Verification Workflow
[Request Received]
│
▼
[Determine Verification Tier]
│
├── Authenticated channel? ──► Tier 1 (auto-verified)
├── Known identifier matches? ──► Tier 2 (request 2 data points)
└── Unknown channel / third party? ──► Tier 3 (request ID + authorisation)
│
▼
[Verification Request Sent (within 3 business days)]
│
▼
[Verification Response Received?]
├── Yes ──► [Data Points Match?]
│ ├── Yes ──► Mark Verified, start clock
│ └── No ──► Request additional info (one retry)
│ ├── Second attempt matches ──► Verified
│ └── Second attempt fails ──► Close as Unverified
│
└── No response (30 days) ──► Close as AbandonedRouting Logic
Automated Request Classification
Upon intake, the system classifies and routes requests based on:
Request type (extracted from web form selection or email keywords):
- Access/DSAR → DSAR team
- Erasure/Deletion → Erasure team
- Portability/Export → Portability team
- Marketing opt-out → Marketing Operations (immediate processing)
- CCPA requests → US Privacy team
- Regulatory complaint → DPO + Legal
Complexity assessment:
- Standard: single request type, single jurisdiction, < 5 data systems
- Complex: multiple request types, cross-border, > 5 data systems, or involving exemptions
- Urgent: regulatory enquiry, legal deadline, or data subject facing imminent harm
Jurisdiction detection:
- UK/EU data subject → GDPR workflow (30-day deadline)
- California resident → CCPA workflow (45-day deadline)
- Other US state → Applicable state privacy law workflow
- Other jurisdiction → Assess applicable law, default to GDPR standard
Show full SKILL.md (423 more words)Show less
Routing Matrix
| Request Type | Assignee | Priority | SLA |
|---|---|---|---|
| DSAR (Art. 15) — Standard | Privacy Analyst | Standard | 30 days |
| DSAR (Art. 15) — Complex | Senior Privacy Analyst | Complex | 30 days (extendable to 90) |
| Erasure (Art. 17) | Privacy Analyst | Standard | 30 days |
| Portability (Art. 20) | Data Engineer + Privacy Analyst | Standard | 30 days |
| Rectification (Art. 16) | Privacy Analyst | Standard | 30 days |
| Restriction (Art. 18) | Senior Privacy Analyst | Standard | 30 days + 72h implementation |
| Object (Art. 21) | DPO | Complex | 30 days + immediate cessation |
| Marketing opt-out (Art. 21(2)) | Marketing Operations | Urgent | 24 hours |
| Automated decision (Art. 22) | DPO + Technical Lead | Complex | 30 days |
| CCPA Know | Privacy Analyst | Standard | 45 days |
| CCPA Delete | Privacy Analyst | Standard | 45 days |
| CCPA Opt-Out | Marketing Operations | Urgent | 15 business days |
| Regulatory complaint | DPO + General Counsel | Urgent | Per DPA deadline |
SLA Tracking
Dashboard Metrics
| Metric | Target | Measurement |
|---|---|---|
| Acknowledgement within 3 business days | 100% | (Acknowledged requests / Total requests) within 3 business days |
| Response within statutory deadline | 100% | (On-time responses / Total responses) |
| Average response time | < 20 calendar days | Sum of response days / Number of completed requests |
| Verification completion rate | > 95% | (Verified requests / Total requests requiring verification) |
| Extension rate | < 15% | (Extended requests / Total requests) |
| First-contact resolution (marketing opt-out) | 100% within 24h | (Resolved within 24h / Total marketing opt-outs) |
Escalation Rules
| Condition | Escalation |
|---|---|
| 20 days elapsed, response not delivered | Alert to assignee and team lead |
| 25 days elapsed, response not delivered | Alert to DPO |
| 28 days elapsed, response not delivered | Alert to DPO + General Counsel (emergency priority) |
| Extension notification not sent by day 28 | Alert to DPO (compliance risk) |
| Verification pending > 14 days | Alert to assignee (follow up with data subject) |
Response Generation
Automated Response Components
The system generates responses by assembling modular components:
- Cover letter: Standard header, addressee, reference number, opening paragraph.
- Right-specific content: Template paragraph for each right type.
- Data compilation: System-generated data extract (for access requests).
- Supplementary information: Art. 15(1)(a)-(h) information block (for access requests).
- Redaction log: Automatically generated from redaction flags (for access requests with exemptions).
- Third-party notification log: Recipients notified under Art. 19 (for erasure/rectification/restriction).
- Rights information: Standard block listing the data subject's other rights and complaint mechanisms.
- Sign-off: DPO name and contact details.
Quality Assurance Checklist
Before any response is sent, the QA reviewer verifies:
- Response addresses all elements of the relevant GDPR article
- Data extract is complete (all identified systems queried)
- Redactions are legally justified and documented
- Response deadline has been met (or extension properly communicated)
- Response is in clear, plain language per Art. 12
- Delivery method is secure (encryption, secure portal, or registered post)
- DPO sign-off obtained
© 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/dsar-intake-system 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
Dsar Intake System 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 |
|---|---|---|---|---|---|---|
| Dsar Intake System this skillmukul975/Privacy-Data-Protection-Skills | 297 | — | ~2.4k | 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 Dsar Intake System
What does Dsar Intake System do?
Builds a multi-channel DSAR intake system supporting web form, email, phone, and in-person requests with identity verification tiers, automated routing logic, SLA tracking, and response generation. Dsar Intake System is an agent skill from mukul975/Privacy-Data-Protection-Skills. Builds a multi-channel DSAR intake system supporting web form, email, phone, and in-person requests with identity verification tiers, automated routing logic, SLA tracking, and response generation.
When should I use Dsar Intake System?
Dsar Intake System fits situations like: tasks that involve Privacy and GDPR.
How do I install Dsar Intake System in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill dsar-intake-system -a claude-code`. Or copy the skill folder (skills/privacy/dsar-intake-system in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/dsar-intake-system in your project. Claude Code loads it when a task matches its description.
How do I install Dsar Intake System in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill dsar-intake-system -a codex`. Or copy the skill folder (skills/privacy/dsar-intake-system in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/dsar-intake-system in your project. Codex loads it when a task matches its description.
Can I use Dsar Intake System 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 dsar-intake-system -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dsar-intake-system, .gemini/skills/dsar-intake-system, .github/skills/dsar-intake-system and .opencode/skills/dsar-intake-system in your project.
What does Dsar Intake System need to run?
Going by SKILL.md and its folder, Dsar Intake System needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Dsar Intake System 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 Dsar Intake System 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 Dsar Intake System use?
Dsar Intake System 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 Dsar Intake System use?
About 2.4k tokens (SKILL.md is roughly 9.5k 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.9k tokens, read only when the agent opens those files.
What are the alternatives to Dsar Intake System?
Skills that share tags, products or a category with Dsar Intake System: 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 Dsar Intake System?
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.