agentleFS
ww-w-aiww-w-ai/bkit-codex/.agents/skills/bkend-quickstart/SKILL.md

bkend-quickstart

Skill69 starsChanged 8 months agoApache-2.0View on GitHub

bkend.ai BaaS quick start guide. Project setup, MCP connection, and first API call. Get started with bkend.ai backend-as-a-service in minutes. Triggers: bkend setup, bkend start, BaaS setup, backend setup, first project, bkend 시작, bkend 설정, 백엔드 설정, bkend開始, bkendセットアップ, bkend开始, bkend设置, empezar bkend, demarrer bkend, bkend starten, iniziare bkend Do NOT use for: auth details (use $bkend-auth), data modeling (use $bkend-data).

  • Reads credentials
  • Installs packages

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    $bkend-data: Create tables and manage data

    line 97
  2. Distinctive:

    $bkend-cookbook: Follow step-by-step tutorials

    line 100

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

bkend.ai Quick Start

Get your backend running in 5 minutes with bkend.ai BaaS.

Actions

ActionDescriptionExample
setupInitial project setup$bkend-quickstart setup
connectConnect MCP server$bkend-quickstart connect
testVerify connection$bkend-quickstart test

Step 1: Create bkend.ai Project

  1. Go to bkend.ai dashboard
  2. Click "New Project"
  3. Enter project name
  4. Copy your Project ID and API URL

Step 2: Environment Setup

# Create .env.local
NEXT_PUBLIC_BKEND_API_URL=https://api.bkend.ai/v1
NEXT_PUBLIC_BKEND_PROJECT_ID=your-project-id
NEXT_PUBLIC_BKEND_ENV=dev

Step 3: Install Client

npm install @bkend/client
# Or use the built-in fetch wrapper (see references/bkend-patterns.md)

Step 4: Create API Client

// lib/bkend.ts
const API_BASE = process.env.NEXT_PUBLIC_BKEND_API_URL!;
const PROJECT_ID = process.env.NEXT_PUBLIC_BKEND_PROJECT_ID!;

async function bkendFetch(path: string, options: RequestInit = {}) {
  const token = localStorage.getItem('bkend_access_token');
  const res = await fetch(`${API_BASE}${path}`, {
    ...options,
    headers: {
      'Content-Type': 'application/json',
      'x-project-id': PROJECT_ID,
      ...(token && { Authorization: `Bearer ${token}` }),
      ...options.headers,
    },
  });
  if (!res.ok) throw new Error(await res.text());
  return res.json();
}

Step 5: Test Connection

# Test with curl
curl -s https://api.bkend.ai/v1/health \
  -H "x-project-id: your-project-id" | jq .

Step 6: Connect MCP (for Codex)

// .codex/mcp.json
{
  "servers": {
    "bkend": {
      "command": "npx",
      "args": ["@bkend/mcp-server"],
      "env": {
        "BKEND_PROJECT_ID": "your-project-id"
      }
    }
  }
}

What's Next?

  • $bkend-data: Create tables and manage data
  • $bkend-auth: Add authentication
  • $bkend-storage: Handle file uploads
  • $bkend-cookbook: Follow step-by-step tutorials

Reference

See references/bkend-patterns.md for complete API patterns and code examples.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.