database-guardrails
Plan Database Changes With Explicit Approval
Database changes can damage data when scope, recovery, and permissions are unclear. This skill guides minimal schema designs and reviewed migration plans before authorized database access.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Review the Skillstore skill "database-guardrails" from https://skillstore.io/skills/shreyam1008-database-guardrails.md and its manifest at https://skillstore.io/api/skills/shreyam1008-database-guardrails/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "database-guardrails". Add persistence for customer delivery preferences without accessing a database.
Resultado esperado:
- Known facts: Live database access is not authorized; existing schema ownership remains unknown.
- Minimal proposal: Reuse the customer model if its ownership and compatibility support the required preference.
- Open questions: Which values are valid, can preferences be absent, and what retention requirements apply?
- Migration artifact: Pending repository review and clarified requirements.
- Approval needed: Specify the target, operation, and scope before any live access.
- Database actions taken: None.
Usando "database-guardrails". Review a proposal to index every column in the orders table.
Resultado esperado:
- Known facts: No named queries or measured performance problems were supplied.
- Minimal proposal: Do not add blanket indexes; identify actual filters, joins, ordering, and uniqueness requirements.
- Open questions: What are the expected selectivity, existing index coverage, write volume, and storage costs?
- Approval needed: Explicit permission is required before collecting live query plans.
- Database actions taken: None.
Auditoría de seguridad
SeguroThe system reconnaissance flag is a false positive: SKILL.md:46 discusses uniqueness, nullability, checks, and valid state transitions. The skill requires explicit authorization before live database access and promotes reviewed migrations. No evidence found of prompt injection, credential theft, or data exfiltration in the reviewed file.
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/shreyam1008-database-guardrails/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/shreyam1008-database-guardrails?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/shreyam1008-database-guardrails?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/shreyam1008-database-guardrails/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/shreyam1008-database-guardrails.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citas académicas (APA · BibTeX · CFF)
Cita APA
shreyam1008. (2026). database-guardrails security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-database-guardrails/audits/1Cita BibTeX
@techreport{shreyam1008-shreyam1008-database-guardrails-2026,
author = {shreyam1008},
title = {database-guardrails security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/shreyam1008-database-guardrails/audits/1},
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: "database-guardrails security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "shreyam1008"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/shreyam1008-database-guardrails/audits/1"
identifiers:
- type: other
value: "skillstore:shreyam1008-database-guardrails:audit:1"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
Design a Minimal Persistence Model
Clarify one application workflow and propose only necessary schema changes without accessing a live database.
Review a Production Migration Plan
Check authorization, recovery, locking, backfills, and disposable upgrade tests before approving migration execution.
Evaluate Proposed Indexes
Review query justification, selectivity, existing coverage, storage, and write costs before retaining an index.
Prueba estos prompts
I need persistence for [workflow]. Ask about requirements and ownership before proposing a schema. Do not connect to or query any database.
Review the repository schema for [workflow]. Propose the smallest necessary change and its integrity constraints. List open questions and avoid live database access.
Review [query description] and the repository indexes. Explain candidate indexes, selectivity assumptions, duplicate coverage, and write costs. Request authorization before obtaining live query plans.
Prepare a versioned migration plan for [change] using repository conventions. Cover backfills, locking, idempotency, disposable tests, recovery, and approval needed. Do not execute database actions.
Mejores prácticas
- Specify the exact database target, operation, and permitted side effects before authorizing access.
- Start with repository artifacts and one bounded workflow before expanding the schema.
- Review versioned migrations, recovery steps, and disposable fresh-install and upgrade tests before execution.
Evitar
- Treating a general development request as permission to inspect or mutate a live database.
- Adding speculative tables, generic data models, or indexes without concrete requirements.
- Running unreviewed SQL, changing applied migrations, or silently modifying schema during application startup.
Preguntas frecuentes
Does the skill access a database automatically?
Does it enforce permissions technically?
What can happen before database approval?
What if the project has no migration system?
How does it decide whether an index is needed?
Can it guarantee a safe production migration?
Detalles del desarrollador
Autor
shreyam1008Licencia
MIT
Revisión de Skillstore
r1
Aviso de versión
El autor no declaró una versión.
Ref.
bbec03cf10354f3aaccd6dd24eda4ac9ceeceac5
Actualidad del mantenimiento
2/10/2026
Uso
0 descargas · 0 vistas
Estructura de archivos
📄 SKILL.md