agentsclimarketplace

Security review checklist

Skill alexzhu0/agent-ready-skills/skills/security-review-checklist

Ten practical AI-agent skills for turning messy work into clear context, evals, reviews, and launch-ready artifacts.

Install
npx -y skills add alexzhu0/agent-ready-skills --skill security-review-checklist

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when reviewing feature specs, tool integrations, agent workflows, API changes, or launch plans for security concerns such as auth, secrets, data exposure, abuse paths, and approval gates.

SKILL.md

1.5 KB, as published. Nobody here has run it

Security Review Checklist

Purpose

Create a pragmatic security review checklist for a feature or workflow.

Fit

  • Use when a feature, tool, integration, or agent workflow can affect data, auth, secrets, or external actions.
  • Do not use when the change is purely cosmetic and has no trust boundary or data-flow impact.

Inputs

  • Feature spec, tool list, API change, workflow description, or launch plan.
  • Auth model, data handled, deployment surface, and user roles if available.
  • Known security requirements or compliance constraints.

Workflow

  1. Identify assets, actors, trust boundaries, and sensitive data.
  2. Review auth, authorization, secrets, logging, and external calls.
  3. Look for abuse paths, privilege escalation, data leakage, and unsafe defaults.
  4. Convert findings into checks and required approvals.
  5. Separate blockers from follow-up hardening.

Output

Produce Markdown with:

  • Security Scope
  • Assets And Trust Boundaries
  • Risk Checklist
  • Required Controls
  • Approval Gates
  • Blockers
  • Follow-Up Hardening

Validation

  • Sensitive data paths are explicit.
  • Auth and authorization are checked separately.
  • Findings have practical controls.
  • Public or external writes require approval gates.
  • Unknown security context is not treated as safe.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.