skills.rest
Nickalus12
Nickalus12COMMUNITY
Explore all skills by this author →
GitHub

security-audit

Audit authentication, authorization, data exposure, and secret handling risks in Loom-style systems.

2|Updated Apr 4, 2026
Search Tags:#authorization#security#vulnerability#audit#remediation#risk-assessment
One-click install
npx skills add https://github.com/Nickalus12/Loom --skill security-audit-nickalus12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/Nickalus12/Loom/tree/main/claude/skills/security-audit
Command: npx skills add https://github.com/Nickalus12/Loom --skill security-audit-nickalus12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loom-style security audits identify and assess security weaknesses across authentication, authorization, data exposure, secret handling, and exploitability risks in Loom-based systems.

Core Features & Use Cases

  • End-to-end security assessment across authentication and authorization flows.
  • Identification and classification of vulnerabilities with remediation guidance.
  • Use Case: When reviewing a Loom deployment or integration, run a structured audit to surface high-risk issues and suggested mitigations.

Quick Start

Define the audit scope, run a Loom-style security assessment across authentication, authorization, and data handling, and deliver prioritized remediation guidance.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I run a security audit on my Loom deployment?▼

Run a Loom-style security audit by defining your audit scope or file paths, then tracing trust boundaries, auth flows, secret handling, and data exposure paths. The process classifies findings by severity and delivers remediation guidance prioritized by risk.

What's the best way to identify secret handling vulnerabilities in a Loom system?▼

The best way to identify secret handling vulnerabilities is applying a structured security audit that traces trust boundaries and secret handling flows across your defined Loom system scope, classifying discovered exposure risks by severity.

Do I need to define an audit scope before assessing Loom vulnerability risks?▼

Yes, you need to define an audit scope or specific file paths before assessing Loom vulnerability risks. Defining the scope allows the audit to effectively trace trust boundaries, auth flows, and data exposure paths to classify findings by severity.

How are security findings classified during a Loom system audit?▼

Security findings are classified by severity during a Loom system audit. After tracing auth flows and data exposure paths, the audit delivers remediation guidance prioritized by risk, ensuring high-risk exploitability issues are addressed first.

Related Skills

Explore More Software Engineering Skills→
balic-AI-ML-R-D-Resourcesbalic-AI-ML-R-D-Resources

security-audit-context-building

Map architecture, trust boundaries, and data flows for security audit scoping.

Official
Advanced
Kevin-Liu-01Kevin-Liu-01
16

security-audit

Audit codebases for adversarial security vulnerabilities across code, config, and deployment boundaries.

Community
Advanced
jaskaranhundaljaskaranhundal
3

sast-dast-coordinator

Orchestrate SAST, DAST, SCA, and secrets scanning tools to correlate and prioritize findings.

Community
Advanced
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic