Skip to content
TrustedSkillsbeta
Back to all skills

Postgres Patterns

Checked
affaan-m·vlatest·database·MIT

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

Repository

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 affaan-m/ecc --skill postgres-patterns -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

affaan-m

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 affaan-m/everything-claude-code at d3b8a3e908.

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

Commit
d3b8a3e908
Manifest
skills/postgres-patterns/SKILL.md
Scanned
3 files, 405 lines
Copies in repo
3 — all of them scanned
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

The postgres-patterns skill provides a collection of common PostgreSQL patterns and best practices, including query optimization techniques, schema design strategies, indexing methods, and advanced SQL features. It helps users write more efficient queries and manage database performance effectively.

When to use it

  • When optimizing slow-running SQL queries for better performance.
  • When designing or refining the schema of a PostgreSQL database.
  • When implementing advanced features like window functions or JSONB operations.
  • When troubleshooting common issues such as locking, deadlocks, or inefficient joins.

Key capabilities

  • Query optimization strategies
  • Indexing best practices
  • Schema design patterns
  • Advanced SQL techniques (e.g., CTEs, window functions)
  • Performance tuning tips

Example prompts

  • "How can I optimize this slow PostgreSQL query?"
  • "What are the best indexing practices for a high-write table in PostgreSQL?"
  • "Can you explain how to use JSONB effectively in PostgreSQL?"

Tips & gotchas

  • Ensure your PostgreSQL version is up-to-date to take full advantage of modern features.
  • Patterns may vary based on workload and data size; always test changes in a staging environment before applying them to production.