RE
refactoring-10-security-privacy
Use when checking for data leaks, PII handling, and license risks in Python research code.
Install
mkdir -p .claude/skills/refactoring-10-security-privacy && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14767" && unzip -o skill.zip -d .claude/skills/refactoring-10-security-privacy && rm skill.zipInstalls to .claude/skills/refactoring-10-security-privacy
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when checking for data leaks, PII handling, and license risks in Python research code.90 chars✓ has a “when” trigger
About this skill
Refactoring 10: Security and Privacy
Goal
Reduce risk of data leakage, PII exposure, or license violations.
Sequence
- Order: 10
- Previous: refactoring-09-performance-profiling
- Next: refactoring-11-ci-automation
Workflow
- Scan for hardcoded secrets, tokens, or private endpoints.
- Success: Secrets and risky endpoints are identified.
- Identify PII fields and confirm how they are stored and logged.
- Success: PII fields and handling are documented.
- Check dataset and library licenses for compatibility.
- Success: License constraints are verified and noted.
- Ensure
.gitignoreexcludes sensitive outputs and large artifacts.- Success: Sensitive outputs are not tracked by git.
- Document required security or privacy constraints in
README.md.- Success: README describes required constraints and handling rules.
Guardrails
- Do not delete or redact data without approval.
- Escalate if sensitive data is discovered.
- Keep changes minimal and focused on safety.