Compétences database-guardrails
📦

database-guardrails

Révision du contenu r1 Sûr

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.

Prend en charge: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 78 Bronze

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent
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.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/shreyam1008-database-guardrails.md manifest signé GET /api/skills/shreyam1008-database-guardrails/manifest lockfile signé GET /api/skills/shreyam1008-database-guardrails/lockfile

Tester

Utilisation de « database-guardrails ». Add persistence for customer delivery preferences without accessing a database.

RĂ©sultat attendu:

  • 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.

Utilisation de « database-guardrails ». Review a proposal to index every column in the orders table.

RĂ©sultat attendu:

  • 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.

Audit de sécurité

Sûr
v1 • 02/10/2026 Ouvrir le rapport versionné

The 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.

1
Fichiers analysés
83
Lignes analysées
0
Éléments à examiner
0
Faux positifs ignorés
Le dernier audit statique et sémantique terminé n’a détecté aucun constat de sécurité confirmé. Cela ne prouve pas que le skill est sans effets secondaires.
Audité par: codex
Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné
Évaluation de sécurité

Copier le lien du rapport

https://skillstore.io/skills/shreyam1008-database-guardrails/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/shreyam1008-database-guardrails/security.svg)](https://skillstore.io/skills/shreyam1008-database-guardrails?utm_source=security_passport_badge)

Badge 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>

Carte intégrable

<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>
Citations académiques (APA · BibTeX · CFF)

Citation APA

shreyam1008. (2026). database-guardrails security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-database-guardrails/audits/1

Citation 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"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen
55
Architecture
85
Maintenabilité
87
Contenu
65
Communauté
91
Conformité aux spécifications

Ce que vous pouvez créer

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.

Essayez ces prompts

Clarify a Database Request 
I need persistence for [workflow]. Ask about requirements and ownership before proposing a schema. Do not connect to or query any database.
Propose a Minimal Schema 
Review the repository schema for [workflow]. Propose the smallest necessary change and its integrity constraints. List open questions and avoid live database access.
Justify an Index Proposal 
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 Migration Review 
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.

Bonnes pratiques

  • 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.

Éviter

  • 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.

Foire aux questions

Does the skill access a database automatically?
Its instructions prohibit live access unless the user explicitly authorizes the exact target, operation, and scope.
Does it enforce permissions technically?
No. It provides behavioral instructions for the agent. Database credentials and access controls still require independent configuration.
What can happen before database approval?
The agent can review repository code, schema files, migration history, documentation, and synthetic or disposable fixtures.
What if the project has no migration system?
It directs the agent to create a scoped migration artifact with dry-run, recovery, and execution instructions before any authorized run.
How does it decide whether an index is needed?
Each index needs a named query, constraint, access path, or measured problem, with selectivity and operational costs considered.
Can it guarantee a safe production migration?
No. Safety depends on project-specific review, explicit authorization, recovery readiness, and fresh-install and upgrade testing in disposable environments.

Détails du développeur

Licence

MIT

RĂ©vision Skillstore

r1

Avis de version

L’auteur n’a déclaré aucune version.

DĂ©pĂ´t

https://github.com/shreyam1008/shre-skills/tree/ba9787f41c2fe1be1062eeb6322bc339a1026383/skills/database-guardrails

RĂ©f

bbec03cf10354f3aaccd6dd24eda4ac9ceeceac5

RĂ©cence de maintenance

02/10/2026

Utilisation

0 téléchargements · 0 vues

Structure de fichiers

đź“„ SKILL.md