Skip to content
TrustedSkillsbeta
Back to all skills

Postgresql Table Design

Checked
wshobson·vlatest·database·MIT

Helps with PostgreSQL, design as part of working with databases and data persistence workflows.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add wshobson/agents --skill postgresql-table-design -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

wshobson

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned wshobson/agents at 46891e7e60.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
2 files, 280 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps design PostgreSQL tables by generating schema definitions based on user requirements. It supports defining columns, data types, constraints, and relationships between tables. The output is typically in SQL format, ready to be executed in a PostgreSQL environment.

When to use it

  • You need to create a new database schema from scratch.
  • You want to refine an existing table structure for better performance or normalization.
  • You're working on a project that requires multiple related tables with foreign key relationships.
  • You’re preparing a prototype and need quick, accurate SQL definitions.

Key capabilities

  • Generates normalized table schemas
  • Supports common PostgreSQL data types (e.g., VARCHAR, DATE, BOOLEAN)
  • Includes constraints like PRIMARY KEY, FOREIGN KEY, and UNIQUE
  • Handles relationships between tables

Example prompts

  • "Design a table for storing user information with email, name, and registration date."
  • "Create a normalized schema for an e-commerce system including users, products, and orders."
  • "Generate SQL to create a table for tracking blog posts with title, content, and author reference."

Tips & gotchas

  • Provide clear details about the data you want to store; vague prompts may lead to incomplete schemas.
  • Review generated SQL for compatibility with your specific PostgreSQL version.