How do I install the Chatbotx Basecode skill?

Run npx skillmds@latest add chatbotxio/chatbotx-basecode in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Chatbotx Basecode safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Chatbotx Basecode?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Chatbotx Basecode free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Chatbotx Basecode?

chatbotxio (@chatbotxio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Chatbotx Basecode by chatbotxio — Agent Skill

Name: Chatbotx Basecode
Author: chatbotxio

Chatbotx Basecode

Understand and audit the ChatbotX base code before making changes. Use when asked to scan the project, check architecture, locate ownership boundaries, onboard to the repository, or decide which project-specific skill should handle a task.

chatbotxio 087c776 3.2 KB Updated Sep 17, 2026

File contents

ChatbotX Basecode

Use this skill as the first pass for broad or ambiguous requests. It is a map, not a replacement for reading adjacent code.

Project Shape

ChatbotX is a pnpm workspace + Turborepo monorepo. The authoritative layout table is AGENTS.md → "Repository layout" — read it there rather than trusting a second copy. To see what actually exists right now:

ls apps packages integrations

Skill Router

The canonical task → skill routing table is CLAUDE.md → "Skill → task mapping". Read it and pick the skill that matches the task; it lists every skill in .agents/skills/.

Two routing notes that table does not spell out:

CLI, MCP server, and the generated public client all follow the public oRPC surface — use orpc-api.
A broad request usually decomposes into several skills (e.g. a new feature with a table and a queue = feature-scaffold + drizzle-database + worker-development). Read each before writing that layer, not all of them up front.

Basecode Scan Checklist

Read the nearest package.json, route/module files, and sibling features.
Identify the owning layer before editing — the chain is action | API handler → service → repository → DB:
- UI/app orchestration (calls a service, never db): apps/builder
- business rules, cache invalidation, events (calls a repository): packages/business
- raw database queries, shard routing: packages/database/src/repositories
- schema/migrations: packages/database
- async processing (calls a service, never db): apps/worker + packages/worker-config
- external channel protocol (calls a service, never db): integrations/<channel>
Search for a similar feature and mirror naming, imports, error handling, and tests.
Check .agents/rules/* for local invariants, especially data access and git.
Keep changes scoped to the user request; do not refactor legacy exceptions unless required.

Non-Negotiable Invariants

New app/integration code must not import db from @chatbotx.io/database/client.
User-facing builder strings must use useTranslations() and message JSON keys.
Next.js app pages use Promise params / searchParams.
Public unauthenticated builder routes must be registered in apps/builder/src/proxy.ts.
Middleware names intentionally contain three ds: workspaceAuthorizedMidddleware and workspaceTokenAuthMidddleware.
Adding database tables requires schema, migration, relation import, and relation spread.
Adding ChannelType values requires fixing every Record<ChannelType, ...> use.

Validation

Prefer targeted checks first, then broader checks when the blast radius grows:

pnpm --filter builder check-types
pnpm --filter @chatbotx.io/database check-types
pnpm --filter worker test
pnpm lint
pnpm build

If the exact script is unclear, inspect the relevant workspace package.json.

---name: chatbotx-basecodedescription: Understand and audit the ChatbotX base code before making changes. Use when asked to scan the project, check architecture, locate ownership boundaries, onboard to the repository, or decide which project-specific skill should handle a task.---# ChatbotX BasecodeUse this skill as the first pass for broad or ambiguous requests. It is a map,not a replacement for reading adjacent code.## Project ShapeChatbotX is a pnpm workspace + Turborepo monorepo. The authoritative layout table is**`AGENTS.md` → "Repository layout"** — read it there rather than trusting a second copy.To see what actually exists right now:```bashls apps packages integrations```## Skill RouterThe canonical task → skill routing table is **`CLAUDE.md` → "Skill → task mapping"**. Readit and pick the skill that matches the task; it lists every skill in `.agents/skills/`.Two routing notes that table does not spell out:- CLI, MCP server, and the generated public client all follow the public oRPC surface — use `orpc-api`.- A broad request usually decomposes into several skills (e.g. a new feature with a table and a queue = `feature-scaffold` + `drizzle-database` + `worker-development`). Read each before writing that layer, not all of them up front.## Basecode Scan Checklist1. Read the nearest `package.json`, route/module files, and sibling features.2. Identify the owning layer before editing — the chain is `action | API handler → service → repository → DB`: - UI/app orchestration (calls a service, never `db`): `apps/builder` - business rules, cache invalidation, events (calls a repository): `packages/business` - raw database queries, shard routing: `packages/database/src/repositories` - schema/migrations: `packages/database` - async processing (calls a service, never `db`): `apps/worker` + `packages/worker-config` - external channel protocol (calls a service, never `db`): `integrations/<channel>`3. Search for a similar feature and mirror naming, imports, error handling, and tests.4. Check `.agents/rules/*` for local invariants, especially data access and git.5. Keep changes scoped to the user request; do not refactor legacy exceptions unless required.## Non-Negotiable Invariants- New app/integration code must not import `db` from `@chatbotx.io/database/client`.- User-facing builder strings must use `useTranslations()` and message JSON keys.- Next.js app pages use Promise `params` / `searchParams`.- Public unauthenticated builder routes must be registered in `apps/builder/src/proxy.ts`.- Middleware names intentionally contain three `d`s: `workspaceAuthorizedMidddleware` and `workspaceTokenAuthMidddleware`.- Adding database tables requires schema, migration, relation import, and relation spread.- Adding `ChannelType` values requires fixing every `Record<ChannelType, ...>` use.## ValidationPrefer targeted checks first, then broader checks when the blast radius grows:```bashpnpm --filter builder check-typespnpm --filter @chatbotx.io/database check-typespnpm --filter worker testpnpm lintpnpm build```If the exact script is unclear, inspect the relevant workspace `package.json`.

Frequently asked questions