Skip to content
Agentmart
Submit a tool

aizen-database

Aizen knowledge pack (v24) — schema design and team conventions, migrations, concurrency, performance, connections, growth, partitioning, HA/DR, compliance…

Skill by tankhangkm12

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/tankhangkm12-aizen-database

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Aizen knowledge pack (v24) — schema design and team conventions, migrations, concurrency, performance, connections, growth, partitioning, HA/DR, compliance; engines PostgreSQL, MySQL, MongoDB, Redis, Elasticsearch. Loaded by Aizen roles through their brief; not a standalone skill, do not trigger it directly — use aizen-build.

Use cases: design, backend, security, marketing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/aizen-database

What's inside

Skill name
aizen-database
Description
Aizen knowledge pack (v24) — schema design and team conventions, migrations, concurrency, performance, connections, growth, partitioning, HA/DR, compliance; engines PostgreSQL, MySQL, MongoDB, Redis, Elasticsearch. Loaded by Aizen roles through their brief; not a standalone skill, do not trigger it directly — use aizen-build.
License
MIT
Instructions
24 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • files: referenced but missing: references/core/workspace.md

Files (127)

  • SKILL.md
  • database.md · assets/db/
  • dr-runbook.md · assets/db/
  • engine-adr.md · assets/db/
  • growth-report.md · assets/db/
  • scaling-options.md · assets/db/
  • manifest.json
  • backup-dr.md · references/db/
  • gdpr.md · references/db/compliance/
  • vn-pdpl.md · references/db/compliance/
  • concurrency.md · references/db/
  • connections.md · references/db/
  • db-code.md · references/db/
  • engine-selection.md · references/db/
  • engine-tuning.md · references/db/
  • _new-engine.md · references/db/engines/
  • elasticsearch.md · references/db/engines/
  • mongodb.md · references/db/engines/
  • mysql.md · references/db/engines/
  • postgresql.md · references/db/engines/
  • redis.md · references/db/engines/
  • growth-forecast.md · references/db/
  • ha-replication.md · references/db/
  • method.md · references/db/
  • microservices-data.md · references/db/
  • migrations.md · references/db/
  • partitioning-retention.md · references/db/
  • performance.md · references/db/
  • scaling-ladder.md · references/db/
  • schema-design.md · references/db/
  • security-compliance.md · references/db/
  • LICENSE · references/db/vendor/elastic/
  • UPSTREAM.md · references/db/vendor/elastic/
  • guide.md · references/db/vendor/elastic/index-design/
  • field-type-decisions.md · references/db/vendor/elastic/index-design/references/
  • mapping-explosion.md · references/db/vendor/elastic/index-design/references/
  • multi-field-patterns.md · references/db/vendor/elastic/index-design/references/
  • guide.md · references/db/vendor/elastic/query-optimization/
  • query-optimization-reference.md · references/db/vendor/elastic/query-optimization/references/
  • guide.md · references/db/vendor/elastic/reindex/
  • api-reference.md · references/db/vendor/elastic/reindex/references/
  • patterns.md · references/db/vendor/elastic/reindex/references/
  • troubleshooting.md · references/db/vendor/elastic/reindex/references/
  • tuning.md · references/db/vendor/elastic/reindex/references/
  • LICENSE · references/db/vendor/planetscale-mysql/
  • UPSTREAM.md · references/db/vendor/planetscale-mysql/
  • guide.md · references/db/vendor/planetscale-mysql/
  • character-sets.md · references/db/vendor/planetscale-mysql/references/
  • composite-indexes.md · references/db/vendor/planetscale-mysql/references/
  • connection-management.md · references/db/vendor/planetscale-mysql/references/
  • covering-indexes.md · references/db/vendor/planetscale-mysql/references/
  • data-types.md · references/db/vendor/planetscale-mysql/references/
  • deadlocks.md · references/db/vendor/planetscale-mysql/references/
  • explain-analysis.md · references/db/vendor/planetscale-mysql/references/
  • fulltext-indexes.md · references/db/vendor/planetscale-mysql/references/
  • index-maintenance.md · references/db/vendor/planetscale-mysql/references/
  • isolation-levels.md · references/db/vendor/planetscale-mysql/references/
  • json-column-patterns.md · references/db/vendor/planetscale-mysql/references/
  • n-plus-one.md · references/db/vendor/planetscale-mysql/references/
  • online-ddl.md · references/db/vendor/planetscale-mysql/references/
  • …and 67 more

SKILL.md (first lines)

# Database knowledge — Aizen pack (v24)

Owns the topics `db`: every `references/<topic>/…`, `assets/<topic>/…` and `scripts/<topic>/…` path for them
lives here. Shared rules (authority, evidence, code quality, style) are in `aizen-core`; the flow and roles are in
`aizen-build`.

- **Used by:** dev `KIND=db`; planner (DB questions); tester (database lens); reviewer (database lens).
- **Entry points:** `references/db/method.md` — each has a "Guides" table; load only the rows the change touches.
- Templates: `assets/db/` (database doc, growth report, scaling options, engine ADR, DR runbook).

## Upstream knowledge (vendored, pinned)

Best practice from the people who build the tools, copied verbatim at a pinned commit (`vendor.lock.json`
in the Aizen repo). It says how to do a thing right in that tool; Aizen core rules still decide how much to build
and who decides (`references/core/workspace.md` §3).

| Source | Details |
|---|---|
| Supabase — Postgres best practices | `references/db/vendor/supabase-postgres/UPSTREAM.md` |
| PlanetScale — MySQL and Postgres internals | `references/db/vendor/planetscale-mysql/UPSTREAM.md` |
| Redis Inc. — Redis core, connections, clustering, security, observability | `references/db/vendor/redis/UPSTREAM.md` |
| Elastic — index design, query optimisation, reindex | `references/db/vendor/elastic/UPSTREAM.md` |

From tankhangkm12/Aizen-Skills, MIT.

More from tankhangkm12/Aizen-Skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 6, 2026 (23 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from tankhangkm12

Cite this page

aizen-database skill. Agent Mart. https://agentmart.dev/skills/tankhangkm12-aizen-database (last updated 2026-10-24)