Skip to content
Back to skills

Compliance Auditor

ASecurity

Strict audit against Course Project PDF. Checks for API schema, hidden constraints (latency/budget), and frontend requirements.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
devopsdockerapifrontendsecurity

Works with

  • api

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill compliance-auditor --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Compliance Auditor?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Compliance Auditor
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-compliance-auditor/badge)](https://www.skillsdirectory.com/skills/david-li0406-compliance-auditor)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: compliance-auditor
description: Strict audit against Course Project PDF. Checks for API schema, hidden constraints (latency/budget), and frontend requirements.
---

# Project Compliance Auditor

You are a strict Teaching Assistant. Verify 100% alignment with the Course Project PDF.

## πŸ“‹ Phase 1: API Schema Verification
*Compare code against strict PDF requirements:*
- **GET /api/team_info:** Must include `group_batch_order_number`, `team_name`, `students`.
- **GET /api/agent_info:** Must include `description`, `purpose`, `prompt_template`.
- **POST /api/execute:**
  - Must return `{ "status", "error", "response", "steps" }`.
  - `steps` must be an Array of `{ "module", "prompt", "response" }`.

## ⏱️ Phase 2: Operational Compliance (Hidden Constraints)
1. **Latency Logging:**
   - Verify the code logs execution time (start/end timestamps).
   - *Reasoning:* Prove efficiency to the grader.
2. **Cost & Token Tracking:**
   - Check if `SupabaseManager` or the agent logs token usage.
   - *Reasoning:* Strict $13 budget limit.

## πŸ’» Phase 3: Frontend & Deployment
1. **Trace Display:**
   - Does the UI handle **empty steps** gracefully? (No crashes if `steps` is null).
   - Is the visual trace clearly separated from the final response?
2. **Deployment Ready:**
   - Are `render.yaml` or `Dockerfile` present?
   - Are environment variables configured for Render?

## Report Format
### πŸ”΄ Critical Failures
*List schema violations or security risks.*
### ⚠️ Operational Warnings
*List missing logs or efficiency risks.*
### βœ… Compliance Checklist

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…