pgx
PGX — Lightweight Postgres for AI agents. Written in Rust. Thousands of isolated databases in one runtime. 🐘
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Product data science as agent skills: route question to the right method, run checks before shipping.
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
Skills that make your coding agent think like a product data scientist.
They decide if a question deserves an analysis, pick the method, and check the result.
One command, a synthetic dataset, and every check once:
The full loop, from a question arriving to the prior store changing on disk, is python3 examples/end-to-end/run_loop.py.
A question enters at the left and leaves as a decision. Measurement is a foundation because what ships changes the data. Theory is a ceiling because what you learn has to outlive the test that produced it.檢視完整 README ↗Statistics libraries assume you already know which question you are answering. Product management skill packs know which question matters and carry no statistics. With gallop, every question passes routing first before any query runs, and goes to one of three method buckets, on a measurement floor and under a knowledge ceiling.
| Bucket | Asks | Hands back |
|---|---|---|
| Description | What happened? | A hypothesis |
| Causation | Did this change cause that? | An effect size |
| Prediction | What will happen? Who gets what? | A forecast, a ranking, an allocation |
gallop's sibling, bluML, builds and runs the models that will live inside the product, from framing to monitoring, when it is installed; gallop keeps the questions around them: whether a model fits the question, uplift targeting, and whether the model moved anything.
A question enters at the left and leaves as a decision. Measurement is a foundation because what ships changes the data. Knowledge is a ceiling because what you learn has to outlive the test that produced it.
| Skill | What it decides | Reach for it when |
|---|---|---|
routing-questions | Whether this becomes work at all, and which skill it becomes | a product, analytics, or experimentation request first arrives, when someone asks for a deep dive or a dashboard, or before opening a query editor on any question about impact, lift, or whether something worked |
defining-metrics | A metric turned into a computation, a source of truth, a registry entry, and a statement of how it will be gamed | defining a north-star or guardrail metric, when two dashboards disagree on the same number, when arbitrating between conflicting metric definitions, or when a report depends on a metric nobody has validated |
forming-hypotheses | A what-happened question turned into a localised, sized hypothesis, with the floor checked first and the gap never quoted as the prize | a metric moved and someone asks what happened, when asked for a deep dive, a funnel or segment analysis, a root cause, or an opportunity size before a roadmap commitment, or when an observed gap between two groups is about to be quoted as the value of closing it |
designing-experiments | The four choices that cannot be repaired after launch, with the MDE from the prior store | planning, powering, or pre-registering an experiment, when deciding whether a question is testable at the available traffic, or when a feature is about to ship without a flag |
reading-experiments | Whether the result is a result: SRM, exposure, the sequential bound, CUPED, shrinkage | analysing or reviewing A/B test results, when a test looks like a winner, when someone reports a lift, or when deciding whether to ship on an experiment report |
choosing-causal-designs | The method that matches how assignment happened, and the exit that says there is no comparison group | measuring the impact of something already rolled out, a launch, a migration, a pricing change, or a campaign that reached everyone at once |
building-models | Whether a forecast or a repeated decision belongs to a model, validated out of time, and the holdout that measures its impact | someone asks for a churn, propensity, LTV, scoring, forecasting, uplift, recommendation or allocation model, when a model's offline accuracy is offered as evidence that something worked, or when deciding who gets an offer, a discount or an intervention |
writing-reports | The decision rule first, the result last; the belief filed where the next question starts | a test finishes, when documenting a shipped or killed decision, when writing up a null result or a rollback, or when a question needs an entry someone can find in a year |
Each skill is a directory of markdown: SKILL.md is the procedure, the reference/ files one level down are the depth. Read them as prose, or copy them into your agent's skills folder:
git clone https://github.com/0trm/gallop
mkdir -p .claude/skills
cp -r gallop/skills/* .claude/skills/
How the skills hand off to each other, and the state they share: docs/orchestration.md.
MIT. What it covers and how to contribute: docs/model.md.