一键导入
bkend-data
bkend.ai database — CRUD, column types, filtering, sorting, relations, indexing. Triggers: bkend table, CRUD, column, filter, sort, relation, 테이블, 데이터.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
bkend.ai database — CRUD, column types, filtering, sorting, relations, indexing. Triggers: bkend table, CRUD, column, filter, sort, relation, 테이블, 데이터.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Sprint Management — generic sprint capability for ANY bkit user. 16 sub-actions: init, start, status, watch, phase, iterate, qa, report, archive, list, feature, pause, resume, fork, help, master-plan. Triggers: sprint, sprint start, sprint init, sprint status, sprint list, 스프린트, 스프린트 시작, 스프린트 상태, スプリント, スプリント開始, スプリント状態, 冲刺, 冲刺开始, 冲刺状态, sprint, iniciar sprint, estado sprint, sprint, demarrer sprint, statut sprint, Sprint, Sprint starten, Sprint Status, sprint, avviare sprint, stato sprint, master plan, multi-sprint plan, sprint master plan, 마스터 플랜, 멀티 스프린트 계획, 스프린트 마스터 플랜, マスタープラン, マルチスプリント計画, スプリントマスタープラン, 主计划, 多冲刺计划, 冲刺主计划, plan maestro, plan multi-sprint, plan maestro sprint, plan maître, plan multi-sprint, plan maître sprint, Masterplan, Multi-Sprint-Plan, Sprint-Masterplan, piano principale, piano multi-sprint, piano principale sprint.
CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report. Triggers: cc-version-analysis, CC upgrade, version analysis, CC 버전 분석, 버전 영향.
View audit logs, decision traces, and session history for AI transparency. ACTION_TYPES (19 entries) include PDCA events (phase_transition, gate_passed/failed, agent_spawned/completed/failed, rollback_executed, destructive_blocked) and Sprint events (sprint_paused, sprint_resumed, master_plan_created — v2.1.13). Triggers: audit, log, decision trace, history, 감사 로그, 결정 추적.
Core rules for bkit — PDCA methodology, level detection, agent triggering, quality standards, Sprint management (8-phase container with 4 auto-pause triggers, v2.1.13), and Trust Level scope (L0-L4 gates PDCA + Sprint auto-run). Triggers: bkit rules, core rules, methodology, 핵심 규칙, PDCA 규칙.
PDCA + Sprint document templates — Plan, Design, Analysis, Report for individual features plus templates/sprint/{master-plan, prd, plan, design, iterate, qa, report}.template.md for sprint-level documents (v2.1.13). Triggers: template, plan document, design template, 템플릿, 문서 양식.
Complete 9-phase development pipeline guide — from schema to deployment. Pipeline phases (1-schema → 9-deployment) are orthogonal to PDCA's 9-phase per-feature cycle and Sprint's 8-phase container; each pipeline phase may host PDCA cycles for individual features, and multi-feature pipeline initiatives can be wrapped in /sprint (v2.1.13). Triggers: development pipeline, where to start, phase, 개발 파이프라인, 순서, 시작.
| name | bkend-data |
| classification | capability |
| classification-reason | Pattern guidance may overlap with model's built-in knowledge as it improves |
| deprecation-risk | medium |
| effort | medium |
| description | bkend.ai database — CRUD, column types, filtering, sorting, relations, indexing. Triggers: bkend table, CRUD, column, filter, sort, relation, 테이블, 데이터. |
| user-invocable | false |
| agent | bkit:bkend-expert |
| allowed-tools | ["Read","Write","Edit","Glob","Grep","Bash","mcp__bkend__*"] |
| imports | ["${PLUGIN_ROOT}/templates/shared/bkend-patterns.md"] |
| Type | Description | Example |
|---|---|---|
| String | Text | name, email |
| Number | Numeric | age, price |
| Boolean | True/false | isActive |
| Date | Date/time | birthDate |
| Array | Array | tags: ["a","b"] |
| Object | Nested object | address: {city, zip} |
| Mixed | Any type | metadata |
required: Field must have a valueunique: No duplicate values alloweddefault: Default value when not provided| Field | Type | Description |
|---|---|---|
| id | String | Auto-generated unique ID |
| createdBy | String | Creator user ID |
| createdAt | Date | Creation timestamp |
| updatedAt | Date | Last update timestamp |
Important: bkend uses id (NOT _id) in all API responses.
| Tool | Purpose | Scope |
|---|---|---|
backend_table_create | Create table | table:create |
backend_table_list | List tables | table:read |
backend_table_get | Get table detail + schema | table:read |
backend_table_delete | Delete table | table:delete |
backend_field_manage | Add/modify/delete fields | table:update |
backend_index_manage | Manage indexes | table:update |
backend_schema_version_list | Schema version history | table:read |
backend_schema_version_get | Schema version detail | table:read |
backend_schema_version_apply | Apply schema version (rollback) | table:update |
backend_index_version_list | Index version history | table:read |
backend_index_version_get | Index version detail | table:read |
| Tool | Purpose | Key Parameters |
|---|---|---|
backend_data_list | List records (filter, sort, paginate) | tableId, page?, limit?, sortBy?, sortDirection?, andFilters?, orFilters? |
backend_data_get | Get single record | tableId, recordId |
backend_data_create | Create record | tableId, data: { field: value } |
backend_data_update | Partial update record | tableId, recordId, data: { field: value } |
backend_data_delete | Delete record | tableId, recordId |
All Data CRUD tools require: organizationId, projectId, environmentId (from get_context).
| Operator | Meaning | Example |
|---|---|---|
$eq | Equal | { "status": { "$eq": "active" } } |
$ne | Not equal | { "role": { "$ne": "admin" } } |
$gt / $gte | Greater than / >= | { "age": { "$gt": 18 } } |
$lt / $lte | Less than / <= | { "price": { "$lt": 100 } } |
$in / $nin | In / Not in array | { "tag": { "$in": ["a","b"] } } |
Use search_docs tool to access these guides:
| Doc ID | Content |
|---|---|
4_howto_implement_data_crud | CRUD implementation patterns |
7_code_examples_data | CRUD + file upload code examples |
Use get_operation_schema to get any tool's input/output schema.
| Method | Endpoint | Description |
|---|---|---|
| GET | /v1/data/{table} | List (filter, sort, page, limit) |
| POST | /v1/data/{table} | Create |
| GET | /v1/data/{table}/{id} | Get single |
| PATCH | /v1/data/{table}/{id} | Partial update |
| DELETE | /v1/data/{table}/{id} | Delete |
?search=keyword?filter[field1]=value1&filter[field2]=value2$eq, $ne, $gt, $gte, $lt, $lte, $in, $nin?sort=field:asc (or desc)?page=1&limit=20 (default 20, max 100)backend_index_manageFor the latest database documentation, use WebFetch: