Kelly crm
Busabase-backed App-in-Skill CRM operator for contacts, companies, deals, and agent-drafted follow-ups in a reviewable follow-up queue. Use when the user invokes $kelly-crm or /kelly-crm, mentions CRM, pipeline, contacts, companies, deals, follow-ups, relationship management, meeting-note capture, outreach drafts, next steps, or wants to review/approve agent-drafted follow-up messages before they are sent through other channels.From its SKILL.md
npx -y skills add mr-kelly/skills --skill kelly-crmAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
9.0 KB, as published. Nobody here has run it
Kelly CRM
Overview
Kelly CRM is a Busabase Cloud App-in-Skill. Its canonical product surface is the
AirApp in Busabase, not a separate local-data product. The same Hono source
supports an explicitly requested local preview with OAuth connection bootstrap.
It keeps a Busabase-backed dashboard over contacts, companies, deals, and
interactions, plus a review queue of agent-drafted follow-up messages. The
skill gathers and updates CRM data from whatever Kelly feeds it — emails,
meeting notes, chat asks — drafts follow-ups, and hands off an approved
follow-up to another channel skill (for example kelly-email) only after
explicit approval.
Default behavior is AirApp-first. Unless the user explicitly asks only for
explanation, update Busabase directly and give the user the clickable AirApp
URL. Start localhost only when local preview/debugging is explicitly
requested; it uses the same Busabase resources and never offers another data
provider. Use chat-only mode only when the user says "纯聊天", "chat only",
"不要打开 UI", or similar; in that mode present numbered follow-ups
(Follow-up #1) and take verdicts in the conversation, still writing them
through Busabase.
Mandatory Dependencies
- Read and follow
$kelly-app-skill-creatorfor product behavior, visual quality, responsive layout, and the complete canonicalcontent/kelly-crm-app/artifact. - Read and follow
$busabasefor connection, target Space, node discovery, ChangeRequests, review, and merge behavior. - Read and follow
$busabase-app-creatorfor resource modeling, AirApp runtime limits, security, validation, and deployment.
If a dependency is unavailable, preserve this skill's local artifact and product contracts, stop before the unavailable Busabase operation, and report the exact missing dependency. Do not invent a second data backend.
App UI Screenshots
<table> <tr> <td width="50%"><img src="assets/screenshots/overview.webp" alt="Kelly CRM overview"></td> <td width="50%"><img src="assets/screenshots/deals.webp" alt="Kelly CRM deal pipeline"></td> </tr> <tr> <td><strong>Overview</strong><br>CRM command desk with pipeline totals by stage, follow-ups due, recent activity, and network counts.</td> <td><strong>Deals</strong><br>Pipeline table across stages with amounts, probability, next steps, and a per-deal interaction timeline.</td> </tr> <tr> <td width="50%"><img src="assets/screenshots/contacts.webp" alt="Kelly CRM contacts"></td> <td width="50%"><img src="assets/screenshots/followups.webp" alt="Kelly CRM follow-up queue"></td> </tr> <tr> <td><strong>Contacts</strong><br>Contact list with relationship strength, last touch, and per-contact interaction history and open deals.</td> <td><strong>Follow-up queue</strong><br>Agent-drafted follow-up messages with editable drafts, risk badges, and approve/request-changes/block decisions.</td> </tr> </table>Boundary
- The AirApp reads Busabase records, drafts follow-up messages, and records human decisions only through Busabase writes. It must never send emails or messages, call external APIs, or perform any external side effect.
- Outbound follow-up messages are always approval-required. Sending is
delegated to other skills (for example
kelly-email) and happens only after the user approves the specific follow-up.scripts/execute_decisions.mjsonly marks an approved followupdonewith handoff metadata; it performs no sending itself. - Treat all contact and deal data as sensitive. Never commit real contact details, tokens, or Busabase credentials.
Busabase Resources
Six Bases under one application Folder (kelly-crm), declared in
content/kelly-crm-app/app/js/config.js and the generated template sidecars under content/:
companies: name, domain, industry, size, location, notes.contacts: name, company, role, email, relationship strength, tags, last touch, next follow-up, agent notes, channels.deals: name, company, primary/linked contacts, stage, amount, currency, probability, next step, owner, dates, status, agent-suggested next action.interactions: contact, company, deal, type, direction, summary, source.followups: the review queue — contact, deal, channel, reason, risk badges, due date, workflowstatus, editablesuggested_reply, and the human verdict fieldsdecision_comment/decided_at/decided_bywritten directly onto the record (there is no separate decisions file).settings: operator profile, pipeline stages, channels, and the agent lock, one row perkind.
Resources provision lazily through an idempotent Busabase ChangeRequest the
first time the app runs in a Space; see references/crm-schema.md for exact
field shapes.
Authentication
Busabase authentication is ambient inside the deployed AirApp, which must not
show OAuth, API-key, Base URL, provider, hosting, or Space controls.
Standalone loopback preview uses browser OAuth without exposing tokens; after
OAuth it auto-selects a single/open-source Space or requires a native
selector when several Spaces are accessible. It performs no app-resource read
or initialization before selection. scripts/execute_decisions.mjs (a
trusted process, not the AirApp) uses BUSABASE_BASE_URL /
BUSABASE_API_KEY / BUSABASE_SPACE_ID from the environment.
Review Workflow
Follow-ups use the standard workflow states: needs_review,
changes_requested, approved, done, blocked. A human verdict
(approve / request_changes / block / revise) writes the new status
plus decision_comment / decided_at / decided_by directly onto the
followup record through busabase-sdk. From a standalone local preview the
write merges immediately (trusted operator); from the deployed AirApp it
creates a pending ChangeRequest for the trusted process to merge, per the
AirApp boundary in $busabase-app-creator.
- When Kelly feeds new material (emails, meeting notes, chat asks): upsert
companies/contacts/deals by stable domain id (
company_id,contact_id,deal_id), append interactions, and draft new followups withstatus: "needs_review", a clearreason, risk badges, and asuggested_replydraft — all as Busabase writes. - Give Kelly the AirApp URL (or local preview URL) to review the pipeline and the follow-up queue.
- For a followup moved to
changes_requested, re-draft it per the review comment and write it back toneeds_review. - On "execute" / "send approved follow-ups": run
node scripts/execute_decisions.mjs --applyto re-read approved followups from Busabase and mark themdonewith handoff metadata, then perform the actual send only through the corresponding skill (for example$kelly-email) with the approved, possibly user-edited draft, one follow-up at a time. - Never send anything for a followup without an explicit
approvedecision, and never re-send a followup alreadydone.
Demo Mode
?demo=1 opens a deterministic, read-only mock CRM for documentation and
screenshots (content/kelly-crm-app/app/js/providers/demo-provider.js). ?demo=overview,
?demo=deals, ?demo=contacts, ?demo=followups, and ?demo=detail select
named mock scenes; detail deep-links to a deal detail. lang=en or
lang=zh forces UI chrome language. Demo mode never reads or writes
Busabase and never claims a real connection.
Completion Criteria
Finish only when:
- the skill contains the complete canonical
content/kelly-crm-app/project andpnpm --dir content/kelly-crm-app devremains supported; - all persistent config, state, decisions, and domain data use
busabase-sdkand the declared resource map — no local JSON, browser storage, or provider choice; - Vault values and API credentials never reach browser-visible surfaces;
- local setup offers Cloud/custom URL OAuth plus the explicit Demo path, while a deployed AirApp uses its ambient session;
- Overview, Deals, Contacts, Follow-ups, and Help & Settings render on desktop and phone widths;
pnpm --dir content/kelly-crm-app run checkandnode --testpass.
Stop Conditions
Stop before consequential Busabase mutation when the target Space is ambiguous, the current user lacks permission, or a same-slug resource is not application-owned. Never send, publish, or otherwise mutate an external system directly from the AirApp.
What ships with it: 46 files
198.2 KB alongside SKILL.md, 19 of them executable
agents/
- openai.yaml225 B
app/
- app/accent-theme.css7.5 KB
- app/accent-theme.jsruns7.3 KB
- app/app.jsruns17.3 KB
- app/connect-gate.css5.3 KB
- app/demo-visuals.css1.4 KB
- app/demo-visuals.jsruns3.3 KB
- app/i18n/messages.jsruns8.0 KB
- app/index.html4.3 KB
- app/js/busabase-client.jsruns226 B
- app/js/config.jsruns7.3 KB
- app/js/connect-gate.jsruns9.1 KB
- app/js/crm-model.jsruns5.8 KB
- app/js/crm-views.jsruns17.6 KB
- app/js/demo-visuals-data.jsruns3.9 KB
- app/js/providers/busabase-provider.jsruns9.5 KB
- app/js/providers/demo-provider.jsruns24.2 KB
- app/js/providers/index.jsruns270 B
- app/js/resource-provisioning.jsruns10.0 KB
- app/styles.css18.9 KB
- package.json881 B
- resource-map.json716 B
- scripts/check.mjsruns1.7 KB
- server.jsruns10.4 KB
- test/crm-model.test.mjsruns2.3 KB
assets/
- screenshots/contacts.webp130 B
- screenshots/contacts-zh-CN.webp130 B
- screenshots/deals.webp131 B
- screenshots/deals-zh-CN.webp130 B
- screenshots/followups.webp130 B
- screenshots/followups-zh-CN.webp130 B
- screenshots/overview.webp130 B
- screenshots/overview-zh-CN.webp130 B
- screenshots/thumbs/contacts.webp130 B
- screenshots/thumbs/contacts-zh-CN.webp130 B
- screenshots/thumbs/deals.webp130 B
- screenshots/thumbs/deals-zh-CN.webp130 B
- screenshots/thumbs/followups.webp130 B
- screenshots/thumbs/followups-zh-CN.webp130 B
- screenshots/thumbs/overview.webp130 B
6 more files not listed here. See all 46 in the repository.