← ClaudeAtlas

kelly-followupslisted

Busabase-backed App-in-Skill for one thing only — record who you need to follow up with after a meeting, see what is due today, mark it done. Use when the user invokes $kelly-followups or /kelly-followups, mentions a followup, follow-up, meeting action item, or wants a lightweight daily reminder of who to check in with, without a full project-management tool.
mr-kelly/skills · ★ 5 · AI & Automation · score 71
Install: claude install-skill mr-kelly/skills
# Kelly Followups ## Overview Kelly Followups 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 does exactly one thing, on purpose: after a meeting, record who you need to follow up with and what needs doing; open the app any morning and see today's list; mark each one done. ## Origin This skill exists as a worked example of the `$kelly-ideas` → `$kelly-app-creator` handoff: a real idea ("周会太多我总忘记谁该跟进" — too many weekly meetings, can never remember who to follow up with) was interrogated through `$kelly-ideas`'s BRD → MRD → PRD ladder, and the resulting PRD's own non-goals — no full project management, no calendar sync, no notification delivery, no team permissions — are exactly this app's scope. It is intentionally this small; growing it into a project-management tool is a different PRD, not a feature request on this one. ## Mandatory Dependencies 1. Read and follow `$busabase` for connection, target Space, node discovery, ChangeRequests, review, merge, and trusted mutations. 2. Read and follow `$kelly-app-creator` for the App-in-Skill artifact contract, the UI contract, and AirApp delivery. ## Busabase Resources | Resource | Holds | | --- | --- | | `followups` | One row per followup: who, what, when it's due, and whether it's done | ## Authentication Connection bootstrap only: `BU