Skip to content
Back to skills

Security Advisory Lessons

ASecurity

Perform a dedicated nanace security review for authentication, authorization/RBAC, RLS and tenant isolation, Qdrant filtering, secrets, MCP exposure, Google sync, or other security boundaries. Use only when the user requests a security review or an adversarial review explicitly escalates to the full threat map; do not auto-load solely because code touches a sensitive path.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentsrustgosecurity

Works with

  • mcp

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 18, 2026

npx -y skills add felichita/nanace --skill security-advisory-lessons --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Security Advisory Lessons?

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

Security grade badge for Security Advisory Lessons
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/felichita-security-advisory-lessons/badge)](https://www.skillsdirectory.com/skills/felichita-security-advisory-lessons)

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: security-advisory-lessons
description: Perform a dedicated nanace security review for authentication, authorization/RBAC, RLS and tenant isolation, Qdrant filtering, secrets, MCP exposure, Google sync, or other security boundaries. Use only when the user requests a security review or an adversarial review explicitly escalates to the full threat map; do not auto-load solely because code touches a sensitive path.
---

# nanace Security Review

Use this skill as the deep security lens. For a normal adversarial review with a
matched security surface, the concise security reference under
`adversarial-validation` is sufficient.

## Workflow

1. Freeze the exact diff/head and identify the changed trust boundaries.
2. Inspect the headings in [threat-patterns.md](references/threat-patterns.md),
   then read the matching sections. Read the full map only for a broad audit.
3. Trace unauthenticated, outsider (other org), wrong-team member,
   low-role member (reader), removed member, malformed-input, and
   default-config cases. Security decisions must fail closed.
4. Require a focused negative regression test for the bypass form (HTTP-level,
   plus a `scoped_tx` test when tenancy is involved), not only the intended
   success path. State residual risk when a test is impractical.
5. Report proven vulnerabilities separately from defense-in-depth hardening.

## Finding Standard

Every candidate names the lower-trust principal, the boundary it crosses, the
affected resource, and the observable result. A best-practice gap or an impact
confined to the caller's own principal is hardening, not a candidate.

Report each candidate under exactly one verdict:

- `confirmed`: a complete `file:line` source trace and a bounded observed
  result. Only confirmed findings carry severity; each also states attacker
  prerequisites, concrete input/path, impact, smallest safe fix, and a
  regression check.
- `needs_validation`: the trace is blocked on one exact unresolved fact, such
  as deployment or infrastructure behavior. State that fact; assign no severity
  and do not substitute an assumption.
- `rejected`: a disproved candidate, with the caller, invariant, or test that
  disproves it.

Do not exaggerate unauthenticated impact when the actual issue requires
authenticated low privilege.

Files in this skill

  • SKILL.md2.3 KB
  • references/threat-patterns.md3.7 KB

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.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.