Hologres Agent Skills

An interactive installer that distributes Hologres AI agent skills to various AI coding tools.

Included Skills

Note: All skills except hologres-cli depend on it as the foundational skill. SQL execution, GUC management, and data operations are performed through CLI commands. Install hologres-cli skill first.

Supported AI Tools

Claude Code, OpenClaw, Cursor, Codex, OpenCode, GitHub Copilot, Qoder, Trae

Quick Start

Install via uvx (Recommended)

# Run directly without installation
uvx hologres-agent-skills

Install via pip

pip install hologres-agent-skills
hologres-agent-skills

Install from source (Development)

cd agent-skills
uv sync
uv run hologres-agent-skills

Usage

The installer guides you through an interactive workflow:

1. Select tool — Choose which AI coding tool to install skills for
2. Confirm path — Verify the installation directory
3. Select skills — Pick one or more skills to install
4. Done — Skills are copied to the tool's skills directory

$ hologres-agent-skills

🚀 Hologres Agent Skills Installer
==================================================

📋 Select tool to install to:
? Select one tool: Claude Code

📁 Project root: /path/to/your/project
   (Skills will be installed under .claude/skills)
? Install skills to this directory? Yes

📦 Select skills to install:
? Select skills:
  ● hologres-cli
  ● hologres-query-optimizer
  ● hologres-slow-query-analysis
  ● hologres-schema-generator
  ● hologres-privileges
  ● hologres-uv-compute
  ● hologres-bsi-profile-analysis
  ● hologres-ad-campaign
  ● hologres-instance-health-analyse
  ● hologres-diagnosis-cpu
  ● hologres-diagnosis-memory
  ● hologres-daily-report
  ● hologres-knowledge-base

✨ Installation complete

Development

Build & Publish to PyPI

cd agent-skills

# Build only (artifacts in dist/)
python upload_to_pypi.py --build

# Upload to TestPyPI (verification)
export TEST_PYPI_TOKEN="pypi-xxx"
python upload_to_pypi.py --test

# Upload to official PyPI
export UV_PUBLISH_TOKEN="pypi-xxx"
python upload_to_pypi.py --publish

# Bump version and publish
python upload_to_pypi.py --publish --version 0.2.0

Publish to ClawHub (OpenClaw Skill Marketplace)

Publish skills to the ClawHub public skill registry:

cd agent-skills

# Prerequisites
npm i -g clawhub
clawhub login

# Publish all skills
python publish_to_clawhub.py

# Publish a specific skill
python publish_to_clawhub.py --skill hologres-cli

# Dry-run (preview without publishing)
python publish_to_clawhub.py --dry-run

# Bump patch version before publishing
python publish_to_clawhub.py --bump

# Set a specific version
python publish_to_clawhub.py --version 1.2.0

# Publish under an org handle
python publish_to_clawhub.py --owner holomcp

Publish to Aone (contextlab)

Publish individual skills to the Aone platform:

cd agent-skills

# Set authentication token
export AONE_TOKEN=<your-token>

# Publish all skills
python publish_to_aone.py

# Publish a specific skill
python publish_to_aone.py --skill hologres-cli

# Dry-run (preview without publishing)
python publish_to_aone.py --dry-run

# Bump patch version before publishing
python publish_to_aone.py --bump

# Set a specific version
python publish_to_aone.py --version 1.2.0

Catalog Consistency Check

Skill names are duplicated in 5 catalog files (installer + 4 READMEs). Every time a new skill is added under skills/, all 5 must be updated, or uvx hologres-agent-skills users won't see / be able to install it. The check script catches the drift:

# Standalone run (exit 1 on drift, exit 0 on clean)
python agent-skills/tests/test_catalog_consistency.py

# Or via pytest
pytest agent-skills/tests/test_catalog_consistency.py -v

Install as a local pre-commit hook (optional, recommended)

A repo-local pre-commit hook lives at .githooks/pre-commit. It chains the user's globally-configured pre-commit (e.g. Alibaba AccessKey scanner) and then runs the catalog check. One-time install per clone:

git config --local core.hooksPath .githooks

To uninstall: git config --local --unset core.hooksPath.

Why a wrapper? When core.hooksPath is set globally (e.g. by Alibaba's AK scanner at ~/.aliyunAKScanHook/hooks), the per-repo .git/hooks/ directory is ignored. We have to set core.hooksPath to a checked-in directory (.githooks) and explicitly re-invoke the global hook from inside the wrapper so the AK scan still runs.

Project Structure

agent-skills/
├── skills/                          # Source skills
│   ├── hologres-cli/
│   ├── hologres-query-optimizer/
│   ├── hologres-slow-query-analysis/
│   ├── hologres-schema-generator/
│   ├── hologres-privileges/
│   ├── hologres-uv-compute/
│   ├── hologres-bsi-profile-analysis/
│   ├── hologres-ad-campaign/
│   ├── hologres-instance-health-analyse/
│   ├── hologres-diagnosis-cpu/
│   ├── hologres-diagnosis-memory/
│   ├── hologres-daily-report/
│   └── hologres-knowledge-base/
├── src/
│   └── holo_plugin_installer/
│       ├── __init__.py
│       └── main.py
├── pyproject.toml
├── MANIFEST.in
├── upload_to_pypi.py
├── publish_to_aone.py
├── README.md
└── README_CN.md

License

Apache License 2.0 — Copyright 2026 Alibaba Cloud