C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Handles GDPR Article 18 right to restriction of processing requests, covering the four grounds for restriction (accuracy contest, unlawful processing, erasure opposition, legitimate interest…
Install Restriction Of Processing
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill restriction-of-processing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills restriction-of-processing --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/restriction-of-processing .claude/skills/restriction-of-processing && 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 "restriction-of-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/restriction-of-processing into .claude/skills/restriction-of-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "restriction-of-processing", 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/restriction-of-processingType 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 restriction-of-processing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills restriction-of-processing --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/restriction-of-processing .agents/skills/restriction-of-processing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "restriction-of-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/restriction-of-processing into .agents/skills/restriction-of-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "restriction-of-processing", 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 restriction-of-processing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills restriction-of-processing --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/restriction-of-processing .cursor/skills/restriction-of-processing && 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 "restriction-of-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/restriction-of-processing into .cursor/skills/restriction-of-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "restriction-of-processing", 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/restriction-of-processing--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 restriction-of-processing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills restriction-of-processing --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/restriction-of-processing .gemini/skills/restriction-of-processing && 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 "restriction-of-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/restriction-of-processing into .gemini/skills/restriction-of-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "restriction-of-processing", 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 restriction-of-processingInstalls 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 restriction-of-processing -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/restriction-of-processing .github/skills/restriction-of-processing && 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 "restriction-of-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/restriction-of-processing into .github/skills/restriction-of-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "restriction-of-processing", 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 restriction-of-processing -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 restriction-of-processing --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/restriction-of-processing .opencode/skills/restriction-of-processing && 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 "restriction-of-processing" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/restriction-of-processing into .opencode/skills/restriction-of-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "restriction-of-processing", 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
restriction-of-processing- GitHub stars
- 301
- Token cost
- ~2.2k tokens
- SKILL.md length
- 1,086 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 18 right to restriction of processing requests, covering the four grounds for restriction (accuracy contest, unlawful processing, erasure opposition, legitimate interest…
- Works in 7 steps: Receive and Log the Request → Identify the Ground for Restriction → Implement Technical Restriction → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Legal Foundation, Restriction Processing Workflow and Response Timeline
- Runs Python scripts from its folder
What it does
Restriction Of Processing is an agent skill from mukul975/Privacy-Data-Protection-Skills. Handles GDPR Article 18 right to restriction of processing requests, covering the four grounds for restriction (accuracy contest, unlawful processing, erasure opposition, legitimate interest pending), technical flagging mechanisms, and lifting procedures. Activate for restriction request, Art. 18, processing freeze queries.
Its SKILL.md is about 2.2k 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 restriction-of-processing skill to handle GDPR Article 18 right to restriction of processing requests, covering the four grounds for…”
- “/restriction-of-processing”
Requirements
- Python 3
Workflow steps
7 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
Restriction Of Processing loads about 2.2k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 1,086 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,086 words, ~2,153 tokens.
Download SKILL.mdSave it as
.claude/skills/restriction-of-processing/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- restriction-of-processing
- description
- Handles GDPR Article 18 right to restriction of processing requests, covering the four grounds for restriction (accuracy contest, unlawful processing, erasure opposition, legitimate interest pending), technical flagging mechanisms, and lifting procedures. Activate for restriction request, Art. 18, processing freeze queries.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-subject-rights
- metadata.tags
- right-to-restriction, gdpr-article-18, processing-freeze, data-flagging, restriction-of-processing
Handling Right to Restriction Requests
Overview
The right to restriction of processing under GDPR Article 18 allows data subjects to request that a controller limits the processing of their personal data in specific circumstances. When restriction is applied, data may be stored but not otherwise processed without the data subject's consent or for limited specified purposes. This skill provides the complete workflow for assessing, implementing, and managing restriction requests.
Legal Foundation
GDPR Article 18 — Right to Restriction of Processing
Four Grounds for Restriction Under Art. 18(1)
- Art. 18(1)(a) — Accuracy contested: The data subject contests the accuracy of the personal data, for a period enabling the controller to verify the accuracy of the personal data.
- Art. 18(1)(b) — Unlawful processing, erasure opposed: The processing is unlawful and the data subject opposes the erasure of the personal data and requests the restriction of their use instead.
- Art. 18(1)(c) — Erasure opposition for legal claims: The controller no longer needs the personal data for the purposes of the processing, but they are required by the data subject for the establishment, exercise, or defence of legal claims.
- Art. 18(1)(d) — Objection pending verification: The data subject has objected to processing under Art. 21(1) pending the verification whether the legitimate grounds of the controller override those of the data subject.
Processing Permitted During Restriction (Art. 18(2))
When processing has been restricted, the personal data may only be processed:
- With the data subject's consent, OR
- For the establishment, exercise, or defence of legal claims, OR
- For the protection of the rights of another natural or legal person, OR
- For reasons of important public interest of the Union or a Member State.
GDPR Article 19 — Notification Obligation
The controller must notify each recipient to whom the personal data have been disclosed of the restriction, unless this proves impossible or involves disproportionate effort.
Lifting the Restriction (Art. 18(3))
A data subject who has obtained restriction of processing shall be informed by the controller before the restriction of processing is lifted.
Restriction Processing Workflow
Step 1: Receive and Log the Request
- Log the request with reference RST-YYYY-NNNN.
- Record the channel, timestamp (UTC), and identity of the requester.
- Send acknowledgement within 3 business days.
- Verify identity using tiered verification.
Step 2: Identify the Ground for Restriction
Determine which of the four grounds applies:
| Ground | Trigger | Duration | Resolution |
|---|---|---|---|
| Art. 18(1)(a) — Accuracy contested | Data subject disputes data accuracy | Until accuracy verified | Verified accurate: lift restriction. Verified inaccurate: rectify under Art. 16 and lift. |
| Art. 18(1)(b) — Unlawful processing, erasure opposed | Processing found unlawful but subject prefers restriction over deletion | Indefinite until subject consents to erasure or processing becomes lawful | Subject requests erasure or lawful basis established. |
| Art. 18(1)(c) — Needed for legal claims | Controller no longer needs data but subject requires it for legal proceedings | Duration of legal proceedings | Legal proceedings concluded or subject no longer requires data. |
| Art. 18(1)(d) — Objection pending | Subject objects under Art. 21(1), assessment pending | Until Art. 21 assessment complete | Legitimate grounds assessment: controller overrides = lift restriction + inform subject. Subject's grounds prevail = erase under Art. 17(1)(c). |
Step 3: Implement Technical Restriction
Apply a technical flagging mechanism to prevent processing of the restricted data:
Database-Level Flags
- Set a
restriction_flagfield toTRUEon all records associated with the data subject. - Set a
restriction_datetimestamp. - Set a
restriction_groundvalue (one of:accuracy_contested,unlawful_opposed,legal_claims,objection_pending). - Set a
restriction_referencevalue linking to the request (RST-YYYY-NNNN).
Application-Level Controls
- Query filters: Modify application queries to exclude records where
restriction_flag = TRUEfrom all standard processing operations. - API access controls: Return HTTP 423 (Locked) or filtered results when restricted data is requested through APIs used for standard processing.
- Batch processing exclusions: Add restriction checks to all ETL, reporting, and analytics pipelines.
- User interface masking: Display restricted records with a visual indicator (e.g., "RESTRICTED — Processing Limited") in internal tools. Prevent editing or use of restricted data.
Show full SKILL.md (435 more words)Show less
Storage Isolation (Recommended for High-Risk Data)
- Move restricted records to a separate restricted data store or partition.
- Apply access controls limiting access to the DPO and Legal team only.
- Log all access to restricted data with justification.
Step 4: Permitted Processing Assessment
When any team needs to process restricted data, they must complete a permitted processing assessment:
- Consent: Has the data subject provided specific consent for this particular processing activity during the restriction period? Document the consent.
- Legal claims: Is the processing necessary for the establishment, exercise, or defence of legal claims by the controller or a third party? Identify the specific claim.
- Protection of rights: Is the processing necessary to protect the rights of another natural or legal person? Identify the person and right.
- Public interest: Is the processing required for reasons of important public interest? Identify the specific public interest basis.
Any processing of restricted data outside these four purposes is a compliance violation.
Step 5: Notify Third-Party Recipients (Art. 19)
- Identify all recipients to whom the restricted data was previously disclosed.
- Send restriction notification to each recipient:
- Data subject reference (pseudonymised)
- Data categories subject to restriction
- Restriction ground (without disclosing details that would identify the subject's reason)
- Instruction to cease processing except for permitted purposes
- Request confirmation within 14 calendar days
- Log all notifications and confirmations.
Step 6: Monitor and Resolve
- Set a review date based on the restriction ground:
- Accuracy contested: Review within 15 business days (or as long as accuracy verification requires).
- Unlawful processing: Review quarterly or upon data subject request.
- Legal claims: Review upon conclusion of legal proceedings (liaise with Legal team quarterly).
- Objection pending: Complete Art. 21 assessment within 20 business days.
- When the restriction is to be lifted:
- Notify the data subject before lifting (Art. 18(3)) with at least 7 calendar days' notice.
- State the reason the restriction is being lifted.
- Inform the data subject of their rights (including the right to object or request erasure).
- Remove technical flags and restore normal processing access.
- Notify third-party recipients that the restriction has been lifted.
Step 7: Document and Close
- Update the restriction register with:
- Restriction applied date
- Ground
- Technical measures implemented
- Third parties notified
- Resolution date and outcome
- Pre-lifting notification date
- Retain the record for 3 years following resolution.
Response Timeline
- Standard deadline: 30 calendar days from receipt of the request.
- Extension: Up to 60 additional days for complex cases (Art. 12(3)).
- Technical implementation: Restriction flags must be applied within 72 hours of the decision to restrict, regardless of the response deadline.
© 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/restriction-of-processing 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
Restriction Of Processing 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 |
|---|---|---|---|---|---|---|
| Restriction Of Processing this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.2k | 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 Restriction Of Processing
What does Restriction Of Processing do?
Handles GDPR Article 18 right to restriction of processing requests, covering the four grounds for restriction (accuracy contest, unlawful processing, erasure opposition, legitimate interest…. Restriction Of Processing is an agent skill from mukul975/Privacy-Data-Protection-Skills. Handles GDPR Article 18 right to restriction of processing requests, covering the four grounds for restriction (accuracy contest, unlawful processing, erasure opposition, legitimate interest pending), technical flagging mechanisms, and lifting procedures.
When should I use Restriction Of Processing?
Restriction Of Processing fits situations like: tasks that involve Privacy and GDPR.
How do I install Restriction Of Processing in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill restriction-of-processing -a claude-code`. Or copy the skill folder (skills/privacy/restriction-of-processing in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/restriction-of-processing in your project. Claude Code loads it when a task matches its description.
How do I install Restriction Of Processing in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill restriction-of-processing -a codex`. Or copy the skill folder (skills/privacy/restriction-of-processing in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/restriction-of-processing in your project. Codex loads it when a task matches its description.
Can I use Restriction Of Processing 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 restriction-of-processing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/restriction-of-processing, .gemini/skills/restriction-of-processing, .github/skills/restriction-of-processing and .opencode/skills/restriction-of-processing in your project.
What does Restriction Of Processing need to run?
Going by SKILL.md and its folder, Restriction Of Processing needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Restriction Of Processing 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 Restriction Of Processing 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 Restriction Of Processing use?
Restriction Of Processing 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 Restriction Of Processing use?
About 2.2k tokens (SKILL.md is roughly 8.6k 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.7k tokens, read only when the agent opens those files.
What are the alternatives to Restriction Of Processing?
Skills that share tags, products or a category with Restriction Of Processing: 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 Restriction Of Processing?
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.