C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Guide for managing consent for scientific research under GDPR Article 89 and Recital 33 broad consent provisions.
Install Managing Consent For Research
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-consent-for-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills managing-consent-for-research --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/managing-consent-for-research .claude/skills/managing-consent-for-research && 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 "managing-consent-for-research" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-consent-for-research into .claude/skills/managing-consent-for-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-consent-for-research", 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/managing-consent-for-researchType 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 managing-consent-for-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills managing-consent-for-research --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/managing-consent-for-research .agents/skills/managing-consent-for-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "managing-consent-for-research" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-consent-for-research into .agents/skills/managing-consent-for-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-consent-for-research", 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 managing-consent-for-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills managing-consent-for-research --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/managing-consent-for-research .cursor/skills/managing-consent-for-research && 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 "managing-consent-for-research" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-consent-for-research into .cursor/skills/managing-consent-for-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-consent-for-research", 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/managing-consent-for-research--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 managing-consent-for-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills managing-consent-for-research --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/managing-consent-for-research .gemini/skills/managing-consent-for-research && 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 "managing-consent-for-research" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-consent-for-research into .gemini/skills/managing-consent-for-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-consent-for-research", 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 managing-consent-for-researchInstalls 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 managing-consent-for-research -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/managing-consent-for-research .github/skills/managing-consent-for-research && 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 "managing-consent-for-research" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-consent-for-research into .github/skills/managing-consent-for-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-consent-for-research", 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 managing-consent-for-research -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 managing-consent-for-research --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/managing-consent-for-research .opencode/skills/managing-consent-for-research && 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 "managing-consent-for-research" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/managing-consent-for-research into .opencode/skills/managing-consent-for-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "managing-consent-for-research", 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
managing-consent-for-research- GitHub stars
- 301
- Token cost
- ~1.9k tokens
- SKILL.md length
- 721 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guide for managing consent for scientific research under GDPR Article 89 and Recital 33 broad consent provisions.
- Works in 5 steps: Research Area Defined: The consent must… → Ethical Standards Met: The research must… → Safeguards Implemented: Article 89(1)… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Broad Consent Under Recital 33, Ethical Review Board… and Purpose Evolution Management, plus 2 more sections
- Runs Python scripts from its folder
What it does
Managing Consent For Research is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guide for managing consent for scientific research under GDPR Article 89 and Recital 33 broad consent provisions. Covers ethical review board coordination, purpose evolution management, appropriate safeguards including pseudonymization, and the interplay between consent and other lawful bases for research processing.
Its SKILL.md is about 1.9k 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
- “/managing-consent-for-research”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Research Area Defined: The consent must specify a recognizable area of scientific research (e.g., "genomic research into rare diseases,"…
- Ethical Standards Met: The research must follow recognized ethical standards, typically verified through an ethics review board/IRB
- Safeguards Implemented: Article 89(1) safeguards must be in place (pseudonymization, data minimization, access controls)
- Transparency: The data subject must still be informed about the general scope and nature of the research
- Withdrawal: The right to withdraw consent remains (Article 7(3)), though Article 89(2) allows Member States to provide derogations
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
Managing Consent For Research loads about 1.9k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 721 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). 721 words, ~1,913 tokens.
Download SKILL.mdSave it as
.claude/skills/managing-consent-for-research/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- managing-consent-for-research
- description
- Guide for managing consent for scientific research under GDPR Article 89 and Recital 33 broad consent provisions. Covers ethical review board coordination, purpose evolution management, appropriate safeguards including pseudonymization, and the interplay between consent and other lawful bases for research processing.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- consent-management
- metadata.tags
- research-consent, article-89, broad-consent, recital-33, scientific-research
Managing Consent for Research
Overview
GDPR Recital 33 acknowledges that "it is often not possible to fully identify the purpose of personal data processing for scientific research purposes at the time of data collection." It therefore permits a degree of flexibility, allowing data subjects to give consent to "certain areas of scientific research when in keeping with recognised ethical standards for scientific research." This is known as "broad consent" and represents a significant departure from the standard specificity requirement.
Article 89(1) requires that processing for scientific research purposes be subject to appropriate safeguards, including technical and organizational measures to ensure respect for the principle of data minimization, such as pseudonymization.
Broad Consent Under Recital 33
What Broad Consent Allows
- Consent to a defined area of research rather than a specific study
- Consent that accommodates purpose evolution within the research area
- Consent that covers secondary use of data for compatible research
Conditions for Valid Broad Consent
- Research Area Defined: The consent must specify a recognizable area of scientific research (e.g., "genomic research into rare diseases," "cloud computing performance optimization research")
- Ethical Standards Met: The research must follow recognized ethical standards, typically verified through an ethics review board/IRB
- Safeguards Implemented: Article 89(1) safeguards must be in place (pseudonymization, data minimization, access controls)
- Transparency: The data subject must still be informed about the general scope and nature of the research
- Withdrawal: The right to withdraw consent remains (Article 7(3)), though Article 89(2) allows Member States to provide derogations
CloudVault SaaS Inc. Research Program
CloudVault SaaS Inc. operates a research program studying cloud storage usage patterns, file system optimization, and data management behaviors. The program:
- Publishes results in peer-reviewed journals and at ACM/IEEE conferences
- Partners with Trinity College Dublin Computer Science department
- Is overseen by the CloudVault Research Ethics Committee
- Processes pseudonymized usage data from consenting users
Research Consent Statement (displayed to users):
"I consent to CloudVault SaaS Inc. using my pseudonymized usage data (file sizes, types, access patterns, storage behaviors — not file contents) for scientific research into cloud storage optimization, file system design, and data management. Research results may be published in academic journals. My data will be pseudonymized before any research use. I can withdraw this consent at any time in Settings > Privacy, though this will not affect the validity of research already conducted with my data."
Ethical Review Board Coordination
Ethics Review Workflow
TRIGGER: New research project proposed using user data
│
├─► Step 1: Principal Investigator submits research proposal
│ ├─ Research question and methodology
│ ├─ Data requirements (what personal data, how much, from whom)
│ ├─ Lawful basis analysis (consent and/or Art. 89 legitimate interest)
│ ├─ Privacy impact assessment summary
│ └─ Safeguards (pseudonymization method, access controls, retention)
│
├─► Step 2: CloudVault Research Ethics Committee review
│ ├─ Does the research fall within the "broad consent" area?
│ ├─ Are the safeguards adequate per Article 89(1)?
│ ├─ Is the data minimized to what is necessary?
│ ├─ Are the results intended for genuine scientific research?
│ └─ Would a reasonable data subject expect this use?
│
├─► Step 3: DPO consultation
│ ├─ Lawful basis confirmation
│ ├─ DPIA review (required if processing involves profiling or large-scale data)
│ └─ Safeguard adequacy sign-off
│
├─► Step 4: Ethics Committee decision
│ ├─ APPROVED: Research may proceed with specified data and safeguards
│ ├─ APPROVED WITH CONDITIONS: Additional safeguards or data minimization required
│ └─ REJECTED: Research does not meet ethical or legal standards
│
└─► Step 5: Ongoing compliance monitoring
├─ Annual ethics review for multi-year research projects
├─ Data access audit (who accessed research data and when)
└─ Publication review to ensure no re-identification riskPurpose Evolution Management
When research questions evolve beyond the original broad consent scope:
Compatible Evolution (No New Consent Required)
- Refining the research question within the same area
- Using different analytical methods on the same data
- Combining datasets already covered by the broad consent
- Extending the research timeline (with ethics committee approval)
Show full SKILL.md (273 more words)Show less
Incompatible Evolution (New Consent Required)
- Expanding to a fundamentally different research area
- Sharing data with a new research partner not covered by original consent
- Using data for commercial product development (not scientific research)
- Linking research data with new data sources not covered by consent
Assessment Framework
| Factor | Compatible | Incompatible |
|---|---|---|
| Same research area? | Yes | No |
| Same data categories? | Yes or subset | New categories needed |
| Same safeguards? | Maintained or enhanced | Weakened |
| Ethics committee approved? | Yes | Not yet or rejected |
| Reasonable expectation of data subjects? | Yes | Questionable |
Article 89(1) Safeguards
Required technical and organizational measures:
- Pseudonymization: Replace direct identifiers with pseudonyms. Store the key separately with strict access controls.
- Data Minimization: Extract only the fields needed for the specific research question. Aggregate where possible.
- Access Controls: Research data accessible only to authorized researchers through a secure research environment.
- Retention Limitation: Research datasets retained only for the duration of the study plus a reasonable verification period (typically 5-10 years for reproducibility per journal requirements).
- No Re-Identification: Technical measures to prevent re-identification. k-anonymity threshold of at least k=5 for published datasets.
- Audit Trail: Log all access to research data with researcher identity, timestamp, and purpose.
Key Regulatory References
- GDPR Article 89(1) — Safeguards for scientific research processing
- GDPR Article 89(2) — Member State derogations for research (rights restrictions)
- GDPR Recital 33 — Broad consent for scientific research
- GDPR Recital 159 — Definition of scientific research (broad interpretation)
- EDPB Guidelines on Research (under development as of 2025)
- Declaration of Helsinki (WMA, 2013 revision) — Ethical principles for medical research
- Council of Europe Recommendation CM/Rec(2019)2 — Protection of health-related data
- Regulation (EU) 2024/1689 (AI Act) — Research exemptions for AI systems
© 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/managing-consent-for-research 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
Managing Consent For Research 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 |
|---|---|---|---|---|---|---|
| Managing Consent For Research this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~1.9k | 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 Managing Consent For Research
What does Managing Consent For Research do?
Guide for managing consent for scientific research under GDPR Article 89 and Recital 33 broad consent provisions. Managing Consent For Research is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guide for managing consent for scientific research under GDPR Article 89 and Recital 33 broad consent provisions.
When should I use Managing Consent For Research?
Managing Consent For Research fits situations like: tasks that involve Privacy and GDPR.
How do I install Managing Consent For Research in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-consent-for-research -a claude-code`. Or copy the skill folder (skills/privacy/managing-consent-for-research in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/managing-consent-for-research in your project. Claude Code loads it when a task matches its description.
How do I install Managing Consent For Research in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-consent-for-research -a codex`. Or copy the skill folder (skills/privacy/managing-consent-for-research in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/managing-consent-for-research in your project. Codex loads it when a task matches its description.
Can I use Managing Consent For Research 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 managing-consent-for-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managing-consent-for-research, .gemini/skills/managing-consent-for-research, .github/skills/managing-consent-for-research and .opencode/skills/managing-consent-for-research in your project.
What does Managing Consent For Research need to run?
Going by SKILL.md and its folder, Managing Consent For Research needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Managing Consent For Research 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 Managing Consent For Research 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 Managing Consent For Research use?
Managing Consent For Research 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 Managing Consent For Research use?
About 1.9k tokens (SKILL.md is roughly 7.7k 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 2.4k tokens, read only when the agent opens those files.
What are the alternatives to Managing Consent For Research?
Skills that share tags, products or a category with Managing Consent For Research: 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 Managing Consent For Research?
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.