← ClaudeAtlas

student-data-protectionlisted

Design, implement or audit student-data protection in school applications. Use when a change affects personal data, identity, permissions, retention, exports or AI data flows, or for a requested privacy/security review. Do not turn an unrelated cosmetic edit into a full compliance audit.
siberius/student-data-protection · ★ 5 · Data & Documents · score 80
Install: claude install-skill siberius/student-data-protection
# Student data protection Use the requested scope and available evidence. This skill supports school software work; it does not certify compliance or authorise production changes. The English/Czech editions cover Czech primary and secondary schools (ZŠ/SŠ), excluding preschools and higher education; choose the actual jurisdiction. A language choice alone does not select national law. ## Choose the mode and affected boundary Infer design, implementation, audit or incident from the request. For an audit, inspect and report without changing the application. Incident analysis does not authorise shutting down services, revoking accounts or sending notifications. For authorised implementation, change the affected boundary and check meaningful regressions. Do not restart a whole-system review for a narrow fix. Flag a serious adjacent risk with evidence and a proposed action rather than silently expanding work. Before substantive work, establish all context necessary for the requested scope. Reuse known facts and safe project inspection, then ask about every relevant gap (goal/scope, jurisdiction, data, audience, identity, recipients, lifecycle, environment and permissions); use workflow section 1.3 as the intake. Wait for consequential missing answers before dependent decisions or changes. Ask in short batches, do not request secrets or real learner records, and do not repeat answered questions or granted authorisation. Synthetic data allow development while a real-data processi