Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add pproenca/dot-skills --skill relational-database-designgit clone --depth 1 https://github.com/pproenca/dot-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/pproenca/dot-skills/relational-database-design)<a href="https://agentmods.dev/skills/pproenca/dot-skills/relational-database-design"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/relational-database-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/pproenca/dot-skills/relational-database-design"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/relational-database-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00170 | $0.02226 |
| Opus 5 | $0.00085 | $0.01113 |
| Sonnet 5 | $0.00034 | $0.00445 |
| Haiku 4.5 | $0.00017 | $0.00223 |
Grade A, and why
relational-database-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Relational Database Design
A logical, RDBMS-agnostic method for designing sound relational databases — the decisions a schema forces and how a disciplined logical-design methodology settles them, written so an agent applies them while designing or reviewing a schema. Each rule names a specific wrong default it corrects; there is no rule for things the model already gets right.
The whole method produces the logical structure first — the tables, fields, keys, relationships, and integrity rules an organization's information requires — deliberately independent of any particular RDBMS product or physical/performance concern. Followed faithfully, it yields fully normalized tables without treating normalization as a separate back-end phase.
When to Apply
- Designing a new relational schema from requirements
- Reviewing or refactoring an existing schema for structural soundness
- Resolving repeating groups, multivalued/multipart fields, or redundant data
- Choosing candidate, primary, and foreign keys for a table
- Modeling one-to-one, one-to-many, many-to-many, or self-referencing relationships
- Deciding deletion rules (restrict, cascade, nullify, deny, set default) and participation constraints
- Deciding where a constraint belongs — field spec, relationship, validation table, or application
- Diagnosing a schema that duplicates, loses, or corrupts data
This skill covers logical design. It does not cover SQL dialects, indexing, partitioning, query tuning, or analytical/dimensional (star-schema) modeling — those are physical/implementation concerns handled after the logical design is sound.
Rule Categories
| # | Category | Prefix | Covers |
|---|---|---|---|
| 1 | Design Process & Requirements | proc- |
Design logically before choosing an RDBMS, follow the sequence, drive from mission + analysis, normalization is built in |
| 2 | Table Structure | tbl- |
One subject per table, the ideal table, no reference fields, minimal redundancy |
| 3 | Field Design | fld- |
The ideal field, single values, atomic fields, no stored calculations, clear names |
| 4 | Keys | key- |
Candidate key elements, one primary key per table, foreign keys mirror primary keys, stable non-sensitive keys |
| 5 | Relationships | rel- |
Junction tables for many-to-many, foreign-key placement, deletion rules, participation, self-referencing |
| 6 | Data Integrity, Rules & Views | intg- |
The four integrity levels, field specifications, database-vs-application rules, validation tables, views |
| 7 | Antipatterns | anti- |
Flat-file, spreadsheet-as-database, RDBMS-driven design, when bending the rules is defensible |
| 8 | Terminology | term- |
Data vs information, nulls, core relational vocabulary |
What ships with it
40 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- AGENTS.md 5.5 KB
- assets/templates/_template.md 694 B
- gotchas.md 82 B
- metadata.json 1.3 KB
- references/_sections.md 3.1 KB
- references/anti-bend-rules-only-deliberately.md 1.5 KB
- references/anti-flat-file-design.md 1.2 KB
- references/anti-rdbms-driven-design.md 1.3 KB
- references/anti-spreadsheet-as-database.md 1.3 KB
- references/fld-clear-singular-field-names.md 1.3 KB
- references/fld-derive-dont-store-calculated-values.md 1.4 KB
- references/fld-ideal-field-checklist.md 1.3 KB
- references/fld-keep-fields-atomic.md 1.4 KB
- references/fld-store-single-values-not-lists.md 1.6 KB
- references/intg-database-vs-application-rules.md 1.7 KB
- references/intg-field-specifications.md 1.4 KB
- references/intg-four-levels-of-data-integrity.md 1.5 KB
- references/intg-validation-tables-for-allowed-values.md 1.2 KB
- references/intg-views-for-derived-and-restricted-data.md 1.5 KB
- references/key-candidate-key-elements.md 1.5 KB
- references/key-foreign-key-mirrors-its-primary-key.md 1.5 KB
- references/key-one-primary-key-per-table.md 1.3 KB
- references/key-prefer-stable-non-sensitive-keys.md 1.4 KB
- references/proc-analyze-and-interview-before-designing.md 1.3 KB
- references/proc-design-logically-before-choosing-rdbms.md 2.1 KB
- references/proc-follow-the-design-sequence.md 1.8 KB
- references/proc-normalization-is-built-in.md 1.5 KB
- references/proc-start-from-mission-and-objectives.md 1.4 KB
- references/rel-deletion-rule-guards-orphans.md 1.5 KB
- references/rel-foreign-key-on-the-many-side.md 1.3 KB
- references/rel-junction-table-for-many-to-many.md 1.6 KB
- references/rel-participation-encodes-constraints.md 1.4 KB
- references/rel-self-referencing-relationships.md 1.3 KB
- references/tbl-ideal-table-checklist.md 1.3 KB
- references/tbl-minimize-redundant-data.md 1.3 KB
- references/tbl-no-reference-fields.md 1.6 KB
- references/tbl-one-subject-per-table.md 1.6 KB
- references/term-data-versus-information.md 1.2 KB
- references/term-null-is-unknown-not-zero.md 1.2 KB
- references/term-relational-vocabulary.md 1.8 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 114 lines · 170 tokens per session scan A d1bd4f39aad4
relational-database-design is a skill published in the GitHub repository pproenca/dot-skills (205 stars, last pushed 24d ago), licensed MIT. It adds 170 tokens to every session and 2,226 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…