agentsclimarketplace

Sillytavern database rolecards

Skill LiarMTTT/TavernWeave/skills/sillytavern-database-rolecards

Design and validate structured in-card data models for SillyTavern rolecards, including table schemas, stable record keys, MVU message-floor storage, field bindings, deterministic migrations, and status-bar or control-center consumers. Use when a rolecard behaves like a small database application or needs schema and migration fixtures across normal multi-floor conversations. Do not introduce an external SQL service or claim same-floor compatibility without real-host evidence.From its SKILL.md

Install
npx -y skills add LiarMTTT/TavernWeave --skill sillytavern-database-rolecards

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

3.6 KB, as published. Nobody here has run it

SillyTavern Database Rolecards

Before schema or migration writes, use $consult-tavernweave-library with the sillytavern-database-rolecards route and load A0, C4, and C7. C8 is returned only with explicit experimental opt-in and remains blocked from mature claims until real-host acceptance.

Treat structured rolecard state as versioned application data. Keep schema, migration, storage scope, writers, and UI bindings machine-checkable.

Fix the supported storage route

First-batch support is limited to normal multi-floor state using message-floor or MVU data. Mark same-floor compatibility as DBR-C8-UNVERIFIED; do not add a fallback that silently changes scope.

Read rolecard-data-model.md before defining tables or migrations. Read floor-and-ui-binding.md before connecting a field to a script, prompt, status bar, or control center.

When exact runtime calls matter, verify getVariables, updateVariablesWith, Mvu.getMvuData, MVU events, and message events with $sillytavern-api-reference. Prefer updater functions and event-driven refresh over replacing an entire variable object.

Validate the model

node scripts/validate-rolecard-schema.mjs model.json

Require a stable model ID and version, a stat_data storage root, multi-floor strategy, explicit tables, primary keys, typed fields, valid defaults, and unique identifiers. Reject same-floor strategy in this release.

Run migration fixtures

node scripts/run-database-migrations.mjs --migration migration.json --input before.json --expected after.json

Require deterministic output and idempotence. Preserve unknown records and fields. Reject destructive operations unless the migration declares data loss and the caller passes --allow-data-loss. Do not write migrated data without --write and --out.

Check every consumer

node scripts/check-field-bindings.mjs --schema model.json --bindings bindings.json

Every binding must reference a declared table and field, name its reader or writer, identify the UI or prompt surface, and state refresh events. Route UI implementation to $sillytavern-embedded-ui and packaging to $sillytavern-card-pipeline.

Keep runtime acceptance open

Static checks cannot prove new-chat initialization, edit, swipe, chat switch, reload, or persistence behavior. Require a real-SillyTavern matrix for those cases before claiming runtime compatibility. Keep C8 excluded until that matrix passes.

Report

State the model version, storage route, table and binding counts, migration result, preserved unknown data, destructive-operation decision, and pending host cases.

Resources

  • scripts/validate-rolecard-schema.mjs: validate the model contract.
  • scripts/run-database-migrations.mjs: apply deterministic migration fixtures.
  • scripts/check-field-bindings.mjs: verify table/field consumers.
  • references/rolecard-data-model.md: schema and migration format.
  • references/floor-and-ui-binding.md: MVU/message-floor and UI lifecycle contract.

Keep looking

Skills are one crate of 613,297. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.