Automate Chilean Compliance with the compliance-cl Agent Skill

Where this fits

A founder building a SaaS for Chilean users faces two ticking clocks: the new data privacy law (Ley 21.719, effective Dec 2026) and the already‑active economic crimes law (Ley 21.595). Manually reading legal texts and drafting policies is a multi‑week chore. compliance-cl turns that into a repo‑level audit: an agent scans your codebase, asks clarifying questions, and produces the full set of compliance documents—policy, DPA, RAT, EIPD, consent forms—pre‑filled and versioned. No lawyer required for the first pass.

Why agents benefit

• Multi‑framework orchestration: The skill understands both laws and can generate docs for one or both, so an agent can adapt its output to the user's specific business type and data flows.
• Legal‑text grounding: It contrasts decisions against the official statute text, not generic templates, giving agents a reliable reference for reasoning about privacy and prevention obligations.
• Zero‑handoff documentation: Every deliverable is fully filled out—no placeholders or "TODO: ask counsel"—so the agent can produce a usable artifact in a single run.
• Versioned state for re‑runs: The skill leaves a structured state in the repo, letting agents re‑audit later when code or law changes, and only regenerate what's necessary.
• Interactive clarification: It uses AskUserQuestion to resolve ambiguities (e.g., data categories, company size), making the agent proactive rather than guessing.

Practical scenarios

Pre‑launch compliance sweep

Before launching a new SaaS in Chile, the agent runs compliance-cl on the repo. It identifies personal data handling patterns, asks about retention and consent mechanisms, and outputs a privacy policy, DPA, and EIPD—ready to publish.

Annual re‑audit after feature changes

A fintech app adds a new analytics module. The agent re‑runs the skill, detects the new data flows, and updates the existing compliance documents—only modifying sections that changed, keeping the version history clean.

Preparing for an economic crimes audit

A company needs to demonstrate a crime prevention model (Ley 21.595). The agent audits internal processes, generates the required RAT and risk matrix, and flags where human legal review is still necessary—see the skill's references/cuando-acudir-a-abogado.

Add it to your agent workflow

Install the skill into your agent (e.g., Claude, Cursor, or any npx‑compatible environment):

npx skills add Lelemon-studio/compliance-cl --skill compliance-cl

Then trigger it with a natural language request like:

Run compliance-cl on this repo for Ley 21.719 and 21.595. Ask me what you need.

The agent will read the repo, ask clarifying questions, and write the compliance pack into a compliance/ folder with a state.json for future runs.

Compare before adopting

Before relying on compliance-cl, evaluate its quality signals: check GitHub stars (currently 191) and recent commit activity to confirm maintenance. Compare it with other security/compliance skills that might cover different jurisdictions or offer manual templates. Most importantly, test it on a sample repo to see if the generated docs match your expected quality and if the AskUserQuestion flow fits your agent's interaction style. Also consider whether your team prefers a fully automated approach over a human‑in‑the‑loop alternative.

Why it is worth tracking

compliance-cl is a strong example of a domain‑specific agent skill that turns legal complexity into a deterministic workflow. Its active repository, clear scope, and MIT license make it a safe bet for early adoption. With Chile's data law deadline approaching, this skill will likely gain traction as more developers need automated compliance. Track it now, and when your agent needs to handle LatAm legal frameworks, it'll be a proven tool. For more details and community updates, see the skill page on OpenAgentSkill.