smithery/silviase

refactoring-10-security-privacy

Use when checking for data leaks, PII handling, and license risks in Python research code.

Installation

$ npx skills add smithery/silviase --skill refactoring-10-security-privacy

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/silviase.

npx skills add smithery/silviase

Browse all from smithery/silviase

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,160 B
  • docs SUMMARY.md 129 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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 .gitignore excludes 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.