otto

Detect LGPD privacy violations in source code using pattern-based checks.

14|1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/metricasboss/otto --skill otto-metricasboss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: otto
Source: https://github.com/metricasboss/otto/tree/main/skills/lgpd
Command: npx skills add https://github.com/metricasboss/otto --skill otto-metricasboss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OTTO LGPD Guard helps teams prevent privacy violations by scanning code for LGPD-related risks and sensitive data exposures before changes reach production.

Core Features & Use Cases

  • Detects hardcoded personal data such as CPF, RG, email, and phone numbers.
  • Flags risky logging, analytics tracking without consent, and unauthorized data sharing.
  • Use Case: before commits that modify data collection, run a privacy scan to catch violations early and reduce risk of fines.

Quick Start

Run an LGPD privacy analysis on your codebase to identify violations and receive concrete remediation steps.

Frequently Asked Questions about otto

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan source code for LGPD privacy violations?

LGPD privacy violations in source code are detected using pattern-based checks defined in patterns.json, which identify hardcoded personal data like CPF and RG, risky logging, and unauthorized data sharing, while assessing risk and proposing remediation steps.

What types of personal data does LGPD compliance scanning detect in code?

It detects hardcoded personal data including CPF, RG, email, and phone numbers, and flags risky logging, analytics tracking without consent, and unauthorized data sharing scenarios within source code.

When do I need to run an LGPD privacy analysis on my codebase?

You should run an LGPD privacy analysis before commits that modify data collection, logging, or analytics, catching violations early to reduce the risk of fines before changes reach production.

Can I get remediation steps for code that logs user information without consent?

Yes, when risky logging or analytics tracking without consent is flagged, the analysis assesses the risk and proposes concrete remediation steps to resolve the LGPD violation.

What is the best way to prevent LGPD violations before changes reach production?

The best way to prevent LGPD violations before production is to run a privacy scan that catches hardcoded personal data exposures and unauthorized data sharing early, reducing the risk of fines.