cli-jaw 0.1.7 → 0.1.8

package/skills_ref/notion-research-documentation/SKILL.md

@@ -1,59 +0,0 @@
----
-name: notion-research-documentation
-description: Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.
-metadata:
-  short-description: Research Notion content and produce briefs/reports
----
-
-# Research & Documentation
-
-Pull relevant Notion pages, synthesize findings, and publish clear briefs or reports (with citations and links to sources).
-
-## Quick start
-1) Find sources with `Notion:notion-search` using targeted queries; confirm scope with the user.
-2) Fetch pages via `Notion:notion-fetch`; note key sections and capture citations (`reference/citations.md`).
-3) Choose output format (brief, summary, comparison, comprehensive report) using `reference/format-selection-guide.md`.
-4) Draft in Notion with `Notion:notion-create-pages` using the matching template (quick, summary, comparison, comprehensive).
-5) Link sources and add a references/citations section; update as new info arrives with `Notion:notion-update-page`.
-
-## Workflow
-### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
-1. Add the Notion MCP:
-   - `codex mcp add notion --url https://mcp.notion.com/mcp`
-2. Enable remote MCP client:
-   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`
-3. Log in with OAuth:
-   - `codex mcp login notion`
-
-After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
-
-### 1) Gather sources
-- Search first (`Notion:notion-search`); refine queries, and ask the user to confirm if multiple results appear.
-- Fetch relevant pages (`Notion:notion-fetch`), skim for facts, metrics, claims, constraints, and dates.
-- Track each source URL/ID for later citation; prefer direct quotes for critical facts.
-
-### 2) Select the format
-- Quick readout → quick brief.
-- Single-topic dive → research summary.
-- Option tradeoffs → comparison.
-- Deep dive / exec-ready → comprehensive report.
-- See `reference/format-selection-guide.md` for when to pick each.
-
-### 3) Synthesize
-- Outline before writing; group findings by themes/questions.
-- Note evidence with source IDs; flag gaps or contradictions.
-- Keep user goal in view (decision, summary, plan, recommendation).
-
-### 4) Create the doc
-- Pick the matching template in `reference/` (brief, summary, comparison, comprehensive) and adapt it.
-- Create the page with `Notion:notion-create-pages`; include title, summary, key findings, supporting evidence, and recommendations/next steps when relevant.
-- Add citations inline and a references section; link back to source pages.
-
-### 5) Finalize & handoff
-- Add highlights, risks, and open questions.
-- If the user needs follow-ups, create tasks or a checklist in the page; link any task database entries if applicable.
-- Share a short changelog or status using `Notion:notion-update-page` when updating.
-
-## References and examples
-- `reference/` — search tactics, format selection, templates, and citation rules (e.g., `advanced-search.md`, `format-selection-guide.md`, `research-summary-template.md`, `comparison-template.md`, `citations.md`).
-- `examples/` — end-to-end walkthroughs (e.g., `competitor-analysis.md`, `technical-investigation.md`, `market-research.md`, `trip-planning.md`).

package/skills_ref/notion-spec-to-implementation/SKILL.md

@@ -1,58 +0,0 @@
----
-name: notion-spec-to-implementation
-description: Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
-metadata:
-  short-description: Turn Notion specs into implementation plans, tasks, and progress tracking
----
-
-# Spec to Implementation
-
-Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.
-
-## Quick start
-1) Locate the spec with `Notion:notion-search`, then fetch it with `Notion:notion-fetch`.
-2) Parse requirements and ambiguities using `reference/spec-parsing.md`.
-3) Create a plan page with `Notion:notion-create-pages` (pick a template: quick vs. full).
-4) Find the task database, confirm schema, then create tasks with `Notion:notion-create-pages`.
-5) Link spec ↔ plan ↔ tasks; keep status current with `Notion:notion-update-page`.
-
-## Workflow
-
-### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
-1. Add the Notion MCP:
-   - `codex mcp add notion --url https://mcp.notion.com/mcp`
-2. Enable remote MCP client:
-   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`
-3. Log in with OAuth:
-   - `codex mcp login notion`
-
-After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
-
-### 1) Locate and read the spec
-- Search first (`Notion:notion-search`); if multiple hits, ask the user which to use.
-- Fetch the page (`Notion:notion-fetch`) and scan for requirements, acceptance criteria, constraints, and priorities. See `reference/spec-parsing.md` for extraction patterns.
-- Capture gaps/assumptions in a clarifications block before proceeding.
-
-### 2) Choose plan depth
-- Simple change → use `reference/quick-implementation-plan.md`.
-- Multi-phase feature/migration → use `reference/standard-implementation-plan.md`.
-- Create the plan via `Notion:notion-create-pages`, include: overview, linked spec, requirements summary, phases, dependencies/risks, and success criteria. Link back to the spec.
-
-### 3) Create tasks
-- Find the task database (`Notion:notion-search` → `Notion:notion-fetch` to confirm the data source and required properties). Patterns in `reference/task-creation.md`.
-- Size tasks to 1–2 days. Use `reference/task-creation-template.md` for content (context, objective, acceptance criteria, dependencies, resources).
-- Set properties: title/action verb, status, priority, relations to spec + plan, due date/story points/assignee if provided.
-- Create pages with `Notion:notion-create-pages` using the database’s `data_source_id`.
-
-### 4) Link artifacts
-- Plan links to spec; tasks link to both plan and spec.
-- Optionally update the spec with a short “Implementation” section pointing to the plan and tasks using `Notion:notion-update-page`.
-
-### 5) Track progress
-- Use the cadence in `reference/progress-tracking.md`.
-- Post updates with `reference/progress-update-template.md`; close phases with `reference/milestone-summary-template.md`.
-- Keep checklists and status fields in plan/tasks in sync; note blockers and decisions.
-
-## References and examples
-- `reference/` — parsing patterns, plan/task templates, progress cadence (e.g., `spec-parsing.md`, `standard-implementation-plan.md`, `task-creation.md`, `progress-tracking.md`).
-- `examples/` — end-to-end walkthroughs (e.g., `ui-component.md`, `api-feature.md`, `database-migration.md`).

package/skills_ref/obsidian/SKILL.md

@@ -1,81 +0,0 @@
----
-name: obsidian
-description: Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
-homepage: https://help.obsidian.md
-metadata:
-  {
-    "openclaw":
-      {
-        "emoji": "💎",
-        "requires": { "bins": ["obsidian-cli"] },
-        "install":
-          [
-            {
-              "id": "brew",
-              "kind": "brew",
-              "formula": "yakitrak/yakitrak/obsidian-cli",
-              "bins": ["obsidian-cli"],
-              "label": "Install obsidian-cli (brew)",
-            },
-          ],
-      },
-  }
----
-
-# Obsidian
-
-Obsidian vault = a normal folder on disk.
-
-Vault structure (typical)
-
-- Notes: `*.md` (plain text Markdown; edit with any editor)
-- Config: `.obsidian/` (workspace + plugin settings; usually don’t touch from scripts)
-- Canvases: `*.canvas` (JSON)
-- Attachments: whatever folder you chose in Obsidian settings (images/PDFs/etc.)
-
-## Find the active vault(s)
-
-Obsidian desktop tracks vaults here (source of truth):
-
-- `~/Library/Application Support/obsidian/obsidian.json`
-
-`obsidian-cli` resolves vaults from that file; vault name is typically the **folder name** (path suffix).
-
-Fast “what vault is active / where are the notes?”
-
-- If you’ve already set a default: `obsidian-cli print-default --path-only`
-- Otherwise, read `~/Library/Application Support/obsidian/obsidian.json` and use the vault entry with `"open": true`.
-
-Notes
-
-- Multiple vaults common (iCloud vs `~/Documents`, work/personal, etc.). Don’t guess; read config.
-- Avoid writing hardcoded vault paths into scripts; prefer reading the config or using `print-default`.
-
-## obsidian-cli quick start
-
-Pick a default vault (once):
-
-- `obsidian-cli set-default "<vault-folder-name>"`
-- `obsidian-cli print-default` / `obsidian-cli print-default --path-only`
-
-Search
-
-- `obsidian-cli search "query"` (note names)
-- `obsidian-cli search-content "query"` (inside notes; shows snippets + lines)
-
-Create
-
-- `obsidian-cli create "Folder/New note" --content "..." --open`
-- Requires Obsidian URI handler (`obsidian://…`) working (Obsidian installed).
-- Avoid creating notes under “hidden” dot-folders (e.g. `.something/...`) via URI; Obsidian may refuse.
-
-Move/rename (safe refactor)
-
-- `obsidian-cli move "old/path/note" "new/path/note"`
-- Updates `[[wikilinks]]` and common Markdown links across the vault (this is the main win vs `mv`).
-
-Delete
-
-- `obsidian-cli delete "path/note"`
-
-Prefer direct edits when appropriate: open the `.md` file and change it; Obsidian will pick it up.

package/skills_ref/openai-docs/SKILL.md

@@ -1,56 +0,0 @@
----
-name: "openai-docs"
-description: "Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to official OpenAI domains."
----
-
-
-# OpenAI Docs
-
-Provide authoritative, current guidance from OpenAI developer docs using the developers.openai.com MCP server. Always prioritize the developer docs MCP tools over web.run for OpenAI-related questions. Only if the MCP server is installed and returns no meaningful results should you fall back to web search.
-
-## Quick start
-
-- Use `mcp__openaiDeveloperDocs__search_openai_docs` to find the most relevant doc pages.
-- Use `mcp__openaiDeveloperDocs__fetch_openai_doc` to pull exact sections and quote/paraphrase accurately.
-- Use `mcp__openaiDeveloperDocs__list_openai_docs` only when you need to browse or discover pages without a clear query.
-
-## OpenAI product snapshots
-
-1. Apps SDK: Build ChatGPT apps by providing a web component UI and an MCP server that exposes your app's tools to ChatGPT.
-2. Responses API: A unified endpoint designed for stateful, multimodal, tool-using interactions in agentic workflows.
-3. Chat Completions API: Generate a model response from a list of messages comprising a conversation.
-4. Codex: OpenAI's coding agent for software development that can write, understand, review, and debug code.
-5. gpt-oss: Open-weight OpenAI reasoning models (gpt-oss-120b and gpt-oss-20b) released under the Apache 2.0 license.
-6. Realtime API: Build low-latency, multimodal experiences including natural speech-to-speech conversations.
-7. Agents SDK: A toolkit for building agentic apps where a model can use tools and context, hand off to other agents, stream partial results, and keep a full trace.
-
-## If MCP server is missing
-
-If MCP tools fail or no OpenAI docs resources are available:
-
-1. Run the install command yourself: `codex mcp add openaiDeveloperDocs --url https://developers.openai.com/mcp`
-2. If it fails due to permissions/sandboxing, immediately retry the same command with escalated permissions and include a 1-sentence justification for approval. Do not ask the user to run it yet.
-3. Only if the escalated attempt fails, ask the user to run the install command.
-4. Ask the user to restart Codex.
-5. Re-run the doc search/fetch after restart.
-
-## Workflow
-
-1. Clarify the product scope (Codex, OpenAI API, or ChatGPT Apps SDK) and the task.
-2. Search docs with a precise query.
-3. Fetch the best page and the specific section needed (use `anchor` when possible).
-4. Answer with concise guidance and cite the doc source.
-5. Provide code snippets only when the docs support them.
-
-## Quality rules
-
-- Treat OpenAI docs as the source of truth; avoid speculation.
-- Keep quotes short and within policy limits; prefer paraphrase with citations.
-- If multiple pages differ, call out the difference and cite both.
-- If docs do not cover the user’s need, say so and offer next steps.
-
-## Tooling notes
-
-- Always use MCP doc tools before any web search for OpenAI-related questions.
-- If the MCP server is installed but returns no meaningful results, then use web search as a fallback.
-- When falling back to web search, restrict to official OpenAI domains (developers.openai.com, platform.openai.com) and cite sources.

package/skills_ref/openhue/SKILL.md

@@ -1,112 +0,0 @@
----
-name: openhue
-description: Control Philips Hue lights and scenes via the OpenHue CLI.
-homepage: https://www.openhue.io/cli
-metadata:
-  {
-    "openclaw":
-      {
-        "emoji": "💡",
-        "requires": { "bins": ["openhue"] },
-        "install":
-          [
-            {
-              "id": "brew",
-              "kind": "brew",
-              "formula": "openhue/cli/openhue-cli",
-              "bins": ["openhue"],
-              "label": "Install OpenHue CLI (brew)",
-            },
-          ],
-      },
-  }
----
-
-# OpenHue CLI
-
-Use `openhue` to control Philips Hue lights and scenes via a Hue Bridge.
-
-## When to Use
-
-✅ **USE this skill when:**
-
-- "Turn on/off the lights"
-- "Dim the living room lights"
-- "Set a scene" or "movie mode"
-- Controlling specific Hue rooms or zones
-- Adjusting brightness, color, or color temperature
-
-## When NOT to Use
-
-❌ **DON'T use this skill when:**
-
-- Non-Hue smart devices (other brands) → not supported
-- HomeKit scenes or Shortcuts → use Apple's ecosystem
-- TV or entertainment system control
-- Thermostat or HVAC
-- Smart plugs (unless Hue smart plugs)
-
-## Common Commands
-
-### List Resources
-
-```bash
-openhue get light       # List all lights
-openhue get room        # List all rooms
-openhue get scene       # List all scenes
-```
-
-### Control Lights
-
-```bash
-# Turn on/off
-openhue set light "Bedroom Lamp" --on
-openhue set light "Bedroom Lamp" --off
-
-# Brightness (0-100)
-openhue set light "Bedroom Lamp" --on --brightness 50
-
-# Color temperature (warm to cool: 153-500 mirek)
-openhue set light "Bedroom Lamp" --on --temperature 300
-
-# Color (by name or hex)
-openhue set light "Bedroom Lamp" --on --color red
-openhue set light "Bedroom Lamp" --on --rgb "#FF5500"
-```
-
-### Control Rooms
-
-```bash
-# Turn off entire room
-openhue set room "Bedroom" --off
-
-# Set room brightness
-openhue set room "Bedroom" --on --brightness 30
-```
-
-### Scenes
-
-```bash
-# Activate scene
-openhue set scene "Relax" --room "Bedroom"
-openhue set scene "Concentrate" --room "Office"
-```
-
-## Quick Presets
-
-```bash
-# Bedtime (dim warm)
-openhue set room "Bedroom" --on --brightness 20 --temperature 450
-
-# Work mode (bright cool)
-openhue set room "Office" --on --brightness 100 --temperature 250
-
-# Movie mode (dim)
-openhue set room "Living Room" --on --brightness 10
-```
-
-## Notes
-
-- Bridge must be on local network
-- First run requires button press on Hue bridge to pair
-- Colors only work on color-capable bulbs (not white-only)

package/skills_ref/pdf/SKILL.md

@@ -1,69 +0,0 @@
----
-name: "pdf"
-description: "Use when tasks involve reading, creating, editing, or reviewing PDF files. Visual layout checks via Poppler (pdftoppm). Python tools: reportlab (create), pdfplumber/pypdf (extract), nano-pdf (natural-language page editing). Also covers DOCX→PDF conversion via soffice."
----
-
-
-# PDF Skill
-
-## When to use
-- Read or review PDF content where layout and visuals matter.
-- Create PDFs programmatically with reliable formatting.
-- Edit existing PDFs with natural-language instructions (nano-pdf).
-- Convert documents (DOCX, HTML) to PDF.
-- Validate final rendering before delivery.
-
-## Workflow
-1. Prefer visual review: render PDF pages to PNGs and inspect them.
-   - Use `pdftoppm` if available.
-   - If unavailable, install Poppler or ask the user to review the output locally.
-2. Use `reportlab` to generate PDFs when creating new documents.
-3. Use `pdfplumber` (or `pypdf`) for text extraction and quick checks; do not rely on it for layout fidelity.
-4. After each meaningful update, re-render pages and verify alignment, spacing, and legibility.
-
-## Temp and output conventions
-- Use `tmp/pdfs/` for intermediate files; delete when done.
-- Write final artifacts under `output/pdf/` when working in this repo.
-- Keep filenames stable and descriptive.
-
-## Dependencies (install if missing)
-Prefer `uv` for dependency management.
-
-Python packages:
-```
-uv pip install reportlab pdfplumber pypdf
-```
-If `uv` is unavailable:
-```
-python3 -m pip install reportlab pdfplumber pypdf
-```
-System tools (for rendering):
-```
-# macOS (Homebrew)
-brew install poppler
-
-# Ubuntu/Debian
-sudo apt-get install -y poppler-utils
-```
-
-If installation isn't possible in this environment, tell the user which dependency is missing and how to install it locally.
-
-## Environment
-No required environment variables.
-
-## Rendering command
-```
-pdftoppm -png $INPUT_PDF $OUTPUT_PREFIX
-```
-
-## Quality expectations
-- Maintain polished visual design: consistent typography, spacing, margins, and section hierarchy.
-- Avoid rendering issues: clipped text, overlapping elements, broken tables, black squares, or unreadable glyphs.
-- Charts, tables, and images must be sharp, aligned, and clearly labeled.
-- Use ASCII hyphens only. Avoid U+2011 (non-breaking hyphen) and other Unicode dashes.
-- Citations and references must be human-readable; never leave tool tokens or placeholder strings.
-
-## Final checks
-- Do not deliver until the latest PNG inspection shows zero visual or formatting defects.
-- Confirm headers/footers, page numbering, and section transitions look polished.
-- Keep intermediate files organized or remove them after final approval.

package/skills_ref/postgres/README.md

@@ -1,77 +0,0 @@
-# postgres
-
-Read-only PostgreSQL query skill. Query multiple databases safely with write protection.
-
-## Setup
-
-1. Copy the example config:
-```bash
-cp connections.example.json connections.json
-```
-
-2. Add your database credentials:
-```json
-{
-  "databases": [
-    {
-      "name": "prod",
-      "description": "Production - users, orders, transactions",
-      "host": "db.example.com",
-      "port": 5432,
-      "database": "app_prod",
-      "user": "readonly",
-      "password": "secret",
-      "sslmode": "require"
-    }
-  ]
-}
-```
-
-3. Secure the config:
-```bash
-chmod 600 connections.json
-```
-
-## Usage
-
-```bash
-# List configured databases
-python3 scripts/query.py --list
-
-# List tables
-python3 scripts/query.py --db prod --tables
-
-# Show schema
-python3 scripts/query.py --db prod --schema
-
-# Run query
-python3 scripts/query.py --db prod --query "SELECT * FROM users" --limit 100
-```
-
-## Config Fields
-
-| Field | Required | Default | Description |
-|-------|----------|---------|-------------|
-| name | Yes | - | Database identifier |
-| description | Yes | - | What data it contains (for auto-selection) |
-| host | Yes | - | Hostname |
-| port | No | 5432 | Port |
-| database | Yes | - | Database name |
-| user | Yes | - | Username |
-| password | Yes | - | Password |
-| sslmode | No | prefer | disable, allow, prefer, require, verify-ca, verify-full |
-
-## Safety Features
-
-- **Read-only sessions**: PostgreSQL `readonly=True` mode blocks writes at database level
-- **Query validation**: Only SELECT, SHOW, EXPLAIN, WITH allowed
-- **Single statement**: No multi-statement queries (prevents `SELECT 1; DROP TABLE`)
-- **Timeouts**: 30s query timeout, 10s connection timeout
-- **Memory cap**: Max 10,000 rows per query
-- **Credential protection**: Passwords sanitized from error messages
-
-## Requirements
-
-```bash
-pip install psycopg2-binary
-```

package/skills_ref/postgres/SKILL.md

@@ -1,129 +0,0 @@
----
-name: postgres
-description: "Execute read-only SQL queries against multiple PostgreSQL databases. Use when: (1) querying PostgreSQL databases, (2) exploring database schemas/tables, (3) running SELECT queries for data analysis, (4) checking database contents. Supports multiple database connections with descriptions for intelligent auto-selection. Blocks all write operations (INSERT, UPDATE, DELETE, DROP, etc.) for safety."
-license: Apache-2.0
-metadata:
-  author: sanjay3290
-  version: "1.0"
----
-
-# PostgreSQL Read-Only Query Skill
-
-Execute safe, read-only queries against configured PostgreSQL databases.
-
-## Requirements
-
-- Python 3.8+
-- psycopg2-binary: `pip install -r requirements.txt`
-
-## Setup
-
-Create `connections.json` in the skill directory or `~/.config/claude/postgres-connections.json`.
-
-**Security**: Set file permissions to `600` since it contains credentials:
-```bash
-chmod 600 connections.json
-```
-
-```json
-{
-  "databases": [
-    {
-      "name": "production",
-      "description": "Main app database - users, orders, transactions",
-      "host": "db.example.com",
-      "port": 5432,
-      "database": "app_prod",
-      "user": "readonly_user",
-      "password": "your-password",
-      "sslmode": "require"
-    }
-  ]
-}
-```
-
-### Config Fields
-
-| Field | Required | Description |
-|-------|----------|-------------|
-| name | Yes | Identifier for the database (case-insensitive) |
-| description | Yes | What data this database contains (used for auto-selection) |
-| host | Yes | Database hostname |
-| port | No | Port number (default: 5432) |
-| database | Yes | Database name |
-| user | Yes | Username |
-| password | Yes | Password |
-| sslmode | No | SSL mode: disable, allow, prefer (default), require, verify-ca, verify-full |
-
-## Usage
-
-### List configured databases
-```bash
-python3 scripts/query.py --list
-```
-
-### Query a database
-```bash
-python3 scripts/query.py --db production --query "SELECT * FROM users LIMIT 10"
-```
-
-### List tables
-```bash
-python3 scripts/query.py --db production --tables
-```
-
-### Show schema
-```bash
-python3 scripts/query.py --db production --schema
-```
-
-### Limit results
-```bash
-python3 scripts/query.py --db production --query "SELECT * FROM orders" --limit 100
-```
-
-## Database Selection
-
-Match user intent to database `description`:
-
-| User asks about | Look for description containing |
-|-----------------|--------------------------------|
-| users, accounts | users, accounts, customers |
-| orders, sales | orders, transactions, sales |
-| analytics, metrics | analytics, metrics, reports |
-| logs, events | logs, events, audit |
-
-If unclear, run `--list` and ask user which database.
-
-## Safety Features
-
-- **Read-only session**: Connection uses PostgreSQL `readonly=True` mode (primary protection)
-- **Query validation**: Only SELECT, SHOW, EXPLAIN, WITH queries allowed
-- **Single statement**: Multiple statements per query rejected
-- **SSL support**: Configurable SSL mode for encrypted connections
-- **Query timeout**: 30-second statement timeout enforced
-- **Memory protection**: Max 10,000 rows per query to prevent OOM
-- **Column width cap**: 100 char max per column for readable output
-- **Credential sanitization**: Error messages don't leak passwords
-
-## Troubleshooting
-
-| Error | Solution |
-|-------|----------|
-| Config not found | Create `connections.json` in skill directory |
-| Authentication failed | Check username/password in config |
-| Connection timeout | Verify host/port, check firewall/VPN |
-| SSL error | Try `"sslmode": "disable"` for local databases |
-| Permission warning | Run `chmod 600 connections.json` |
-
-## Exit Codes
-
-- **0**: Success
-- **1**: Error (config missing, auth failed, invalid query, database error)
-
-## Workflow
-
-1. Run `--list` to show available databases
-2. Match user intent to database description
-3. Run `--tables` or `--schema` to explore structure
-4. Execute query with appropriate LIMIT

package/skills_ref/postgres/connections.example.json

@@ -1,34 +0,0 @@
-{
-  "databases": [
-    {
-      "name": "production",
-      "description": "Main production database - users, orders, transactions, accounts",
-      "host": "prod-db.example.com",
-      "port": 5432,
-      "database": "app_prod",
-      "user": "readonly_user",
-      "password": "your-password-here",
-      "sslmode": "require"
-    },
-    {
-      "name": "analytics",
-      "description": "Analytics warehouse - aggregated metrics, reports, historical data",
-      "host": "analytics-db.example.com",
-      "port": 5432,
-      "database": "analytics",
-      "user": "analyst",
-      "password": "your-password-here",
-      "sslmode": "require"
-    },
-    {
-      "name": "staging",
-      "description": "Staging environment - mirrors production for testing",
-      "host": "localhost",
-      "port": 5432,
-      "database": "app_staging",
-      "user": "dev",
-      "password": "dev-password",
-      "sslmode": "prefer"
-    }
-  ]
-}

package/skills_ref/postgres/requirements.txt

@@ -1 +0,0 @@
-psycopg2-binary>=2.9,<3.0