Run any Skill in Manus with one click

check-updates

Stars5

Forks0

UpdatedApril 16, 2026 at 19:45

Check for skills-for-postgres marketplace updates at session start. Compares local version against GitHub releases and shows changelog if updates are available. Use when the user wants to: (1) check for skill updates, (2) see what's new in skills-for-postgres, (3) verify current version. Triggers: "check for updates", "am I up to date", "what version", "update skills", "show changelog".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

raunakjhawar

raunakjhawar/skills-for-postgres

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	check-updates
description	Check for skills-for-postgres marketplace updates at session start. Compares local version against GitHub releases and shows changelog if updates are available. Use when the user wants to: (1) check for skill updates, (2) see what's new in skills-for-postgres, (3) verify current version. Triggers: "check for updates", "am I up to date", "what version", "update skills", "show changelog".

Check for Updates

This skill checks for updates to the skills-for-postgres marketplace at the start of each session.

When to Run

Run this check once per week when any skills-for-postgres skill is first invoked. Skip if already checked within the last 7 days.

Session State

The update check marker is stored in a persistent, user-level directory:

~/.config/postgres-skills/last-update-check.json

This file contains a JSON object with the UTC date (YYYY-MM-DD) of the last update check:

{
  "postgres-skills": "2026-03-23"
}

Before checking, read ~/.config/postgres-skills/last-update-check.json:

If the file exists and the date is within the last 7 days, skip the check.
If the file is missing or the date is more than 7 days old, run the update check.

Update Check Procedure

Step 1: Get Local Version

Read the version field from the local package.json file.

Step 2: Fetch Latest Version

Method A — Git CLI (preferred)

git fetch origin main --quiet
git show origin/main:package.json

Method B — GitHub API

Use the GitHub API to read the remote package.json.

Step 3: Compare Versions

If the remote version is newer than the local version:

Show the version difference
Display the CHANGELOG entries between versions
Provide update instructions

Step 4: Update Timestamp

Write the current UTC date to the check file:

# Linux/macOS
mkdir -p ~/.config/postgres-skills
echo "{\"postgres-skills\": \"$(date -u +%Y-%m-%d)\"}" > ~/.config/postgres-skills/last-update-check.json

# Windows (PowerShell)
$dir = "$env:USERPROFILE\.config\postgres-skills"
New-Item -ItemType Directory -Path $dir -Force | Out-Null
@{ "postgres-skills" = (Get-Date).ToUniversalTime().ToString("yyyy-MM-dd") } | ConvertTo-Json | Set-Content "$dir\last-update-check.json"

More from this repository

same repository

postgres-troubleshooting-cli

raunakjhawar/skills-for-postgres

Diagnose and resolve Azure Database for PostgreSQL Flexible Server issues via CLI. Use when the user wants to: (1) troubleshoot connection failures or timeouts, (2) identify and resolve lock contention or deadlocks, (3) find and terminate long-running or blocking queries, (4) diagnose high CPU, memory, or IO usage, (5) detect and fix table or index bloat, (6) debug replication lag on read replicas, (7) analyze PostgreSQL error logs, (8) investigate autovacuum issues, (9) resolve Azure-specific server health problems. Triggers: "postgres not connecting", "connection timeout", "deadlock postgres", "blocked queries", "long running query", "kill query postgres", "high CPU postgres", "table bloat", "index bloat", "replication lag", "autovacuum not running", "postgres error", "troubleshoot postgres", "debug postgres", "postgres slow", "out of connections", "too many connections", "lock wait timeout".

2026-04-175

postgres-admin-cli

raunakjhawar/skills-for-postgres

Manage Azure Database for PostgreSQL Flexible Server infrastructure via Azure CLI. Use when the user wants to: (1) provision or configure a Flexible Server, (2) manage high availability and read replicas including cascading replicas and virtual endpoints, (3) configure private networking with VNet integration, Private DNS zones, and NSG rules, (4) set up Entra ID authentication, (5) manage backups including geo-redundant backup, on-demand backup, point-in-time restore, geo-restore, and long-term retention, (6) plan BCDR and disaster recovery with cross-region replicas, (7) tune server parameters, (8) monitor server health and replication metrics, (9) manage extensions and major version upgrades. Triggers: "create postgres server", "configure HA", "add firewall rule", "setup entra auth", "restore postgres", "server parameters", "postgres backup", "read replica", "geo-restore", "upgrade postgres version", "enable pgbouncer", "postgres monitoring", "postgres security", "vnet integration postgres", "private endpo

2026-04-175

postgres-authoring-cli

raunakjhawar/skills-for-postgres

Execute authoring SQL (DDL, DML, schema design, stored procedures, functions, triggers, indexing, partitioning) against Azure Database for PostgreSQL Flexible Server from agentic CLI environments. Use when the user wants to: (1) create/alter/drop tables, (2) insert/update/delete data, (3) create stored procedures or functions in PL/pgSQL, (4) design indexes and partitions, (5) create triggers, (6) manage constraints, (7) bulk load data with COPY. Triggers: "create table in postgres", "insert data", "create function", "create index", "alter table", "upsert postgres", "create trigger", "partition table", "bulk load postgres", "stored procedure postgres", "COPY INTO postgres".

2026-04-175

postgres-extensions-cli

raunakjhawar/skills-for-postgres

Discover, install, configure, and use PostgreSQL extensions on Azure Database for PostgreSQL Flexible Server via CLI. Use when the user wants to: (1) list available extensions, (2) install or upgrade extensions, (3) use pg_stat_statements for query profiling, (4) schedule jobs with pg_cron, (5) use PostGIS for geospatial queries, (6) use pg_trgm for fuzzy text search, (7) set up auto_explain for automatic plan logging, (8) use pg_partman for automated partition management, (9) use pg_repack for online table repacking, (10) use azure_ai for AI/ML integration, (11) use azure_storage for cloud storage access, (12) use pg_diskann for scalable vector search, (13) set up pgaudit for compliance auditing, (14) use timescaledb for time-series data, (15) use hypopg for hypothetical index testing, (16) use pg_hint_plan to control query plans, (17) use wal2json for change data capture, (18) manage extension lifecycle and dependencies. Triggers: "postgres extension", "install extension", "available extensions", "pg_stat_s

2026-04-175

pgvector-authoring-cli

raunakjhawar/skills-for-postgres

Set up and use pgvector and pg_diskann for vector similarity search on Azure Database for PostgreSQL Flexible Server. Use when the user wants to: (1) install and configure pgvector or pg_diskann, (2) create tables with vector columns, (3) build vector indexes (IVFFlat, HNSW, DiskANN), (4) run similarity search queries, (5) implement RAG patterns, (6) store and query embeddings from Microsoft Foundry / Azure AI models, (7) choose between HNSW and DiskANN for large-scale vector workloads. Triggers: "pgvector", "vector search", "similarity search", "embeddings postgres", "RAG postgres", "vector index", "HNSW", "IVFFlat", "cosine similarity", "nearest neighbor postgres", "AI postgres", "semantic search postgres", "pg_diskann", "DiskANN", "diskann index", "scalable vector search".

2026-04-165

postgres-consumption-cli

raunakjhawar/skills-for-postgres

Execute read-only SQL queries against Azure Database for PostgreSQL Flexible Server via CLI. Default skill for any PostgreSQL data query (SELECT, aggregation, schema exploration, performance analysis). Use when the user wants to: (1) query PostgreSQL data, (2) explore schemas and columns, (3) analyze query performance with EXPLAIN, (4) monitor active connections and locks, (5) export query results to CSV, (6) discover table sizes and statistics. Triggers: "query postgres", "select from", "explore schema", "show tables", "describe table", "explain query", "postgres performance", "export CSV", "count rows", "list columns", "database size", "active queries", "slow queries".

2026-04-165

name	check-updates
description	Check for skills-for-postgres marketplace updates at session start. Compares local version against GitHub releases and shows changelog if updates are available. Use when the user wants to: (1) check for skill updates, (2) see what's new in skills-for-postgres, (3) verify current version. Triggers: "check for updates", "am I up to date", "what version", "update skills", "show changelog".

Check for Updates

This skill checks for updates to the skills-for-postgres marketplace at the start of each session.

When to Run

Run this check once per week when any skills-for-postgres skill is first invoked. Skip if already checked within the last 7 days.

Session State

The update check marker is stored in a persistent, user-level directory:

~/.config/postgres-skills/last-update-check.json

This file contains a JSON object with the UTC date (YYYY-MM-DD) of the last update check:

{
  "postgres-skills": "2026-03-23"
}

Before checking, read ~/.config/postgres-skills/last-update-check.json:

If the file exists and the date is within the last 7 days, skip the check.
If the file is missing or the date is more than 7 days old, run the update check.

Update Check Procedure

Step 1: Get Local Version

Read the version field from the local package.json file.

Step 2: Fetch Latest Version

Method A — Git CLI (preferred)

git fetch origin main --quiet
git show origin/main:package.json

Method B — GitHub API

Use the GitHub API to read the remote package.json.

Step 3: Compare Versions

If the remote version is newer than the local version:

Show the version difference
Display the CHANGELOG entries between versions
Provide update instructions

Step 4: Update Timestamp

Write the current UTC date to the check file:

# Linux/macOS
mkdir -p ~/.config/postgres-skills
echo "{\"postgres-skills\": \"$(date -u +%Y-%m-%d)\"}" > ~/.config/postgres-skills/last-update-check.json

# Windows (PowerShell)
$dir = "$env:USERPROFILE\.config\postgres-skills"
New-Item -ItemType Directory -Path $dir -Force | Out-Null
@{ "postgres-skills" = (Get-Date).ToUniversalTime().ToString("yyyy-MM-dd") } | ConvertTo-Json | Set-Content "$dir\last-update-check.json"