security-gate
Review Security Before Release
Teams miss security issues when release checks are informal. This skill guides Claude, Codex, and Claude Code through structured security questions and warning templates.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "security-gate" from https://skillstore.io/skills/danielpodolsky-security-gate.md and its manifest at https://skillstore.io/api/skills/danielpodolsky-security-gate/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "security-gate". Review a profile update feature before release.
Expected outcome:
Security gate warning: user input is accepted, but server-side validation is not documented. Confirm allowed fields, length limits, and ownership checks before release.
Using "security-gate". Assess an admin-only export feature.
Expected outcome:
Critical warning: the feature exports sensitive data and needs clear admin authorization checks, audit logging, and safe error handling before production use.
Using "security-gate". Check a password reset flow.
Expected outcome:
Security gate questions: how long do reset tokens last, where are they stored, and what prevents reuse after a successful reset?
Security Audit
SafeAll static findings are false positives caused by Markdown security checklist text and illustrative vulnerability examples. The skill contains no executable scripts, external command execution, environment access, or prompt injection attempts.
Risk Factors
⚡ Contains scripts (4)
⚙️ External commands (20)
🔑 Env variables (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/danielpodolsky-security-gate/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/danielpodolsky-security-gate?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/danielpodolsky-security-gate?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/danielpodolsky-security-gate/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/danielpodolsky-security-gate.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
DanielPodolsky. (2026). security-gate security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/danielpodolsky-security-gate/audits/8BibTeX citation
@techreport{danielpodolsky-danielpodolsky-security-gate-2026,
author = {DanielPodolsky},
title = {security-gate security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/danielpodolsky-security-gate/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "security-gate security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "DanielPodolsky"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/danielpodolsky-security-gate/audits/8"
identifiers:
- type: other
value: "skillstore:danielpodolsky-security-gate:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Pre-Release Feature Review
Check a new feature for input validation, authorization, and data exposure risks before launch.
Security Coaching Session
Use structured questions to help a developer understand security risks in their implementation.
Pull Request Risk Triage
Summarize security concerns from a change and decide which issues need attention before merge.
Try These Prompts
Run the security gate for this feature. Focus on user input, data access, secrets, and obvious release risks.
Apply the security gate to this pull request. List pass items, warnings, critical warnings, and questions for the author.
Use the security gate to review how this change handles sensitive data, tokens, logs, errors, and authorization checks.
Run the full security gate and produce a release recommendation. Separate must-fix issues, recommended fixes, residual risks, and owner questions.
Best Practices
- Provide the relevant code paths, data flows, and user roles before running the gate.
- Treat critical warnings as release blockers until a responsible owner accepts the risk.
- Document each warning with a location, impact, and follow-up decision.
Avoid
- Using the gate as a substitute for automated security testing.
- Reviewing only happy paths and skipping malicious input cases.
- Closing warnings without recording the reason or owner.
Frequently Asked Questions
Does this skill scan my repository automatically?
Can it find every vulnerability?
What does a critical warning mean?
Who should use this skill?
Does it support Claude Code and Codex workflows?
What input works best?
Developer Details
Author
DanielPodolskyLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
34f316ba14ef36c7a620fc09f2676d2429997a77
Maintenance freshness
7/18/2026
Usage
6 downloads · 256 views
File structure
📄 SKILL.md