Columbia-Cloudworks-LLC/auditor
.cursor/skills/auditor/SKILL.md
Use when generating a jurisdiction-specific audit questionnaire and pass-fail compliance matrix from a regulatory rule pack, such as Texas audit readiness requests.
$ install --global
skillsauthnpx skillsauth add Columbia-Cloudworks-LLC/EquipQR auditorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 10:46 PM14.1s2 files scanned
SKILL.md
- name:
- auditor
- description:
- Use when generating a jurisdiction-specific audit questionnaire and pass-fail compliance matrix from a regulatory rule pack, such as Texas audit readiness requests.
Auditor
Purpose
Generate a deterministic audit questionnaire and pass-fail matrix for a named regulatory space.
This skill only produces:
- Scope assumptions
- Audit questions
- Pass-fail matrix
- Coverage gaps (if the rule pack is incomplete)
Not In Scope
Do not produce:
- developer remediation guidance
- implementation instructions
- browser workflows
- screenshot capture steps
- printable report assembly
- evidence collection playbooks
If the user asks for those, stop after this output and recommend a separate downstream skill.
Invocation
/auditor texas- "Generate Texas audit questions and pass/fail matrix"
- "Create an audit questionnaire for Texas compliance readiness"
Rule Packs
Load a jurisdiction reference from this directory:
texas.md
If the jurisdiction is unsupported, say so and list available packs.
Workflow
Copy this checklist and complete in order:
Auditor Progress
- [ ] 1) Confirm jurisdiction and assumptions
- [ ] 2) Load matching rule pack
- [ ] 3) Emit fixed audit questions by regime
- [ ] 4) Build pass-fail matrix from rule-pack logic
- [ ] 5) Report coverage gaps without inventing requirements
1) Confirm jurisdiction and assumptions
State:
- jurisdiction name
- regulatory regimes covered by the pack
- applicability assumptions when needed
2) Load matching rule pack
Use only mapped requirements from the pack. Do not add legal requirements from memory.
3) Emit fixed audit questions by regime
Use the same regime order and question order defined in the pack.
4) Build pass-fail matrix
Create a matrix using this schema:
| Regime | Area | Audit Question | Pass When | Fail When | | --- | --- | --- | --- | --- |
Rules:
- keep language deterministic and testable
- map each row to a question or control area from the pack
- avoid advice text in matrix cells
5) Report coverage gaps
If requirements are missing or ambiguous in the pack, add a short Coverage Gaps section.
Output Contract
Always return, in this exact order:
ScopeAudit QuestionsPass-Fail MatrixCoverage Gaps(only if needed)
Formatting Contract
- Use concise markdown headings
- Group questions by regime and area
- Keep question wording auditor-facing
- Keep matrix rows one control intent per row
Guardrails
- Do not claim legal certification or legal advice
- Do not invent citations not present in the rule pack
- Do not mix developer and auditor outputs
- Do not include evidence-production instructions
Example (Texas)
When asked for Texas:
- Load
texas.md - Emit the regime-ordered questionnaire
- Emit the pass-fail matrix based on Texas pass-fail logic
- Stop
Related Skills
Columbia-Cloudworks-LLC/react-best-practices
development
VerifiedTrustedCommunity
React performance optimization guidelines from Vercel Engineering, with EquipQR-specific mappings (Vite + React Router + TanStack Query). Use when writing, reviewing, or refactoring React code in this repo, especially around waterfalls, bundle size, and re-renders.
1SKILL.mdUpdated Apr 16, 2026
Columbia-Cloudworks-LLC/postgres-best-practices
testing
VerifiedTrustedCommunity
Postgres performance optimization and best practices from Supabase, adapted to EquipQR's Supabase (Postgres + RLS) workflow. Use when editing SQL, migrations, indexes, or RLS policies.
1SKILL.mdUpdated Apr 16, 2026
Columbia-Cloudworks-LLC/brand-guidelines
development
VerifiedTrustedCommunity
Applies EquipQR's brand colors and design-system tokens to any artifact that should match EquipQR's look-and-feel. Use it when brand colors, style guidelines, visual formatting, or EquipQR design standards apply.
1SKILL.mdUpdated Apr 16, 2026
Columbia-Cloudworks-LLC/trowel
development
VerifiedTrustedCommunity
Use when auditing dependency health, API contract consistency, shared data shapes, or brittle integration seams between modules, services, and packages.
1SKILL.mdUpdated Apr 16, 2026