policy-checker

Name: policy-checker
Availability: InStock
Author: vmobifystudio

Validate project privacy, security, licensing, and accessibility policies with explicit evidence.

4|Updated Jun 1, 2026

Search Tags:#security #compliance #privacy #evidence tracking #release readiness #waivers #policy validation

Ready to run

npx skills add https://github.com/vmobifystudio/app-dev-team --skill policy-checker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: policy-checker
Source: https://github.com/vmobifystudio/app-dev-team/tree/main/skills/policy-checker
Command: npx skills add https://github.com/vmobifystudio/app-dev-team --skill policy-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents sensitive changes and releases from being approved without documented evidence for privacy, security, accessibility, licensing, and release requirements.

Core Features & Use Cases

Policy Validation: Runs the project's policy check and identifies applicable compliance artifacts.
Evidence-Based Findings: Classifies issues as BLOCKED, CANNOT EVALUATE, or WAIVED with required ownership and supporting evidence.
Release Governance: Links findings to tickets and release records while distinguishing facts, assumptions, decisions, and recommendations.
Use Case: Before releasing an app with a new data-sharing feature, use this Skill to verify the relevant privacy and security evidence and identify any unresolved approval blockers.

Quick Start

Ask the policy checker to validate the project policies and report every finding with its evidence, owner, and release impact.

Frequently Asked Questions about policy-checker

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

FAQPage Schema

How do I verify policy compliance before a software release?▼

To verify policy compliance before a software release, validate project privacy, security, licensing, accessibility, and release requirements by running a policy check that classifies findings and requires explicit evidence for every approval.

What is evidence-based release governance for sensitive changes?▼

Evidence-based release governance for sensitive changes is the process of linking compliance findings to tickets and release records while distinguishing facts, assumptions, decisions, and recommendations to prevent unapproved deployments.

How do I document authorized waivers for security and privacy compliance findings?▼

To document authorized waivers for security and privacy compliance findings, classify the issue as WAIVED with required ownership and supporting evidence linked directly to the relevant tickets and release records.

Can I use a policy checker to identify unresolved release blockers for a new data-sharing feature?▼

Yes, you can use a policy checker to identify unresolved release blockers for a new data-sharing feature by validating the applicable privacy and security evidence and reporting any missing approval documentation.

What does it mean when a compliance policy check returns CANNOT EVALUATE?▼

When a compliance policy check returns CANNOT EVALUATE, it means the system lacks sufficient declared policy artifacts or evidence to classify the finding as BLOCKED or WAIVED for the release readiness assessment.