C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Texas Data Privacy and Security Act (TDPSA) compliance. An agent skill from mukul975/Privacy-Data-Protection-Skills.
Install Texas Tdpsa Compliance
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill texas-tdpsa-compliance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills texas-tdpsa-compliance --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/texas-tdpsa-compliance .claude/skills/texas-tdpsa-compliance && 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 "texas-tdpsa-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/texas-tdpsa-compliance into .claude/skills/texas-tdpsa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "texas-tdpsa-compliance", 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/texas-tdpsa-complianceType 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 texas-tdpsa-compliance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills texas-tdpsa-compliance --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/texas-tdpsa-compliance .agents/skills/texas-tdpsa-compliance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "texas-tdpsa-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/texas-tdpsa-compliance into .agents/skills/texas-tdpsa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "texas-tdpsa-compliance", 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 texas-tdpsa-compliance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills texas-tdpsa-compliance --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/texas-tdpsa-compliance .cursor/skills/texas-tdpsa-compliance && 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 "texas-tdpsa-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/texas-tdpsa-compliance into .cursor/skills/texas-tdpsa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "texas-tdpsa-compliance", 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/texas-tdpsa-compliance--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 texas-tdpsa-compliance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills texas-tdpsa-compliance --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/texas-tdpsa-compliance .gemini/skills/texas-tdpsa-compliance && 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 "texas-tdpsa-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/texas-tdpsa-compliance into .gemini/skills/texas-tdpsa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "texas-tdpsa-compliance", 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 texas-tdpsa-complianceInstalls 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 texas-tdpsa-compliance -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/texas-tdpsa-compliance .github/skills/texas-tdpsa-compliance && 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 "texas-tdpsa-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/texas-tdpsa-compliance into .github/skills/texas-tdpsa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "texas-tdpsa-compliance", 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 texas-tdpsa-compliance -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 texas-tdpsa-compliance --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/texas-tdpsa-compliance .opencode/skills/texas-tdpsa-compliance && 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 "texas-tdpsa-compliance" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/texas-tdpsa-compliance into .opencode/skills/texas-tdpsa-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "texas-tdpsa-compliance", 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
texas-tdpsa-compliance- GitHub stars
- 301
- Token cost
- ~2k tokens
- SKILL.md length
- 989 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Texas Data Privacy and Security Act (TDPSA) compliance. An agent skill from mukul975/Privacy-Data-Protection-Skills.
- Works in 3 steps: Conducts business in Texas or produces a… → Processes or engages in the sale of… → Is not a small business as defined by…
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Applicability (§541.002), Consumer Rights (§541.051) and Sensitive Data (§541.001(29),…, plus 5 more sections
- Runs Python scripts from its folder
What it does
Texas Tdpsa Compliance is an agent skill from mukul975/Privacy-Data-Protection-Skills. Texas Data Privacy and Security Act (TDPSA) compliance. No revenue threshold applies to all businesses. Covers data broker registration requirements, biometric identifier provisions under CUBI, consumer rights, AG enforcement, and 30-day cure period. Effective July 1, 2024.
Its SKILL.md is about 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 texas-tdpsa-compliance skill to texa Data Privacy and Security Act (TDPSA) compliance. An agent skill from…”
- “/texas-tdpsa-compliance”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Conducts business in Texas or produces a product or service consumed by Texas residents
- Processes or engages in the sale of personal data
- Is not a small business as defined by the U.S. Small Business Administration (SBA)
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
Texas Tdpsa Compliance loads about 2k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 74 tokens; SKILL.md has 989 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). 989 words, ~1,997 tokens.
Download SKILL.mdSave it as
.claude/skills/texas-tdpsa-compliance/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- texas-tdpsa-compliance
- description
- Texas Data Privacy and Security Act (TDPSA) compliance. No revenue threshold applies to all businesses. Covers data broker registration requirements, biometric identifier provisions under CUBI, consumer rights, AG enforcement, and 30-day cure period. Effective July 1, 2024.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- us-state-privacy-laws
- metadata.tags
- tdpsa, texas-privacy, data-broker, biometric, no-revenue-threshold
Texas Data Privacy and Security Act (TDPSA)
Overview
The Texas Data Privacy and Security Act (TDPSA), codified as Tex. Bus. & Com. Code §541.001 through §541.203, was signed into law on June 18, 2023 (HB 4), and became effective July 1, 2024. Texas is the largest state by population to enact comprehensive consumer privacy legislation and is notable for having no revenue threshold for applicability — the TDPSA applies to any person that conducts business in Texas or produces products or services consumed by Texas residents, regardless of company size.
The TDPSA also interacts with the existing Texas Capture or Use of Biometric Identifier Act (CUBI), Tex. Bus. & Com. Code §503.001, which provides separate biometric data protections.
Applicability (§541.002)
The TDPSA applies to a person that:
- Conducts business in Texas or produces a product or service consumed by Texas residents
- Processes or engages in the sale of personal data
- Is not a small business as defined by the U.S. Small Business Administration (SBA)
Key feature: No revenue or consumer count threshold. Unlike California ($25M revenue), Virginia (100,000 consumers), or Colorado (100,000 consumers), the TDPSA applies broadly to any non-small business processing personal data of Texas residents.
Small business exemption: Small businesses as defined by SBA size standards are exempt from most provisions but are NOT exempt from the prohibition on selling sensitive data without consent (§541.107(b)).
Additional exemptions (§541.003):
- State agencies and political subdivisions
- Financial institutions subject to GLBA (entity-level)
- Covered entities and business associates under HIPAA (entity-level)
- Nonprofit organizations
- Institutions of higher education
- Electric utilities (ERCOT-related)
Liberty Commerce Inc. Assessment: Liberty Commerce Inc. is not an SBA-defined small business (annual revenue: $48M, 320 employees). It conducts business in Texas and processes personal data of Texas residents. The TDPSA applies.
Consumer Rights (§541.051)
Five Consumer Rights
- Right to Access (§541.051(1)): Confirm processing and access personal data
- Right to Correct (§541.051(2)): Correct inaccuracies
- Right to Delete (§541.051(3)): Delete personal data
- Right to Portability (§541.051(4)): Obtain data in portable, readily usable format
- Right to Opt Out (§541.051(5)): Opt out of:
- Targeted advertising
- Sale of personal data
- Profiling in furtherance of decisions producing legal or similarly significant effects
Response Requirements (§541.055)
- Respond within 45 days
- Extension: up to 45 additional days with notice
- At least one free response per 12 months per right
- Appeal process: respond within 60 days
Sensitive Data (§541.001(29), §541.101(b)(5))
Categories
- Racial or ethnic origin
- Religious beliefs
- Mental or physical health diagnosis
- Sexual orientation
- Citizenship or immigration status
- Genetic or biometric data processed for identification
- Personal data of a known child
- Precise geolocation data
Consent Requirements
Processing sensitive data requires opt-in consent. For small businesses: selling sensitive data without consent is prohibited regardless of SBA size.
Data Broker Provisions (§541.201-§541.203)
The TDPSA includes specific data broker requirements:
Definition (§541.201)
A "data broker" is a business entity whose principal source of revenue is derived from collecting, processing, or transferring personal data the entity did not directly collect from consumers.
Registration Requirement (§541.202)
Data brokers must register with the Texas Secretary of State and pay a registration fee. Registration must include:
- Legal name and primary business address
- Contact information for privacy inquiries
- Description of data collection practices
- Whether the broker has experienced a data breach in the preceding 3 years
Consumer Rights for Data Brokers (§541.203)
Data brokers must provide:
- Clear and conspicuous disclosure that they are a data broker
- A mechanism for consumers to opt out of data collection
- Instructions for submitting access and deletion requests
Liberty Commerce Inc. Assessment: Liberty Commerce Inc. is not a data broker — its principal revenue derives from e-commerce, not from collecting/processing/transferring personal data. The data broker provisions do not apply.
Show full SKILL.md (370 more words)Show less
Biometric Data: CUBI Interaction
Texas Capture or Use of Biometric Identifier Act (CUBI) — Tex. Bus. & Com. Code §503.001
CUBI, enacted in 2009, provides additional protections for biometric identifiers:
- Defines biometric identifier: retina or iris scan, fingerprint, voiceprint, record of hand or face geometry
- Requires informed consent before capture
- Prohibits sale, lease, or disclosure without consent
- Requires reasonable care in storage, transmission, and protection
- Requires destruction within a reasonable time (when purpose fulfilled or within 3 years of last interaction)
- No private right of action — AG enforcement only
- Penalties: Up to $25,000 per violation
Liberty Commerce Inc. Implementation: Liberty Commerce Inc. does not capture biometric identifiers from Texas consumers. Device-side biometric authentication (Face ID, fingerprint) processes locally and does not transmit biometric data to Liberty Commerce Inc. servers.
Controller Obligations (§541.101)
- Purpose limitation (§541.101(a)(1)): Limit processing to adequate, relevant, and reasonably necessary purposes
- Data minimization (§541.101(a)(2)): Do not process beyond what is reasonably necessary
- Data security (§541.101(a)(3)): Appropriate technical and organizational measures
- Non-discrimination (§541.101(a)(4)): No processing in violation of antidiscrimination laws
- Sensitive data consent (§541.101(b)(5)): Obtain consent before processing
Privacy Notice (§541.101(b))
Must include:
- Categories of personal data processed
- Purposes for processing
- Consumer rights exercise instructions
- Categories shared with third parties
- Categories of third parties
- Contact information
Data Protection Assessments (§541.103)
Required for:
- Targeted advertising
- Sale of personal data
- Profiling with legal or significant effects
- Sensitive data processing
- High-risk processing activities
Enforcement (§541.151-§541.155)
Attorney General Authority
- Exclusive enforcement — no private right of action (except CUBI has AG enforcement only)
- May investigate and bring action under the Deceptive Trade Practices — Consumer Protection Act (Tex. Bus. & Com. Code §17.41 et seq.)
30-Day Cure Period (§541.154)
- AG must provide 30-day written notice of alleged violation
- If cured within 30 days and express written statement of cure provided: AG may not bring action
- Unlike CPRA: Cure period is permanent, not sunsetting
Penalties
- Civil penalties up to $7,500 per violation
- Injunctive relief
- Reasonable attorney fees and investigation costs
Key Regulatory References
- Tex. Bus. & Com. Code §541.001-§541.203 (TDPSA)
- Tex. Bus. & Com. Code §503.001 (CUBI — biometric identifiers)
- Tex. Bus. & Com. Code §17.41 et seq. (DTPA — enforcement framework)
- SBA Size Standards (13 CFR §121.201) — small business determination
- Texas Secretary of State — Data broker registration
© 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/texas-tdpsa-compliance 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
Texas Tdpsa Compliance 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 |
|---|---|---|---|---|---|---|
| Texas Tdpsa Compliance this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~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 Texas Tdpsa Compliance
What does Texas Tdpsa Compliance do?
Texas Data Privacy and Security Act (TDPSA) compliance. An agent skill from mukul975/Privacy-Data-Protection-Skills. Texas Tdpsa Compliance is an agent skill from mukul975/Privacy-Data-Protection-Skills. Texas Data Privacy and Security Act (TDPSA) compliance.
When should I use Texas Tdpsa Compliance?
Texas Tdpsa Compliance fits situations like: tasks that involve Privacy and GDPR.
How do I install Texas Tdpsa Compliance in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill texas-tdpsa-compliance -a claude-code`. Or copy the skill folder (skills/privacy/texas-tdpsa-compliance in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/texas-tdpsa-compliance in your project. Claude Code loads it when a task matches its description.
How do I install Texas Tdpsa Compliance in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill texas-tdpsa-compliance -a codex`. Or copy the skill folder (skills/privacy/texas-tdpsa-compliance in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/texas-tdpsa-compliance in your project. Codex loads it when a task matches its description.
Can I use Texas Tdpsa Compliance 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 texas-tdpsa-compliance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/texas-tdpsa-compliance, .gemini/skills/texas-tdpsa-compliance, .github/skills/texas-tdpsa-compliance and .opencode/skills/texas-tdpsa-compliance in your project.
What does Texas Tdpsa Compliance need to run?
Going by SKILL.md and its folder, Texas Tdpsa Compliance needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Texas Tdpsa Compliance 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 Texas Tdpsa Compliance 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 Texas Tdpsa Compliance use?
Texas Tdpsa Compliance 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 Texas Tdpsa Compliance use?
About 2k tokens (SKILL.md is roughly 8k 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 Texas Tdpsa Compliance?
Skills that share tags, products or a category with Texas Tdpsa Compliance: 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 Texas Tdpsa Compliance?
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.