mcpField
A
appdb-collection-create

appdb-collection-create

github.com/stahuraData & databases24191 installsUpdated 26w ago
Repository

About appdb-collection-create

A skill for initializing AppDB storage through `community-domo-cli`, creating a datastore and collection and recording their identifiers for follow-up app wiring. It is intended for app projects that need a new collection rather than an existing one.

Key features

  1. 01Create datastore and collection
  2. 02Accept collection schema input
  3. 03Capture datastore and collection IDs
  4. 04Prepare manifest mapping follow-up
  5. 05Hand off to document CRUD workflow

Use cases

  1. 01Initialize storage for an app feature
  2. 02Create a collection with defined columns
  3. 03Pass collection IDs to downstream workflows

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/stahura/domo-ai-vibe-rules --skill appdb-collection-create

After installing, type/appdb-collection-createin Claude Code to confirm it loaded.

Details

From the project README

AppDB Collection Create (CLI)

Use this skill when the app needs new AppDB storage and the CLI path can create both datastore and collection in one operation.

Intent

This skill covers storage initialization lifecycle:

  • create required datastore
  • create collection inside that datastore
  • capture resulting identifiers
  • prepare follow-up manifest mapping and document-write usage

For document CRUD operations after collection exists, use ~/.agents/skills/appdb/SKILL.md.

Assumed CLI Behavior

Assume community-domo-cli includes:

  • appdb collection-create

and that this operation handles datastore provisioning automatically when needed.

Primary Execution Path

Prefer CLI:

community-domo-cli --instance <instance> appdb collection-create --body-file collection.json

If CLI support is unavailable in a given environment, fall back to direct endpoint workflows:

  • POST /api/datastores/v1 (create datastore)
  • POST /api/datastores/v1/{datastoreId}/collections (create collection)

Required Input Contract

Use a body that includes at least:

  • collection name
  • collection schema.columns
  • optional syncEnabled

Example:

{
  "name": "TasksCollection",
  "schema": {
    "columns": [
      { "name": "title", "type": "STRING" },
      { "name": "status", "type": "STRING" }
    ]
  },
  "syncEnabled": true
}

Output Requirements

Return or persist:

  • datastoreId
  • collectionId
  • collectionName

so downstream skills can:

  • wire manifest mappings
  • create documents in the new collection

Manifest Follow-up

After successful creation, ensure app manifest contains collection wiring expected by the app project conventions in this repo.

Checklist

  • App requires new AppDB storage (not existing collection reuse)
  • CLI collection-create path used first
  • Datastore+collection identifiers captured
  • Manifest collection mapping follow-up performed
  • Hand-off to document CRUD flow (~/.agents/skills/appdb/SKILL.md) is clear

Comments

Markdown supported