postgresql

Design Community

Skill notes

When to Use This Skill

This skill should be triggered when: Working with postgresql Asking about postgresql features or APIs Implementing postgresql solutions Debugging postgresql code

Common Patterns

Pattern 1: 32.1. Database Connection Control Functions # 32.1.1.

Example Code Patterns

Example 1 (javascript): Example 2 (javascript):

Reference Files

This skill includes comprehensive documentation in references/: getting_started.md - Getting Started documentation sql.md - Sql documentation Use view to read specific reference files when detailed information is needed.

For Beginners

Start with the getting_started or tutorials reference files for foundational concepts.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
84 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Heavy
Setup complexity
Manual integration
External API key
Required · Vendor-specific
Operating systems
Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview postgresql-tomevault-io.preview
# For Code Examples

The quick reference section above contains common patterns extracted from the official docs.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.