recoup-roster-onboard

Bootstrap an empty org's roster — when the account has no artists yet, gather the label's roster (names or a pasted list) and onboard them all by fanning recoup-roster-add-artist out across parallel subagents (each runs the full create → enrich chain), optionally scouting talent first. Use for "set up our roster", "we have no artists yet", "onboard our whole roster", "import these artists", or when recoup-platform-build-os / recoup-platform-connect-account finds an empty roster. For a single artist use recoup-roster-add-artist; to see the roster use recoup-roster-list-artists.

跳到安装

仓库: recoupable/skills
最近来源活动: 2026年6月26日 02:36
检测到的 SKILL.md 语言: 英语
星标: 3
分支: 2

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/recoupable/skills --skill recoup-roster-onboard

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

recoup-internal-sales

INTERNAL — Recoup staff tooling, gated by the recoup-internal keyword. Invoke ONLY when the request explicitly includes "recoup-internal" (e.g. "recoup-internal run the sales sweep"). Never use for customer-facing or artist requests. Run Recoup's daily sales sweep — walk the whole activity surface (Stripe payments, Privy logins, new catalog valuations, BOTH Attio funnels (Valuation Leads for subscriptions and Agency Leads for custom-build/advisory work), Supabase credits, scheduled tasks, and chats), turn each signal into a prioritized follow-up, then act on it: log the follow-up in Attio and draft (never send) outreach. Use when asked to "run the sales sweep", "who should we follow up with", "work the sales pipeline", "any new customers to reach out to", "who signed in / paid / ran a valuation", "who's about to churn", "what's in the agency pipeline", or "find zombie tasks we can turn off". Also covers **meeting prep for a booked call with a qualified customer** — producing the pitch, the meeting plan, and t

2026-08-26

recoup-internal-upwork

INTERNAL — Recoup staff tooling, gated by the recoup-internal keyword. Invoke ONLY when the request explicitly includes "recoup-internal" (e.g. "recoup-internal apply to this Upwork job"). Never use for customer-facing or artist requests. Find, win and close Upwork contract work end to end: run the daily pipeline, triage a client before writing anything, verify every claim against the actual repositories, draft the cover letter and screening answers, pick the right work-sample pack, set the rate, then follow up, handle the reply, run the call and convert a trial into ongoing work. Use when asked to "apply to this Upwork job", "write an Upwork proposal", "should I bid on this", "triage this client", "is this job worth connects", "find Upwork jobs worth applying to", "run the Upwork pipeline", "a client replied", "prep for the client call", "follow up on my proposals", "why is nothing converting", or when an Upwork job posting is pasted in. Requires a local workspace directory and read access to the repositorie

2026-08-21

recoup-internal-marketing

INTERNAL — Recoup staff tooling, gated by the recoup-internal keyword. Invoke ONLY when the request explicitly includes "recoup-internal" (e.g. "recoup-internal do today's marketing"). Never use for customer-facing or artist requests. The daily marketing run for one of our own social accounts, in order: read the account workspace (narrative canon, hook doctrine, video styles, post ledger), scrape the account's own socials to learn what is working and what flopped, pick today's topic (continue an arc, pull a logged idea, or draft a new one), then build the asset and hand off. Use when the user says "do today's marketing", "today's content run", "make today's video", "our hooks are weak", or asks what to post today for one of OUR OWN accounts. Runs the whole day end to end. Its stated goal: convert a free content viewer into a paying Recoup subscriber — and know which post did it; so the run opens on the funnel numbers and refuses to ship into a destination that cannot convert. **Not for a single post's copy**

2026-08-19

查看这个仓库的全部 Skills

Recoup — Onboard Roster

Bootstrap a brand-new/empty org: turn a list of artist names into a fully created + enriched roster by fanning recoup-roster-add-artist out across parallel subagents. The empty-org entry point that recoup-platform-build-os hands off to.

Procedure

Confirm the roster is actually empty. Via recoup-platform-api-access, roster-discover (GET /accounts/id -> GET /organizations -> GET /artists?org_id=…). If any artists already exist, stop — that's recoup-roster-add-artist (one more) or recoup-platform-build-os (scaffold) territory, not a bootstrap. Never run on a populated roster.

Refuse throwaway accounts. If /accounts/id resolves to an agent+…@recoupable.com email, stop and ask for a real-account credential — artists created under a throwaway key get orphaned.

Get the roster to create. Either:

the user supplies names (or a pasted / CSV list) — use those; or
they want A&R help — run recoup-research-find-talent to propose candidates, then confirm the final list with the user before creating anything (creation is a real, billable mutation on the live account).

Fan out (parallel subagents). For each confirmed artist, dispatch a subagent that runs recoup-roster-add-artist for that one name (the create -> Spotify -> research -> catalog -> socials -> knowledge-base chain; writes artists/{slug}/RECOUP.md). Run them in parallel, but keep the batch to a sane width (≈5–8 at a time); pass each subagent only its one artist plus the org/auth context. Skip any name already on the roster.

Reconcile. When the subagents finish, run recoup-roster-list-artists to verify every intended artist now exists; retry the ones that failed (never fabricate a success).

Hand back. Return to recoup-platform-build-os to scaffold / refresh the workspace around the now-populated roster.

Guardrails

API-first — never mkdir a roster. Each artist is created through recoup-roster-add-artist (which goes through the Recoup API); folders follow from the API result.

Confirm names before creating. Creating artists costs credits and writes to the live account — no silent bulk-create.

Idempotent. Skip artists that already exist; safe to re-run after a partial failure.

One artist per subagent. Keeps each chain resumable and isolates failures.

Recoup — Onboard Roster

Procedure

Refuse throwaway accounts. If /accounts/id resolves to an agent+…@recoupable.com email, stop and ask for a real-account credential — artists created under a throwaway key get orphaned.

Get the roster to create. Either:

the user supplies names (or a pasted / CSV list) — use those; or
they want A&R help — run recoup-research-find-talent to propose candidates, then confirm the final list with the user before creating anything (creation is a real, billable mutation on the live account).

Reconcile. When the subagents finish, run recoup-roster-list-artists to verify every intended artist now exists; retry the ones that failed (never fabricate a success).

Hand back. Return to recoup-platform-build-os to scaffold / refresh the workspace around the now-populated roster.

Guardrails

API-first — never mkdir a roster. Each artist is created through recoup-roster-add-artist (which goes through the Recoup API); folders follow from the API result.

Confirm names before creating. Creating artists costs credits and writes to the live account — no silent bulk-create.

Idempotent. Skip artists that already exist; safe to re-run after a partial failure.

One artist per subagent. Keeps each chain resumable and isolates failures.

recoup-roster-onboard

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills

Recoup — Onboard Roster

Procedure

Guardrails

Recoup — Onboard Roster

Procedure

Guardrails