New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Az Eu Website Privacy Audit

by lawve-ai in lawve-ai/awesome-legal-skills

Audits a website for compliance with Azerbaijan's Law on Personal Data No.

CC-BY-4.0Auto-check passedLegal & Compliance

Install Az Eu Website Privacy Audit

skills CLI
$ npx skills add lawve-ai/awesome-legal-skills --skill az-eu-website-privacy-audit -a claude-code

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

GitHub CLI
$ gh skill install lawve-ai/awesome-legal-skills az-eu-website-privacy-audit --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/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/az-eu-website-privacy-audit-mirza-chiragov .claude/skills/az-eu-website-privacy-audit && 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
az-eu-website-privacy-audit
GitHub stars
847
Token cost
~3.8k tokens
SKILL.md length
1,909 words
Files
8 (incl. references, assets)
Skills in repo
154
Repo updated
First seen
Licence
CC-BY-4.0

At a glance

Audits a website for compliance with Azerbaijan's Law on Personal Data No.

  • Works in 7 steps: Scope → Document inventory → AZ Law findings → …
  • The user shares a URL
  • SKILL.md covers When to invoke, Inputs you need before starting, Workflow and Anti-hallucination rules, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Az Eu Website Privacy Audit is an agent skill from lawve-ai/awesome-legal-skills. Audits a website for compliance with Azerbaijan's Law on Personal Data No. 998-IIIQ and, where applicable, EU GDPR plus ePrivacy/cookie consent rules. Inventories the privacy documents present (privacy policy, cookie policy, cookie banner, consent flow, controller and DPO contact, data subject rights channel, cross-border transfer disclosures, AZ operator-registration references) and scores each against the applicable statutory requirements. Produces a dual-layer report: a plain-language traffic-light summary for…

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files and assets (for example `README.md`, `assets/audit_report_template.md` and `references/az_law_998_overview.md`).

It sits in Legal & Compliance, covering Privacy and GDPR. The repository describes itself as: A curated list of awesome Agent Skills for automating legal work. The licence is CC-BY-4.0.

When your agent uses it

  • The user shares a URL
  • Privacy/cookie policy text for an AZ-based
  • AZ-targeted site
  • Also when the user mentions an .az domain

Example prompts

  • “is my site GDPR compliant”
  • “do I need to register as an operator in Azerbaijan”
  • “is our cookie banner lawful”
  • “/az-eu-website-privacy-audit”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Scope
  2. Document inventory
  3. AZ Law findings
  4. GDPR findings (only if applicable per Step 1)
  5. ePrivacy / cookie findings
  6. Cross-border transfer analysis
  7. Produce the report

What it can do on your machine

Read from SKILL.md and the folder at commit 045f738. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Az Eu Website Privacy Audit loads about 3.8k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 262 tokens; SKILL.md has 1,909 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from lawve-ai/awesome-legal-skills at commit 045f738, republished under its CC-BY-4.0 licence (© lawve-ai). 1,909 words, ~3,825 tokens.

Download SKILL.mdSave it as .claude/skills/az-eu-website-privacy-audit/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
az-eu-website-privacy-audit
description
Audits a website for compliance with Azerbaijan's Law on Personal Data No. 998-IIIQ and, where applicable, EU GDPR plus ePrivacy/cookie consent rules. Inventories the privacy documents present (privacy policy, cookie policy, cookie banner, consent flow, controller and DPO contact, data subject rights channel, cross-border transfer disclosures, AZ operator-registration references) and scores each against the applicable statutory requirements. Produces a dual-layer report: a plain-language traffic-light summary for business owners plus a clause-by-clause findings table with article-level citations for lawyers. Assessment-only — no drafting. Use whenever the user shares a URL or privacy/cookie policy text for an AZ-based or AZ-targeted site; also when the user mentions an .az domain, Law 998, the AZ State Register, ePrivacy, an Art. 27 EU representative, or asks "is my site GDPR compliant", "do I need to register as an operator in Azerbaijan", or "is our cookie banner lawful" — even without the word "audit".
license
CC BY 4.0
author
Mirza Chiragov
metadata
author: "Mirza Chiragov" license: "cc-by-4.0" version: "2026-05-13"

Azerbaijan + EU Website Privacy Compliance Audit

You are acting as a personal data compliance reviewer for a website. Your job is to identify what the site has, what it is missing, and where it diverges from the applicable law — under both the Azerbaijani Law on Personal Data No. 998-IIIQ (the "AZ Law") and, where applicable, the EU GDPR plus the ePrivacy regime. You do not draft replacement documents. If the user asks for drafts, decline and say this skill is assessment-only.

When to invoke

Trigger this skill when the user:

  • Shares a URL or pastes the text of a privacy policy, cookie policy, terms of service, consent banner, or any combination of these, and asks for a compliance review.
  • Mentions Azerbaijan, an .az domain, an AZ-registered business, or "operator registration" in the context of personal data.
  • Asks whether GDPR applies to their AZ-based business.
  • Asks whether a cookie banner is lawful or whether their consent flow is valid.
  • Mentions Law No. 998, Law on Personal Data, the State Register of personal data information systems, EDPB, EDPS, Convention 108, the e-Privacy Directive, or Planet49 / cookie consent case law in an AZ context.

Do not invoke this skill for: general legal advice, dispute resolution, drafting of privacy documents, employment data questions outside of website processing, or jurisdictions other than AZ + EU.

Inputs you need before starting

Before generating findings, confirm the following with the user. If anything is missing, ask once in a single consolidated message; do not stop the audit if the user says "use your best judgment".

  1. What you have access to. A live URL, pasted text, screenshots, or a file. If only a URL is given and you cannot fetch it, request the text.
  2. Site language(s). The audit is performed against the original language of the documents. Do not score compliance based on a machine translation.
  3. Audience. Is the site offered to (a) only Azerbaijani users, (b) EU/EEA users, (c) both, (d) global? This drives GDPR Art. 3 applicability.
  4. What the site does. Public marketing site, e-commerce, SaaS account/login, mobile app companion, ad-supported media, etc. This drives which lawful bases and cookie categories are realistic.
  5. Output preference. Default is "both layers" (executive summary + lawyer-grade table). If the user wants only one, comply.

If the user is plainly a business owner (non-lawyer phrasing, asks "is this OK"), lead with the executive summary and put the citation-heavy table under a collapsed/secondary heading. If the user is a lawyer (cites articles, asks about specific provisions), lead with the findings table.

Workflow

Follow these steps in order. Do not skip the scoping step even if the user seems impatient — without scope, the GDPR applicability analysis is unreliable.

Step 1 — Scope

Produce a short scoping block:

  • Site URL / identifier
  • Language(s) of privacy documents reviewed
  • Apparent controller (legal entity name, country, contact)
  • Business model and categories of personal data processed (inferred)
  • Audience determination (AZ only / EU-targeted / global)
  • GDPR applicability conclusion: applies / does not apply / unclear, with one-sentence reasoning grounded in Art. 3 GDPR. See references/gdpr_for_az_websites.md.
  • AZ Law applicability: virtually always applies if the controller is registered in AZ or processes data of AZ persons. Confirm and move on.
  • Cookie / ePrivacy regime: applies if the site is accessible from the EU/EEA and uses non-strictly-necessary trackers. See references/eprivacy_and_cookies.md.
Step 2 — Document inventory

List every privacy-relevant document found on the site, with status:

DocumentStatusLocation
Privacy policy / noticePresent / Missing / Linked but inaccessibleURL or "footer link"
Cookie policy……
Cookie consent banner……
Terms of service / use……
Data subject rights request form or channel……
Controller identification (legal entity, address)……
DPO or AZ representative contact……
Operator-registration disclosure (AZ)……
EU representative under Art. 27 GDPR (if GDPR applies and controller is outside EU)……

Treat "linked-but-404" or "linked but only in a language the audience does not speak" as non-compliant, not "present".

Step 3 — AZ Law findings

For each requirement in references/az_law_998_overview.md, record:

  • Requirement (one line)
  • Statutory anchor (article of Law 998-IIIQ)
  • Evidence from the site (quote, verbatim, in the original language — translate in parentheses if not English)
  • Status: Compliant / Partial / Missing / Risk / Not applicable
  • Note (one or two sentences explaining the gap or why partial)

Also assess operator-registration obligations using references/az_operator_registration.md and flag explicitly whether the user appears to need to register.

Step 4 — GDPR findings (only if applicable per Step 1)

Same table structure, with anchors to GDPR articles. Cover at minimum:

  • Lawful basis (Art. 6) — is one stated, and is it plausible?
  • Special categories (Art. 9) — if processed, is Art. 9(2) basis identified?
  • Information to data subjects (Arts. 13 and 14) — checklist in the reference file
  • Data subject rights (Arts. 15–22) — is each named with a channel to exercise it?
  • International transfers (Chapter V, Arts. 44–49) — for any data flowing out of EU/EEA
  • Records / accountability (Art. 30) — is there a stated controller and contact?
  • DPO (Art. 37) — is one appointed where required?
  • EU representative (Art. 27) — required for non-EU controllers offering goods or services to EU residents
  • Security and breach notification (Arts. 32–34) — referenced in the policy?

See references/gdpr_for_az_websites.md for the full checklist and citation pinpoints.

Using references/eprivacy_and_cookies.md, assess:

  • Is a banner shown on first visit before any non-essential trackers fire?
  • Is "Reject all" as easy as "Accept all"?
  • Are pre-ticked boxes used? (Always non-compliant per Planet49.)
  • Are cookie categories itemised (strictly necessary, functional, analytics, advertising) with purposes and retention?
  • Is the cookie policy linked from the banner?
  • If IAB TCF is implemented, is the CMP a registered vendor and is the consent string properly stored?
  • Is consent withdrawable as easily as it was given?

If the user has tooling output (a cookie scanner export, a HAR file, a TCF console log), use it. Otherwise, base findings on the visible banner UI and any pasted code/screenshots, and flag the limitation.

Step 6 — Cross-border transfer analysis

If the site or its processors send personal data outside Azerbaijan (almost always yes — analytics, hosting, payment, email), check both legs:

  • Outbound from AZ. Under Law 998-IIIQ, cross-border transfer requires legal grounds (typically consent or adequate protection in the destination). Note that AZ is a party to Council of Europe Convention 108, which provides one basis for transfers to other Convention parties. See references/cross_border_transfers.md.
  • Outbound from EU/EEA to AZ (relevant if EU users' data flows back to AZ controllers/processors). AZ has no EU adequacy decision as of the knowledge cutoff — transfers require Chapter V safeguards (SCCs + a transfer impact assessment, BCRs, or a derogation under Art. 49). Verify the SCCs are the 2021 modules, not the legacy 2010/2004 sets.
Step 7 — Produce the report

Use the template in assets/audit_report_template.md. Do not deviate from the section order — the template is structured so a business reader can stop after the executive summary and a lawyer can drill into the findings tables.

Show full SKILL.md (783 more words)Show less

Anti-hallucination rules

These rules are non-negotiable. A wrong citation in a legal audit is worse than a missing one.

  1. Never invent article numbers. If you are not certain of the exact provision, write Law No. 998-IIIQ, provision on [topic] or GDPR, the provision requiring [X]. Do not produce a fabricated "Art. 14(2)(c)" you are not sure exists.
  2. Quote, do not paraphrase, when assessing the policy text. The findings table must include the actual wording from the document under review (in the original language, with a translation only in parentheses). If the user did not share the text and only gave a URL you cannot fetch, stop and request the text.
  3. State the jurisdiction of each finding. Every row in a findings table must make clear whether the requirement comes from the AZ Law, GDPR, ePrivacy, or a combination. Mixed-jurisdiction findings should be split.
  4. Mark the regulator and registration body generically. Azerbaijan's regulatory architecture for personal data has been reorganised more than once. Refer to "the competent Azerbaijani authority" and "the State Register of personal data information systems" rather than naming a specific agency unless the user has stated it. If you do name one, mark it as "verify current name with the user / Ministry of Digital Development and Transport".
  5. Flag unverified facts explicitly. If something is uncertain — for example, whether a CMP is properly registered under IAB TCF, or whether a cross-border transfer actually occurs to a non-Convention-108 country — write Unverified: [reason] in the findings table rather than guessing.
  6. Do not score compliance against a translated text. If the policy is in Azerbaijani or Russian and you only have a machine translation, mark all language-dependent findings as Unverified — original-language review required.
  7. No drafting. This skill is assessment-only. If asked to draft a privacy policy, cookie banner copy, or any other document, decline and refer the user to a drafting workflow.

Output structure

Always use this exact section order, taken from assets/audit_report_template.md:

# Privacy Compliance Audit — [Site identifier]

## 1. Executive summary
   - Top 3 critical issues (red)
   - Top 3 medium issues (amber)
   - Overall compliance posture: AZ Law / GDPR / ePrivacy
   - One-paragraph plain-language summary for the business owner

## 2. Scope
   - As produced in Step 1

## 3. Document inventory
   - As produced in Step 2

## 4. Findings — Azerbaijani Law No. 998-IIIQ

## 5. Findings — GDPR (if applicable)

## 6. Findings — ePrivacy / cookies

## 7. Cross-border transfers

## 8. Operator registration assessment (AZ)

## 9. Prioritised remediation list
   - Numbered list of fixes, each tagged [AZ] / [EU] / [ePrivacy], with severity

## 10. Assumptions and limitations
   - What the auditor could not verify and why

Severity levels

Use these consistently across all findings tables:

  • Red / Critical. Direct statutory breach with realistic regulatory or litigation exposure. Examples: no privacy notice at all; pre-ticked consent for advertising cookies; international transfers to non-adequate jurisdictions with no safeguards; processing of special-category data without an Art. 9 basis.
  • Amber / Material. Provision is present but materially deficient — for example, lawful basis listed but not tied to specific processing purposes; data subject rights named without a working channel to exercise them.
  • Yellow / Minor. Drafting gap unlikely to attract enforcement on its own — for example, retention stated as "as long as necessary" without further detail.
  • Green / Compliant. Provision meets the requirement.
  • Grey / Not applicable. Document or topic does not apply to this site.

Examples

Example 1 — business owner asking about cookies

Input: "Hi, our AZ company runs an e-commerce site at example.az, we sell to people in Azerbaijan and some in Germany. Our cookie banner has Accept and Settings. Is this OK?"

Approach: Run full Step 1 scoping (Germany customers → GDPR Art. 3(2)(a) applies → ePrivacy applies for cookies on EU visitors). Find that "no Reject button parallel to Accept" is a Red finding under Planet49 and EDPB Guidelines 05/2020. Lead with the executive summary in plain language; place the article citations in the detailed findings table.

Example 2 — lawyer reviewing a policy

Input: "Please review the attached privacy policy for an AZ fintech onboarding KYC documents. They have users in AZ, UAE, and France."

Approach: GDPR applies for the French users. KYC implies Art. 9 special-category data may be processed (depending on data types). AML/CFT obligation is a lawful-basis candidate under Art. 6(1)(c). AZ Law operator registration almost certainly required for a fintech KYC system. Lead with the findings tables; keep the executive summary brief.

Example 3 — pasted policy text, AZ-only audience

Input: A wall of text in Azerbaijani plus "we only serve Azerbaijan, do we need GDPR?"

Approach: Conclude GDPR does not apply (Art. 3 not triggered) unless the user later reveals EU targeting. Run AZ Law and operator-registration analysis only. Assess the original-language text directly; do not run machine translation through the findings.

Reference files

Read these into context only when you reach the relevant step — they are not needed for scoping.

  • references/az_law_998_overview.md — Key obligations under Law No. 998-IIIQ with article anchors and audit checkpoints.
  • references/az_operator_registration.md — When operator registration in the State Register is required, exemptions, and what to look for on the site.
  • references/gdpr_for_az_websites.md — Art. 3 applicability, Art. 27 EU representative, and a checklist of Arts. 13/14 disclosures.
  • references/eprivacy_and_cookies.md — Consent requirements, Planet49, EDPB guidance, IAB TCF assessment points.
  • references/cross_border_transfers.md — Both directions: AZ-out under Law 998 + Convention 108, and EU-out to AZ under Chapter V.

Asset files

  • assets/audit_report_template.md — The mandatory output structure for the final report.

© lawve-ai, CC-BY-4.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 7 other files (references, assets) in skills/az-eu-website-privacy-audit-mirza-chiragov of lawve-ai/awesome-legal-skills.

  • SKILL.md
  • README.md
  • assets/audit_report_template.md
  • references/az_law_998_overview.md
  • references/az_operator_registration.md
  • references/cross_border_transfers.md
  • references/eprivacy_and_cookies.md
  • references/gdpr_for_az_websites.md

Open the folder on GitHubat commit 045f738

Compare with similar skills

Az Eu Website Privacy Audit 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.

Az Eu Website Privacy Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Az Eu Website Privacy Audit this skilllawve-ai/awesome-legal-skills847—~3.8kAutomated safety check: PassCC-BY-4.0
C15tc15t/c15t1.9k1 repos~1.6kAutomated safety check: PassApache-2.0
HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed5.5k—~1.7kAutomated safety check: PassApache-2.0
Korean Privacy Termskimlawtech/korean-privacy-terms587—~2.9kAutomated safety check: PassApache-2.0
Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9461 repos~3.9kAutomated safety check: PassMIT
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9461 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • C15t

    c15t/c15t

    Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.

    1.9k GitHub starsUsed in 1 repo~1.6k tokens
    Legal & ComplianceAuto-check passed

  • 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.

    5.5k GitHub stars~1.7k tokensUpdated today
    Legal & ComplianceAuto-check passed

  • Korean Privacy Terms

    kimlawtech/korean-privacy-terms

    처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.

    587 GitHub stars~2.9k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

  • 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…

    946 GitHub starsUsed in 1 repo~3.9k tokens
    Legal & ComplianceAuto-check passed

  • Hipaa Compliance

    Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

    Expert HIPAA compliance assistant for healthcare and software contexts.

    946 GitHub starsUsed in 1 repo~2.3k tokens
    Legal & ComplianceAuto-check passed

  • Pii Contract Analyze

    gregmos/PII-Shield

    Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.

    150 GitHub stars~8.9k tokensUpdated 3 mo ago
    Legal & ComplianceAuto-check: notes

More from lawve-ai/awesome-legal-skills

All 154 skills in this repo

  • Customs Trade Law Onur Kafkas

    lawve-ai/awesome-legal-skills

    U.S. An agent skill from lawve-ai/awesome-legal-skills.

    847 GitHub stars~4.1k tokensUpdated 8 days ago
    Auto-check passed

  • Eu Data Act Oliver Schmidt Prietz

    lawve-ai/awesome-legal-skills

    Practitioner skill for advising on EU Regulation 2023/2854 (Data Act).

    847 GitHub stars~3.9k tokensUpdated 8 days ago
    Auto-check passed

  • Litigation Deadline Calendar

    lawve-ai/awesome-legal-skills

    Calendar litigation and arbitration deadlines from a scheduling order.

    847 GitHub stars~4.3k tokensUpdated 8 days ago
    Auto-check passed

  • Outlook Emails Lawvable

    lawve-ai/awesome-legal-skills

    Read, search, and download emails and attachments from Microsoft Outlook via OAuth2.

    847 GitHub stars~672 tokensUpdated 8 days ago
    Auto-check passed

  • Ambiguity Report

    lawve-ai/awesome-legal-skills

    Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable.

    847 GitHub stars~4.6k tokensUpdated 8 days ago
    Auto-check passed

  • Cookie Policy Malik Taiar

    lawve-ai/awesome-legal-skills

    Guide for drafting cookie policies compliant with GDPR and the ePrivacy Directive.

    847 GitHub stars~3k tokensUpdated 8 days ago
    Auto-check passed

Categories

Questions about Az Eu Website Privacy Audit

What does Az Eu Website Privacy Audit do?

Audits a website for compliance with Azerbaijan's Law on Personal Data No. Az Eu Website Privacy Audit is an agent skill from lawve-ai/awesome-legal-skills. Audits a website for compliance with Azerbaijan's Law on Personal Data No.

When should I use Az Eu Website Privacy Audit?

Az Eu Website Privacy Audit fits situations like: the user shares a URL; privacy/cookie policy text for an AZ-based; AZ-targeted site; also when the user mentions an .az domain.

How do I install Az Eu Website Privacy Audit in Claude Code?

Run `npx skills add lawve-ai/awesome-legal-skills --skill az-eu-website-privacy-audit -a claude-code`. Or copy the skill folder (skills/az-eu-website-privacy-audit-mirza-chiragov in lawve-ai/awesome-legal-skills) into .claude/skills/az-eu-website-privacy-audit in your project. Claude Code loads it when a task matches its description.

How do I install Az Eu Website Privacy Audit in Codex?

Run `npx skills add lawve-ai/awesome-legal-skills --skill az-eu-website-privacy-audit -a codex`. Or copy the skill folder (skills/az-eu-website-privacy-audit-mirza-chiragov in lawve-ai/awesome-legal-skills) into .agents/skills/az-eu-website-privacy-audit in your project. Codex loads it when a task matches its description.

Can I use Az Eu Website Privacy Audit 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 lawve-ai/awesome-legal-skills --skill az-eu-website-privacy-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/az-eu-website-privacy-audit, .gemini/skills/az-eu-website-privacy-audit, .github/skills/az-eu-website-privacy-audit and .opencode/skills/az-eu-website-privacy-audit in your project.

What does Az Eu Website Privacy Audit need to run?

SKILL.md names no scripts, command-line tools or credentials: Az Eu Website Privacy Audit is instructions for the agent only.

Does Az Eu Website Privacy Audit 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 Az Eu Website Privacy Audit 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. Review the folder before installing.

What licence does Az Eu Website Privacy Audit use?

Az Eu Website Privacy Audit is published under the CC-BY-4.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Az Eu Website Privacy Audit use?

About 3.8k 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 8.5k tokens, read only when the agent opens those files.

What are the alternatives to Az Eu Website Privacy Audit?

Skills that share tags, products or a category with Az Eu Website Privacy Audit: 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 Az Eu Website Privacy Audit?

lawve-ai (a GitHub organization) maintains it in lawve-ai/awesome-legal-skills, which has 847 GitHub stars. The repository holds 154 skills in this directory. The repository was last updated on October 2, 2026.

Source: lawve-ai/awesome-legal-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.