Agent skill

Cloud Retention Config

by mukul975 in mukul975/Privacy-Data-Protection-Skills

Configures cloud storage retention policies across AWS S3, Azure Blob Storage, and Google Cloud Storage.

Apache-2.0Auto-check passedLegal & Compliance

Install Cloud Retention Config

skills CLI
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill cloud-retention-config -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Privacy-Data-Protection-Skills cloud-retention-config --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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/cloud-retention-config .claude/skills/cloud-retention-config && rm -rf skills-src

Use ~/.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/

Facts

Skill name
cloud-retention-config
GitHub stars
301
Token cost
~3.7k tokens
SKILL.md length
1,294 words
Files
5 (incl. scripts, references, assets)
Skills in repo
280
Repo updated
First seen
Licence
Apache-2.0

At a glance

Configures cloud storage retention policies across AWS S3, Azure Blob Storage, and Google Cloud Storage.

  • Works in 5 steps: Identical retention periods: Replicated… → Synchronized lifecycle rules: Lifecycle… → Legal hold propagation: Legal holds… → …
  • Tasks that involve File uploads and storage
  • SKILL.md covers Overview, Legal Context, AWS S3 Lifecycle and Retention… and Microsoft Azure Blob Storage…, plus 3 more sections
  • Runs Python scripts from its folder; calls gcloud, aws and az

What it does

Cloud Retention Config is an agent skill from mukul975/Privacy-Data-Protection-Skills. Configures cloud storage retention policies across AWS S3, Azure Blob Storage, and Google Cloud Storage. Covers lifecycle rules, object lock, legal hold, immutability policies, cross-region replication retention alignment, and compliance mode configuration. Activate for cloud retention, S3 lifecycle, Azure retention, GCP retention policy queries.

Its SKILL.md is about 3.7k 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 File uploads and storage and Privacy and GDPR. It works with Google Cloud, Microsoft Azure, Amazon S3 and Azure Blob Storage. 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 File uploads and storage
  • Tasks that involve Privacy and GDPR

Example prompts

  • “Use the cloud-retention-config skill to configure cloud storage retention policies across AWS S3, Azure Blob Storage, and Google Cloud Storage”
  • “/cloud-retention-config”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Identical retention periods: Replicated data in the destination region must have the same retention period as the source.
  2. Synchronized lifecycle rules: Lifecycle transitions and expirations must be configured identically on source and destination…
  3. Legal hold propagation: Legal holds applied in the source must also be applied in the destination. Configure automated propagation.
  4. Deletion propagation: When an object expires or is deleted in the source, the replica must also be deleted. Configure replication to…
  5. Jurisdictional considerations: If the destination region is in a different jurisdiction, confirm that the applicable retention…

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.

    Shell commands in SKILL.md call:

    • gcloud
    • aws
    • az

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gcloud, aws and az, which can reach the network depending on how they are called.

    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

Cloud Retention Config loads about 3.7k tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 1,294 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~93
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.3k

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,294 words, ~3,705 tokens.

Download SKILL.mdSave it as .claude/skills/cloud-retention-config/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
cloud-retention-config
description
Configures cloud storage retention policies across AWS S3, Azure Blob Storage, and Google Cloud Storage. Covers lifecycle rules, object lock, legal hold, immutability policies, cross-region replication retention alignment, and compliance mode configuration. Activate for cloud retention, S3 lifecycle, Azure retention, GCP retention policy queries.
license
Apache-2.0
metadata.author
mukul975
metadata.version
1.0
metadata.domain
privacy
metadata.subdomain
data-retention-deletion
metadata.tags
cloud-retention, s3-lifecycle, azure-blob-retention, gcp-retention, object-lock

Cloud Storage Retention Configuration

Overview

Cloud storage platforms provide native retention and lifecycle management features that can enforce data retention schedules at the infrastructure level. Proper configuration ensures that personal data stored in cloud environments is automatically transitioned, archived, or deleted according to retention policies, while legal hold and object lock features prevent premature deletion of data subject to regulatory or litigation requirements. This skill covers configuration for the three major cloud platforms: AWS S3, Microsoft Azure Blob Storage, and Google Cloud Storage.

GDPR Article 5(1)(e) — Storage Limitation

Cloud storage retention policies are a technical implementation of the storage limitation principle, ensuring data is not retained beyond the period necessary for processing purposes.

GDPR Article 32 — Security of Processing

Retention configuration must include appropriate security measures, including encryption at rest, access controls, and audit logging for all retention-related operations.

GDPR Article 25 — Data Protection by Design and by Default

Cloud retention policies should be configured as default settings on all storage resources, rather than applied retroactively.

AWS S3 Lifecycle and Retention Configuration

S3 Lifecycle Rules

S3 Lifecycle rules automate transitions between storage classes and object expiration:

Lifecycle Rule Configuration for Orion Data Vault Corp
Rule NamePrefix/Tag FilterTransitionExpirationPurpose
customer-data-lifecycleprefix: customer-data/90 days → S3 Glacier Instant Retrieval; 365 days → S3 Glacier Deep Archive2,190 days (6 years)Customer transaction records — HMRC retention
marketing-data-lifecycletag: data-category=marketing180 days → S3 Intelligent-Tiering730 days (2 years)Marketing contact data — consent-based retention
analytics-data-lifecycleprefix: analytics/90 days → S3 Glacier Instant Retrieval790 days (26 months)Website analytics — ICO/CNIL recommended period
cctv-footage-lifecycleprefix: cctv/None30 daysCCTV footage — ICO CCTV Code of Practice
applicant-data-lifecycleprefix: recruitment/None180 days (6 months)Unsuccessful job applicant data
financial-records-lifecycleprefix: finance/365 days → S3 Glacier Deep Archive2,190 days (6 years)Financial and tax records — Companies Act 2006
employee-records-lifecycletag: data-category=employee730 days → S3 Glacier Deep ArchiveControlled by HR system (employment + 6 years)Employee HR records
S3 Lifecycle Rule — JSON Configuration Example
json
{
  "Rules": [
    {
      "ID": "customer-data-lifecycle",
      "Filter": {
        "Prefix": "customer-data/"
      },
      "Status": "Enabled",
      "Transitions": [
        {
          "Days": 90,
          "StorageClass": "GLACIER_IR"
        },
        {
          "Days": 365,
          "StorageClass": "DEEP_ARCHIVE"
        }
      ],
      "Expiration": {
        "Days": 2190
      },
      "NoncurrentVersionTransitions": [
        {
          "NoncurrentDays": 30,
          "StorageClass": "GLACIER_IR"
        }
      ],
      "NoncurrentVersionExpiration": {
        "NoncurrentDays": 2190
      }
    }
  ]
}
S3 Object Lock

S3 Object Lock prevents objects from being deleted or overwritten for a fixed retention period or indefinitely. It operates in two modes:

ModeBehaviourUse Case at Orion Data Vault Corp
Governance ModePrevents deletion by most users; users with s3:BypassGovernanceRetention permission can overrideStandard retention enforcement — allows DPO-approved early deletion for valid Art. 17 requests
Compliance ModePrevents deletion by ALL users, including root account, for the entire retention periodRegulatory records where deletion before expiry is legally prohibited (e.g., AML records under MLR 2017)
Object Lock Configuration
json
{
  "ObjectLockConfiguration": {
    "ObjectLockEnabled": "Enabled",
    "Rule": {
      "DefaultRetention": {
        "Mode": "GOVERNANCE",
        "Days": 2190
      }
    }
  }
}

Critical consideration for GDPR erasure: If using Compliance Mode, data subject erasure requests under Art. 17 cannot be fulfilled until the retention period expires. Use Governance Mode for data categories where erasure requests are possible, and reserve Compliance Mode only for data with mandatory statutory retention that overrides the right to erasure under Art. 17(3)(b).

Legal hold is an independent, on/off flag that prevents object deletion regardless of retention settings:

aws s3api put-object-legal-hold \
  --bucket orion-data-vault-regulated \
  --key customer-data/2024/transaction-batch-0142.parquet \
  --legal-hold Status=ON

Legal hold must be:

  • Applied immediately upon receipt of a litigation hold notice
  • Tracked in the litigation hold management register (cross-reference: litigation-hold-mgmt skill)
  • Removed only upon written authorization from Legal counsel
  • Auditable — all legal hold changes logged via CloudTrail

Microsoft Azure Blob Storage Retention

Immutability Policies

Azure Blob Storage supports immutability policies at the container level:

Policy TypeBehaviourConfiguration
Time-based retentionPrevents modification and deletion for a specified intervalSet retention interval in days; can be locked (irreversible) or unlocked
Legal holdPrevents modification and deletion until all legal hold tags are clearedApply named legal hold tags; multiple holds can coexist
Time-Based Retention Policy Configuration
json
{
  "properties": {
    "immutabilityPeriodSinceCreationInDays": 2190,
    "allowProtectedAppendWrites": true,
    "allowProtectedAppendWritesAll": false
  }
}
Azure Lifecycle Management Rules
json
{
  "rules": [
    {
      "enabled": true,
      "name": "customer-data-retention",
      "type": "Lifecycle",
      "definition": {
        "filters": {
          "blobTypes": ["blockBlob"],
          "prefixMatch": ["customer-data/"]
        },
        "actions": {
          "baseBlob": {
            "tierToCool": {
              "daysAfterModificationGreaterThan": 90
            },
            "tierToArchive": {
              "daysAfterModificationGreaterThan": 365
            },
            "delete": {
              "daysAfterModificationGreaterThan": 2190
            }
          },
          "snapshot": {
            "delete": {
              "daysAfterCreationGreaterThan": 2190
            }
          }
        }
      }
    },
    {
      "enabled": true,
      "name": "analytics-data-retention",
      "type": "Lifecycle",
      "definition": {
        "filters": {
          "blobTypes": ["blockBlob"],
          "prefixMatch": ["analytics/"]
        },
        "actions": {
          "baseBlob": {
            "tierToCool": {
              "daysAfterModificationGreaterThan": 90
            },
            "delete": {
              "daysAfterModificationGreaterThan": 790
            }
          }
        }
      }
    }
  ]
}
az storage container legal-hold set \
  --account-name oriondatavault \
  --container-name regulated-data \
  --tags "litigation-2026-001" "regulatory-investigation-2026-003"
Azure Versioning and Soft Delete Interaction

When configuring retention, account for Azure's soft delete and versioning features:

FeatureRetention ImpactRecommended Setting
Blob soft deleteDeleted blobs retained for recovery periodSet to 14 days — ensure actual deletion occurs after soft delete period
Container soft deleteDeleted containers retained for recoverySet to 14 days
Blob versioningPrevious versions retainedApply lifecycle rules to versions; ensure expired versions are deleted

Google Cloud Storage Retention

Bucket-Level Retention Policy

GCP applies retention policies at the bucket level. Objects cannot be deleted or overwritten until the retention period expires:

json
{
  "retentionPolicy": {
    "retentionPeriod": "189216000",
    "isLocked": false
  }
}

The retentionPeriod is specified in seconds. Common values:

Retention PeriodSecondsUse Case
30 days2,592,000CCTV footage
6 months15,552,000Unsuccessful applicant data
26 months68,256,000Analytics data
2 years63,072,000Marketing data
6 years189,216,000Financial/tax records
7 years220,752,000Audit records
Locking a Retention Policy
gcloud storage buckets update gs://orion-regulated-finance \
  --lock-retention-policy

Warning: Locking a retention policy is IRREVERSIBLE. Once locked, the retention period cannot be reduced or removed. The bucket cannot be deleted until every object in it has met its retention period. Only lock policies for data categories with absolute statutory retention requirements that override Art. 17 rights.

Show full SKILL.md (492 more words)Show less
GCP Object Hold
Hold TypeBehaviourUse Case
Temporary holdPrevents deletion; can be removed at any timeArt. 17 request pauses (assessment period); temporary preservation
Event-based holdPrevents deletion until the hold is released; retention period begins on hold releaseData where retention period starts from a future event (e.g., contract termination)
gcloud storage objects update gs://orion-regulated-data/customer-data/batch-0142.parquet \
  --temporary-hold
GCP Lifecycle Rules
json
{
  "lifecycle": {
    "rule": [
      {
        "action": {
          "type": "SetStorageClass",
          "storageClass": "NEARLINE"
        },
        "condition": {
          "age": 90,
          "matchesPrefix": ["customer-data/"]
        }
      },
      {
        "action": {
          "type": "SetStorageClass",
          "storageClass": "ARCHIVE"
        },
        "condition": {
          "age": 365,
          "matchesPrefix": ["customer-data/"]
        }
      },
      {
        "action": {
          "type": "Delete"
        },
        "condition": {
          "age": 2190,
          "matchesPrefix": ["customer-data/"]
        }
      }
    ]
  }
}

Cross-Region Replication Retention Alignment

When data is replicated across regions for availability or disaster recovery, retention policies must be aligned:

Alignment Requirements
  1. Identical retention periods: Replicated data in the destination region must have the same retention period as the source.
  2. Synchronized lifecycle rules: Lifecycle transitions and expirations must be configured identically on source and destination buckets/containers.
  3. Legal hold propagation: Legal holds applied in the source must also be applied in the destination. Configure automated propagation.
  4. Deletion propagation: When an object expires or is deleted in the source, the replica must also be deleted. Configure replication to handle delete markers.
  5. Jurisdictional considerations: If the destination region is in a different jurisdiction, confirm that the applicable retention requirements in that jurisdiction do not conflict with the source retention period.
Cross-Region Configuration Checklist
CheckAWSAzureGCP
Lifecycle rules match sourceApply identical S3 lifecycle rules to destination bucketApply identical lifecycle management policy to destination containerApply identical lifecycle rules to destination bucket
Retention/lock settings matchConfigure identical Object Lock settings on destinationApply identical immutability policy to destinationApply identical retention policy to destination
Delete marker replicationEnable DeleteMarkerReplication in replication configEnable blob change feed and handle deletesConfigure bucket notifications for deletion events
Legal hold synchronizationUse Lambda triggered by CloudTrail to propagate legal holdsUse Event Grid + Azure Function to propagate legal holdsUse Cloud Functions triggered by audit logs to propagate holds
MonitoringCloudWatch metrics on replication lagAzure Monitor replication metricsCloud Monitoring replication metrics

Compliance Monitoring

Monthly Cloud Retention Audit
  1. Policy drift detection: Compare active lifecycle rules and retention policies against the approved retention schedule. Flag any discrepancies.
  2. Coverage verification: Confirm that all storage buckets/containers holding personal data have applicable retention policies.
  3. Legal hold inventory: List all active legal holds across all cloud platforms. Cross-reference with the litigation hold register to identify holds that should have been released.
  4. Expiration verification: Sample recently expired objects to confirm they were actually deleted (not just transitioned or soft-deleted).
  5. Cross-region consistency: Verify that replicated buckets/containers maintain identical retention configuration.
Alert Configuration
AlertConditionAction
Policy removedRetention policy or lifecycle rule deleted from a regulated bucketImmediate alert to Cloud Security + DPO
Object lock bypasss3:BypassGovernanceRetention usedAlert to DPO; verify authorized deletion
Legal hold changeLegal hold applied or removedLog to litigation hold register; alert Legal
Retention policy unlock attemptAttempt to modify locked retention policyAlert to Cloud Security (should fail — investigate)
Replication lag > 24hCross-region replication behind by more than 24 hoursAlert IT Operations — potential retention gap in DR region

© 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/cloud-retention-config 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

Cloud Retention Config 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.

Cloud Retention Config compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cloud Retention Config this skillmukul975/Privacy-Data-Protection-Skills301—~3.7kAutomated safety check: PassApache-2.0
Deploying Cloud Deception With Decoy Resourcesmukul975/Anthropic-Cybersecurity-Skills34k—~2.8kAutomated safety check: PassApache-2.0
Implementing Cloud Dlp For Data Protectionmukul975/Anthropic-Cybersecurity-Skills34k—~4.2kAutomated safety check: PassApache-2.0
Azure Storagemicrosoft/GitHub-Copilot-for-Azure2552 repos~1.3kAutomated safety check: PassMIT
Neon Object Storageneondatabase/agent-skills100—~3.5kAutomated safety check: NotesApache-2.0
Storage S3 Resiliency Expertiseaws/tools-for-devops-agent103—~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • Deploying Cloud Deception With Decoy Resources

    mukul975/Anthropic-Cybersecurity-Skills

    Deploy cloud-native deception across AWS, Azure, and GCP using decoy (honey) resources whose only purpose is to generate a high-fidelity alert the instant an attacker touches them: canary IAM access…

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Implementing Cloud Dlp For Data Protection

    mukul975/Anthropic-Cybersecurity-Skills

    Implement cloud DLP using Amazon Macie, Google Cloud DLP API, Microsoft Purview, Azure Information Protection, and Nightfall AI to discover, classify, label, de-identify, and protect sensitive data…

    34k GitHub stars~4.2k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed
  • Azure Storage

    microsoft/GitHub-Copilot-for-Azure

    Official

    Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake.

    255 GitHub starsUsed in 2 repos~1.3k tokens
    DatabasesAuto-check passed
  • Neon Object Storage

    neondatabase/agent-skills

    Official

    S3-compatible object storage that branches with your Neon project, so files and the database stay in sync across every branch.

    100 GitHub stars~3.5k tokensUpdated yesterday
    Backend & APIsAuto-check: notes
  • Storage S3 Resiliency Expertise

    aws/tools-for-devops-agent

    Official

    S3 resiliency, security, and data protection review. An agent skill from aws/tools-for-devops-agent.

    103 GitHub stars~2.8k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Azure Storage Blob Py

    microsoft/skills

    Official

    Azure Blob Storage SDK for Python. An agent skill from microsoft/skills.

    3.1k GitHub stars~2.3k tokensUpdated today
    Backend & APIsAuto-check passed

More from mukul975/Privacy-Data-Protection-Skills

All 280 skills in this repo
  • Age Gating Services

    mukul975/Privacy-Data-Protection-Skills

    Implements age-gating mechanisms for online services to restrict access based on user age.

    301 GitHub stars~3.7k tokensUpdated 6 mo ago
    Auto-check passed
  • AI Data Retention

    mukul975/Privacy-Data-Protection-Skills

    Manages AI model retention and machine unlearning requirements.

    301 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • 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.

    301 GitHub stars~3.4k tokensUpdated 6 mo ago
    Auto-check passed
  • 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).

    301 GitHub stars~846 tokensUpdated 6 mo ago
    Auto-check passed
  • 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.

    301 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • 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.

    301 GitHub stars~880 tokensUpdated 6 mo ago
    Auto-check passed

Questions about Cloud Retention Config

What does Cloud Retention Config do?

Configures cloud storage retention policies across AWS S3, Azure Blob Storage, and Google Cloud Storage. Cloud Retention Config is an agent skill from mukul975/Privacy-Data-Protection-Skills. Configures cloud storage retention policies across AWS S3, Azure Blob Storage, and Google Cloud Storage.

When should I use Cloud Retention Config?

Cloud Retention Config fits situations like: tasks that involve File uploads and storage; tasks that involve Privacy and GDPR.

How do I install Cloud Retention Config in Claude Code?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cloud-retention-config -a claude-code`. Or copy the skill folder (skills/privacy/cloud-retention-config in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/cloud-retention-config in your project. Claude Code loads it when a task matches its description.

How do I install Cloud Retention Config in Codex?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cloud-retention-config -a codex`. Or copy the skill folder (skills/privacy/cloud-retention-config in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/cloud-retention-config in your project. Codex loads it when a task matches its description.

Can I use Cloud Retention Config 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 cloud-retention-config -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cloud-retention-config, .gemini/skills/cloud-retention-config, .github/skills/cloud-retention-config and .opencode/skills/cloud-retention-config in your project.

What does Cloud Retention Config need to run?

Going by SKILL.md and its folder, Cloud Retention Config needs Python for the scripts in its folder and the command-line tools its instructions call (gcloud, aws and az). Our summary lists: Python 3.

Does Cloud Retention Config 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 Cloud Retention Config 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 Cloud Retention Config use?

Cloud Retention Config 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 Cloud Retention Config use?

About 3.7k tokens (SKILL.md is roughly 15k 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.6k tokens, read only when the agent opens those files.

What are the alternatives to Cloud Retention Config?

Skills that share tags, products or a category with Cloud Retention Config: Deploying Cloud Deception With Decoy Resources (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Implementing Cloud Dlp For Data Protection (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Azure Storage (microsoft/GitHub-Copilot-for-Azure, 255 stars) and Neon Object Storage (neondatabase/agent-skills, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cloud Retention Config?

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.