← ClaudeAtlas

agentic-security-review-skilllisted

Create CompleteTech LLC security, safety, permissions, and production-readiness review artifacts for agentic development workflows, including risk intake, tool permissions, secrets handling, data exposure, prompt-injection testing, retrieval trust, approval gates, external actions, audit logging, model/provider configuration, retention, dependency risk, least privilege, launch blockers, rollback, incident response, escalation, red-team results, and security signoff. Use before production launch or whenever tools, data, credentials, integrations, retrieval sources, or external actions change.
CompleteTech-LLC/agentic-security-review-skill · ★ 0 · AI & Automation · score 73
Install: claude install-skill CompleteTech-LLC/agentic-security-review-skill
# Agentic Security Review Skill ## Purpose Create practical security review artifacts for CompleteTech LLC agentic development workflows. Use this skill before launch, before granting new access, after material configuration changes, and after incidents or near misses. ## System Boundary This skill owns security, safety, permissions, data, credential, tool, and launch-risk review. Use it alongside discovery, proposal, or delivery when risk needs a dedicated artifact. It does not replace `agentic-delivery-skill` launch checklists, `agentic-contract-skill` legal terms, external compliance certification, formal penetration testing, or counsel-reviewed privacy/security advice. ## Core Workflow 1. Identify the review event: launch, new tool, sensitive data, external action, retrieval/RAG, credential change, dependency change, incident, or signoff. 2. Gather verified facts: workflow purpose, users, data classes, tools, permissions, credentials, integrations, retrieval sources, human approvals, logs, deployment path, rollback owner, incident contacts, and known constraints. 3. Use `references/use-case-decision-table.md` to choose the right review artifact. 4. Use `references/security-positioning.md` for CompleteTech LLC security language and guardrails. 5. Use `references/security-catalog.md` for the artifact library. 6. Keep the review bounded and evidence-based. Do not claim compliance, certification, legal approval, penetration-test completion, production readiness, or guar