ob-skills packages OceanBase knowledge as agent skills. It is not an application in the usual sense. It is a set of reusable instructions and workflows for database architecture, DDL review, and tooling guidance.

The project exists because raw prompting is not enough for repeated technical work.

What is inside

The repo contains skills such as:

  • OceanBase solution architect guidance
  • OceanBase DDL syntax checking
  • seekdb-backed DDL validation

Each skill tries to narrow the agent’s behavior for a specific kind of work. Instead of asking a general model to “help with OceanBase,” the skill defines what kind of answer is expected, which constraints matter, and which validation path should be used.

Why skills instead of notes

Traditional notes help humans. Skills help agents act more consistently.

That difference matters. A good skill should:

  • define the task boundary
  • mention common failure modes
  • route to validation where possible
  • make assumptions explicit
  • avoid generic advice when concrete checks exist

For database work, this is especially useful because the cost of vague answers is high. A DDL suggestion that sounds plausible but violates grammar or deployment constraints is worse than no suggestion.

The useful pattern

The best skills are not huge knowledge dumps. They are small operational wrappers around repeatable judgment.

For example, a DDL validation skill should not merely explain DDL. It should push the agent toward an actual validation path and make clear when offline validation is possible.

That is the difference between “LLM as autocomplete” and “LLM as a guided operator.”

What I learned

Agent quality improves when domain knowledge is packaged close to the workflow. It is not enough to rely on the model remembering a product correctly.

Skills are also easier to maintain than long prompts embedded in many tools. If a rule changes, update the skill. If a validation command improves, update the skill. The agent workflows that use it inherit the better behavior.

Open source status

ob-skills is public because the project is mostly guidance and validation workflow. It is a good fit for sharing: others can inspect the assumptions, reuse the structure, or adapt the skill pattern to their own database work.