security

Name: security
Availability: InStock
Author: zmsqnfl-commits

Automate security and privacy reviews, storing validated outputs in final/.

1|Updated Jun 3, 2026

Search Tags:#security #rbac #static-analysis #privacy #dependency-check #artifact-management

Ready to run

npx skills add https://github.com/zmsqnfl-commits/quintpact-vas --skill security-zmsqnfl-commits

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security
Source: https://github.com/zmsqnfl-commits/quintpact-vas/tree/main/.agents/skills/security
Command: npx skills add https://github.com/zmsqnfl-commits/quintpact-vas --skill security-zmsqnfl-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Security and privacy risks in project workflows are mitigated by automated reviews, with validated outputs stored to final/ after successful verification.

Core Features & Use Cases

Automated security review and privacy compliance checks on project assets.
Final artifact storage to final/ after passing checks, with audit-ready reporting.
Workflow integration with /setup-from-application to auto-update rules and RBAC policies.

Quick Start

Run the security review on your current project and save validated results to final/.

Frequently Asked Questions about security

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

FAQPage Schema

How do I automate security and privacy reviews for project assets before release?▼

To automate security and privacy reviews for project assets, you can use this Skill to run static analysis and dependency checks during pre-release workflows. It validates your artifacts and only stores outputs to final/ after all checks pass successfully.

What static analysis and dependency scanners are used for code reviews?▼

The designated scanners used for static analysis and dependency checks include bandit, safety, npm audit, trivy, and snyk. These tools validate project assets to identify vulnerabilities before allowing any writes to the final/ directory.

How does RBAC enforcement work with artifact validation?▼

RBAC enforcement restricts write access to the final/ directory, ensuring only designated users can save validated outputs. This workflow integrates with /setup-from-application to auto-update rules and RBAC policies during artifact validation.

Can I use this for pre-release workflow artifact validation and audit reporting?▼

Yes, this is specifically designed for pre-release workflows, code reviews, and artifact validation. It enforces RBAC, applies designated scanners, and generates audit-ready reporting while restricting writes to final/ only after successful validation.

What are the limitations of restricting writes to final/ after security checks?▼

Restricting writes to final/ after security checks means unvalidated outputs cannot be stored in that directory. This ensures audit-ready reporting and privacy compliance, but requires all static analysis and dependency checks to pass successfully first.