Menü
How to update and publish pgdbm skills for Claude Code users
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
How to release a new pgdbm library version to PyPI
Use before implementing pgdbm patterns to avoid common mistakes - provides rationalization table and red flags that prevent pool multiplication, schema errors, and template syntax violations
Use when writing tests for pgdbm-based code - provides fixture selection decision tree and complete usage patterns without needing testing docs
Use when deciding which pgdbm pattern to use (standalone, dual-mode library, or shared pool) - provides decision tree based on deployment context without requiring doc exploration
Use when implementing pgdbm database operations - provides complete AsyncDatabaseManager and DatabaseConfig API with all methods and parameters
Use when implementing shared connection pool for multiple services in same application - provides complete setup steps for FastAPI/multi-service apps without needing examples
| name | publish-skills |
| description | How to update and publish pgdbm skills for Claude Code users |
pgdbm provides skills for Claude Code via the juanre-ai-tools marketplace. This skill explains the structure and how to publish updates.
juanre-ai-tools (MARKETPLACE)
└── marketplace.json references:
└── juanre/pgdbm (GITHUB REPO)
├── skills/ ← Skills content lives here
│ ├── testing-database-code/SKILL.md
│ ├── common-mistakes/SKILL.md
│ ├── choosing-pattern/SKILL.md
│ └── ...
└── .claude-plugin/
└── plugin.json ← Version controls caching
Key points:
skills/ at repo root (NOT .claude/skills/).claude/skills/ is for LOCAL project skills (like this one).claude-plugin/plugin.json version determines when users get updatesSkills are in /skills/<skill-name>/SKILL.md:
skills/
├── choosing-pattern/SKILL.md
├── common-mistakes/SKILL.md
├── core-api-reference/SKILL.md
├── dual-mode-library/SKILL.md
├── migrations-api-reference/SKILL.md
├── shared-pool-pattern/SKILL.md
├── standalone-service/SKILL.md
├── testing-database-code/SKILL.md
└── using-pgdbm/SKILL.md
Critical: Users only get updates when the version changes.
# Check current version
cat .claude-plugin/plugin.json | grep version
# Edit to bump version
# "version": "0.2.1" → "version": "0.2.2"
Keep plugin version in sync with library version in pyproject.toml.
git add skills/ .claude-plugin/plugin.json
git commit -m "docs: update skills for X.Y.Z
- Description of skill changes
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>"
git push origin main
# Check version on GitHub
curl -s https://api.github.com/repos/juanre/pgdbm/contents/.claude-plugin/plugin.json | jq -r '.content' | base64 -d | grep version
Users subscribed to juanre-ai-tools marketplace get the pgdbm plugin.
Manual update:
claude plugin update pgdbm@juanre-ai-tools
Auto-update: Disabled by default for third-party marketplaces. Users can enable via /plugin → Marketplaces → Enable auto-update.
After pushing, test the update:
# Update plugin
claude plugin update pgdbm@juanre-ai-tools
# Verify new version cached
ls ~/.claude/plugins/cache/juanre-ai-tools/pgdbm/
# Check skill content
head -30 ~/.claude/plugins/cache/juanre-ai-tools/pgdbm/*/skills/testing-database-code/SKILL.md
Each skill needs YAML frontmatter:
---
name: skill-name
description: One-line description used for skill discovery
---
# Skill Title
## Overview
Brief explanation of what this skill covers.
## Content
The actual guidance...
The juanre-ai-tools marketplace.json has entries like:
{
"name": "pgdbm",
"source": {
"source": "github",
"repo": "juanre/pgdbm"
},
"description": "...",
"version": "1.0.0" ← This is the LISTING version, not the plugin version
}
The listing version (1.0.0) is independent of the plugin version. The plugin version in .claude-plugin/plugin.json is what matters for caching.
release skill