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.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
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.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„database-guardrails“ wird verwendet. Add persistence for customer delivery preferences without accessing a database.
Erwartetes Ergebnis:
- 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.
„database-guardrails“ wird verwendet. Review a proposal to index every column in the orders table.
Erwartetes Ergebnis:
- 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.
Sicherheitsaudit
SicherThe 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.
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/shreyam1008-database-guardrails/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/shreyam1008-database-guardrails?utm_source=security_passport_badge)HTML-Badge
<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>Einbettungskarte
<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>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
shreyam1008. (2026). database-guardrails security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-database-guardrails/audits/1BibTeX-Zitat
@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"
Skillstore-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
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.
Diese Prompts ausprobieren
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.
Bewährte Praktiken
- 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.
Vermeiden
- 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.
Häufig gestellte Fragen
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?
Entwicklerdetails
Autor
shreyam1008Lizenz
MIT
Skillstore-Revision
r1
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
bbec03cf10354f3aaccd6dd24eda4ac9ceeceac5
Aktualität der Wartung
2.10.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur
📄 SKILL.md