Security audit
Security checks across malware telemetry and agentic risk
This is a transparent instruction-only demo-building skill that may create prototype files and optionally research references, but it has a review gate and no hidden execution, credentials, or persistence.
Install this only where it is acceptable for the coding agent to make prototype-oriented file changes with reasonable assumptions. Review generated files, dependencies, mock data, and any external reference research, and be cautious when explicitly asking it to skip the default review gate.
- Use realistic mock content. - Include important states, not just the happy path. - Visually communicate the intended product experience. - Make incomplete functionality feel intentional through simulation or clear state changes. Prototype techniques may include:
- [ ] Empty data state renders cleanly. - [ ] Long text or overflow does not break layout. - [ ] Invalid input is handled with visible feedback. - [ ] Repeated clicks on primary actions do not corrupt state. - [ ] Loading or pending state is visible where async work happens. - [ ] Failure path shows recoverable UI, not a crash. - [ ] Small viewport, 375px width or equivalent, remains usable on the main screen.
57/57 vendors flagged this skill as clean.
No suspicious patterns detected.
