kelly-instructor-sourcinglisted

Run a Busabase-backed sandbox desk for scoring and triaging course-instructor ("讲师") candidates found on a recruiting-style platform. Use whenever the user invokes $kelly-instructor-sourcing or /kelly-instructor-sourcing, wants a lightweight instructor candidate tracker, needs to score sourcing-platform leads against a three-axis rubric (background endorsement, expertise depth/breadth, teaching-service ability) before reaching out, or wants to log a WeChat add without building a live-connected outreach tool. Three subcommands - setup, criteria, review - plus the desk itself. v1 is sandbox-only — every dataset is deterministic mock data, it never connects to a real sourcing-platform or messaging account, and it never sends a message or automates a WeChat add - that stays entirely human-performed outside the app.
mr-kelly/skills · ★ 5 · AI & Automation · score 71

Install: claude install-skill mr-kelly/skills

# Kelly Instructor Sourcing Turn a rough "who are we looking for" hypothesis into a scored, triaged pool of 講師/instructor candidates: capture the search criteria and a three-axis scoring rubric, score each candidate a human found on a recruiting-style platform, and record the connection state as it happens in the real world. Everything in v1 is sandbox-only — see Product Boundary. ## Subcommands | Invocation | What to do | | --- | --- | | `/kelly-instructor-sourcing setup` | Create or adopt the Busabase Folder and two Bases, then verify them. | | `/kelly-instructor-sourcing criteria` | Capture or edit the search-criteria hypothesis and the three-axis scoring rubric. | | `/kelly-instructor-sourcing review` | Enter or update candidate leads, score them against the rubric, and move them through the queue. | | `/kelly-instructor-sourcing` | Open the desk and report the current bounded next step. | Run `setup`, then `criteria`, then `review` the first time. Afterwards, `review` repeats as new candidates surface. There is no `send` subcommand: first-stage scope is 获取信息 → 建立连接 → 录入数据 only, and the actual WeChat exchange happens manually outside this app — `review` records that it happened, it never performs it. ## Dependencies Before changing the app: 1. Read `$kelly-app-skill-creator` for product behavior, responsive UI, and the canonical `content/kelly-instructor-sourcing-app/` artifact. 2. Read `$busabase` for target Space, ChangeRequests, review, merge, and Vault behavior