config
Generate ScalarDB configuration files (database.properties, build.gradle dependencies) based on your choices.
Skill by wfukatsu
Chalk Labs
Need help deploying config?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
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/wfukatsu-config
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.
About
Use cases: backend
Reviews
Write a reviewNo 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 and code. 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/config
What's inside
- Skill name
config- Description
- Generate ScalarDB configuration files (database.properties, build.gradle dependencies) based on your choices. Use when starting a ScalarDB project, switching backend/edition (Core/Cluster) or interface (CRUD/JDBC, 1PC/2PC), or debugging connection/configuration errors.
- License
- MIT
- Instructions
- 119 lines in SKILL.md · view on GitHub
Agent Skills spec issues
- name: missing
Files (1)
- SKILL.md
SKILL.md (first lines)
# /scalardb:config — ScalarDB Configuration Generator
Shared files: a path written `@rules/…`, `@skills/…`, `@templates/…` or `@docs/…` is relative to the
plugin root, `${CLAUDE_PLUGIN_ROOT}` — not to the project being worked on. Read it from there.
## Instructions
You are a ScalarDB configuration generator. Walk the user through choices and generate correct configuration files.
**Knowledge grounding**: version-specific behavior (API signatures, config keys, exception retryability, edition-gated features) comes from the version-pinned OKF bundle, cited by `resource` URL, never from memory — @rules/okf-knowledge-bundle.md.
## Interactive Flow
### Step 1: Deployment Mode
Ask: "Which deployment mode?"
- **Core** — Direct database connection (development, simple apps)
- **Cluster** — Via ScalarDB Cluster (production)
### Step 2: API Style
Ask: "Which API style?"
- **CRUD API** — Java native builder pattern (Get, Scan, Insert, etc.)
- **JDBC/SQL** — ScalarDB SQL via the ScalarDB JDBC driver (requires Cluster mode, Enterprise Premium)
If user chose Core + JDBC, explain that ScalarDB SQL requires Cluster mode and suggest either
switching to Cluster or using the CRUD API — or, if the real need is "SQL tools / PostgreSQL drivers
must query the data" or "a legacy SQL application keeps its native SQL on the same database", point
to the PostgreSQL wire protocol (Cluster 3.20+; standalone Apache-2.0 frontend on Core) or ScalarDB
Native JDBC, which are configured outside this file: @rules/scalardb-postgres-frontend-patterns.md,
@rules/scalardb-native-jdbc-patterns.md.
### Step 3: Transaction Mode
Ask: "Which transaction mode?"
- **One-phase commit (1PC)** — Standard transactions, including multi-storage from one application
and, on Cluster 3.19+, transactions spanning services through the Microservice Transaction API
(shared cluster, or separated clusters with `scalar.db.cluster.client.transaction_coordinator.*`)
- **Two-phase commit (2PC)** — The application-driven 2PC interface, **deprecated as of 3.19**;
only for a release before 3.19, Core without Cluster, or Spring Data JDBC, as a recorded deviation
### Step 4: Database Backend
Ask: "Which database backend?"
- MySQL
- PostgreSQL
- Cassandra
- DynamoDB (or DynamoDB Local for development)
- Cosmos DB
- Oracle
- SQL Server
- Multi-storage (multiple backends)
### Step 5: Generate Configuration
Based on choices, generate:
1. **`database.properties`** (or `scalardb-sql.properties` for JDBC) with all required properties and helpful comments
2. **`build.gradle` dependencies section** with correct Maven artifacts
3. **Brief explanation** of each property's purpose
## Reference
Read `${CLAUDE_PLUGIN_ROOT}/skills/common/references/configuration-reference.md` for the complete property reference.
Read `${CLAUDE_PLUGIN_ROOT}/skills/common/references/interface-matrix.md` for the dependency matrix.
Read `${CLAUDE_PLUGIN_ROOT}/rules/scalardb-config-validation.md` for the checks a properties file must pass and the mistakes to catch.
## Dependency Versions
The dependency coordinates below are written `:<version>` on purpose. Resolve the concrete version
per `rules/dependency-versions.md` — read the published list from
`https://repo1.maven.org/maven2/com/scalar-labs/<artifact>/maven-metadata.xml`, pick the newest
**stable** release (no `-alpha`/`-beta`/`-rc`/`-SNAPSHOT`) that matches the project's edition and Java
version, keep every ScalarDB artifact on the **same** version, and confirm with the user unless the
project opted out (`options.confirm_versions` / `--no-confirm-versions`).
## Configuration Templates
### Core + CRUD (MySQL)
```properties
scalar.db.storage=jdbc
scalar.db.contact_points=jdbc:mysql://localhost:3306/
scalar.db.username=root
scalar.db.password=mysql
```
Dependency: `com.scalar-labs:scalardb:<version>`
### Core + CRUD (PostgreSQL)
```properties
scalar.db.storage=jdbc
scalar.db.contact_points=jdbc:postgresql://localhost:5432/
scalar.db.username=postgres
scalar.db.password=postgres
```
Dependency: `com.scalar-labs:scalardb:<version>`
### Core + CRUD (Cassandra)
```properties
scalar.db.storage=cassandra
scalar.db.contact_points=localhost
scalar.db.username=cassandra
scalar.db.password=cassandra
```
Dependency: `com.scalar-labs:scalardb:<version>`
### Core + CRUD (DynamoDB Local)
```properties
scalar.db.storage=dynamo
scalar.db.contact_points=sample
scalar.db.username=sample
scalar.db.password=sample
scalar.db.dynamo.endpoint_override=http://localhost:8000
```
Dependency: `com.scalar-labs:scalardb:<version>`
### Cluster + CRUD
```properties
scalar.db.transaction_manager=cluster
scalar.db.contact_points=indirect:localhost
```
Dependency: `com.scalar-labs:scalardb-cluster-java-client-sdk:<version>`
### Cluster + JDBCFrom wfukatsu/nexus-architect, MIT.
More from wfukatsu/nexus-architect
- 0.632score
crud-ops
wfukatsu
Show ScalarDB CRUD operation patterns — builder syntax for Get, Scan, Insert, Upsert, Update, Delete with examples.
SkillAFreshness: A★ 13Claude Code +9 - 0.632score
docs
wfukatsu
Search ScalarDB / ScalarDL documentation for specific topics.
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
analyze
wfukatsu
Extract ubiquitous language, actor-role-permission matrix, and domain-code mapping.
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
generate-test-specs
wfukatsu
Generate BDD scenarios, contract test, unit test, property-based test, integration test, and performance test specifications.
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
build-app
wfukatsu
Build a complete ScalarDB application from a domain description.
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
capture-followup
wfukatsu
Capture follow-up work discovered during backlog delivery — deferred tasks, out-of-scope findings, doc drift, waived acceptance criteria — into a reviewable…
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
deliver-backlog
wfukatsu
Drive each Issue under an Epic through implement → review → human approval → merge, in order, resuming from backlog-manifest.json and stopping at every human…
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
analyze-data-model
wfukatsu
Comprehensive data layer analysis including entity/relationship analysis, DB design evaluation, and ER diagram generation.
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
analyze-ui
wfukatsu
Analyze the user interface of an existing system: screens with their inputs, outputs, actions and access; UI components; features and user tasks; business…
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
design-api
wfukatsu
Generate REST/GraphQL/gRPC/AsyncAPI specifications as the project's single, verifiable API contract — named schemas, every status code declared, RFC 9457…
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
design-data-layer
wfukatsu
Generic database design for non-ScalarDB projects.
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
design-graphql
wfukatsu
Design a schema-first Spring for GraphQL API after /architect:design-api selects GraphQL or a hybrid surface.
SkillAFreshness: A★ 13Claude Code +9
Signals
- Stars
- 13
- Forks
- 1
- Open issues
- 0
- Last commit (this folder)
- Oct 8, 2026 (23 days ago)
- Last release
- Oct 9, 2026 (22 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/wfukatsu/nexus-architect
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from wfukatsu
- 0.632score
docs
wfukatsu
Search ScalarDB / ScalarDL documentation for specific topics.
SkillAFreshness: A★ 13Claude Code +9 - 0.632score
crud-ops
wfukatsu
Show ScalarDB CRUD operation patterns — builder syntax for Get, Scan, Insert, Upsert, Update, Delete with examples.
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
analyze
wfukatsu
Extract ubiquitous language, actor-role-permission matrix, and domain-code mapping.
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
analyze-ui
wfukatsu
Analyze the user interface of an existing system: screens with their inputs, outputs, actions and access; UI components; features and user tasks; business…
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
build-app
wfukatsu
Build a complete ScalarDB application from a domain description.
SkillAFreshness: A★ 13Claude Code +9 - 0.629score
analyze-data-model
wfukatsu
Comprehensive data layer analysis including entity/relationship analysis, DB design evaluation, and ER diagram generation.
SkillAFreshness: A★ 13Claude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get config running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
config skill. Agent Mart. https://agentmart.dev/skills/wfukatsu-config (last updated 2026-10-24)