[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JF717N88WFDK7PQBXVSTF5":3,"skill-same:01M6JF717N88WFDK7PQBXVSTF5":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6JF717N88WFDK7PQBXVSTF5","hiring-and-managing-a-team",null,"Use when hiring or onboarding an appointment setter (growth specialist), a virtual assistant, or any remote team member for an agency\u002Fcoaching business - covers role definition, pay structures, onboarding cadence, management rhythm, and how to fire correctly. Source - Grow Acquisition 3.0 (Nikk Kleinherenbrink).","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fpersonal\u002Fclient-acquisition\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"Hiring","hiring and managing a team","team","how to","assistant","source","for","role","pay","remote","agency","cadence","grow","coaching","use","growth","business","acquisition","virtual","how","2026-11-10 10:12:30",false,"---\nname: hiring-and-managing-a-team\ndescription: Use when hiring or onboarding an appointment setter (growth specialist), a virtual assistant, or any remote team member for an agency\u002Fcoaching business - covers role definition, pay structures, onboarding cadence, management rhythm, and how to fire correctly. Source - Grow Acquisition 3.0 (Nikk Kleinherenbrink).\n---\n\n# Hiring & Managing a Team\n\nPhase 4 (\"work ON the business, not IN it\"): delegate to skilled, autonomous team members. \"Most teams fail not from lack of talent but lack of leadership.\"\n\n## Know the role you're actually hiring\n\n| Role | Decides | Rate (guide) |\n|---|---|---|\n| **Virtual Assistant (Follower)** | neither what nor how; follows processes | $3-8\u002Fhr |\n| **Freelancer (Doer)** | the how, not the what (outcome given) | $10+\u002Fhr |\n| **Expert (Creator)** | the what, when, why, how | $20+\u002Fhr |\n\nDon't hire a VA for: marketing strategy, running ads\u002Ffunnels without a clear process, web dev without a process, or appointment setting (that's a trained setter role). DO hire a VA for repeatable tasks: admin, lead-gen, support, research, bookkeeping, personal assistant tasks. Philippines preferred (good English, work ethic, affordable).\n\n## Creating a VA role\n\n1. Confirm it's actually a VA (not freelancer\u002Fexpert).\n2. Main purpose: lead-gen \u002F customer support \u002F general admin (can be a mix).\n3. Full-time or part-time (budget + workload).\n4. Track your repetitive tasks over 3-5 days → \"buy back your time\" first.\n5. Add other responsibilities → write job description → post.\n\n## Hiring a Growth Specialist (appointment setter) — 8 steps\n\n1. Finish the program phases yourself first.\n2. Train them on: IG prospecting; conversations → relationships → booked meetings; weekly Q&A\u002Froleplay\u002Fcall review + shadow; daily workflow; tracking sheet; working independently.\n3. Pay model (decided on onboarding call): per qualified appointment \u002F per close (commission) \u002F per outreach \u002F per show-up \u002F base pay (cheapest). Top performers can move to base + %.\n4. Onboarding call: hours & days, goals & role, daily KPIs (e.g. 100 new DMs, 50 follow-ups), expectations, EOD + EOW reports, payment frequency (weekly recommended) + channel (PayPal\u002FWise\u002FStripe). Give access to market-analysis + tracking sheets.\n5. Start: setter hits daily\u002Fweekly KPIs, fills EOD, follows up. You monitor campaign performance and unblock.\n6. Daily calls early on to build the relationship and solve problems.\n7. Work ethic: show them the vision, make them feel part of it, celebrate wins.\n8. Monthly review on the 1st: what went well, improvement points, next-month plan.\n\n## Onboarding a VA\n\nMake an offer → Orientation call → Set up with software.\n- **Offer conversation** (zoom\u002Fslack): make offer, on-call vs scheduled, internet & power check, set expectations, Q&A → if accepted, set start date + book orientation.\n- **Orientation call (30-60 min):** share about yourself, ask about them, build schedule, go over job description, software, communicate culture, Q&A → ensure they're set up on all software.\n\n## Management rhythm\n\nCommunication via Slack (day-to-day) + Zoom (calls).\n- Daily check-ins; weekly huddle (20-30 min, near start of week); quarterly 1:1 (30-60 min).\n- First 2 weeks: a call EVERY day, 10-15 min (role, SOPs, support).\n- Next 30 days: 2-3 calls\u002Fweek, then reduce to what's needed.\n- **Culture = values + beliefs + standards.** Aim to be their favourite client; even great coaching fails in a toxic culture. Self-audit: do they feel valued, see their impact, believe the work matters, are you upfront vs passive-aggressive?\n\n## Handling issues & firing\n\nMost issues are prevented by strong onboarding. When they arise (lateness, tasks wrong\u002Fundone): address immediately — Slack for small, a call for serious. Be clear, repeat the key parts, reset expectations, get confirmation in writing. **No one should be surprised to be fired** — have the lead-up conversations first.\n\nFiring sequence: wait until they're offline → change passwords \u002F revoke LastPass → remove chat & software access → double-check access removed → inform your team → then reach out and explain.\n\n## Related skills\n\nOnce the setter is hired and onboarded, they need a lead workflow to work from. For reactivating cold\u002Fstale CRM leads (tiering, scripts, email sequences, API pipeline moves), load:\n\n- **crm-reactivation-campaigns** — audit stale CRM data, tier leads by stage, write DM scripts per tier, build email sequences, and tag\u002Fmove via API.\n\n## Common mistakes\n\n- Hiring a VA for strategy\u002Fads\u002Fsetting work that needs an expert or trained setter.\n- No repetitive-task tracking first, so the role is vague and time isn't actually bought back.\n- Skipping the daily-call onboarding window — the relationship and standards never set.\n- Firing as a surprise with no documented lead-up conversations.\n- Cutting access AFTER you message them instead of before.","# Hiring & Managing a Team\n\nPhase 4 (\"work ON the business, not IN it\"): delegate to skilled, autonomous team members. \"Most teams fail not from lack of talent but lack of leadership.\"\n\n## Know the role you're actually hiring\n\n| Role | Decides | Rate (guide) |\n|---|---|---|\n| **Virtual Assistant (Follower)** | neither what nor how; follows processes | $3-8\u002Fhr |\n| **Freelancer (Doer)** | the how, not the what (outcome given) | $10+\u002Fhr |\n| **Expert (Creator)** | the what, when, why, how | $20+\u002Fhr |\n\nDon't hire a VA for: marketing strategy, running ads\u002Ffunnels without a clear process, web dev without a process, or appointment setting (that's a trained setter role). DO hire a VA for repeatable tasks: admin, lead-gen, support, research, bookkeeping, personal assistant tasks. Philippines preferred (good English, work ethic, affordable).\n\n## Creating a VA role\n\n1. Confirm it's actually a VA (not freelancer\u002Fexpert).\n2. Main purpose: lead-gen \u002F customer support \u002F general admin (can be a mix).\n3. Full-time or part-time (budget + workload).\n4. Track your repetitive tasks over 3-5 days → \"buy back your time\" first.\n5. Add other responsibilities → write job description → post.\n\n## Hiring a Growth Specialist (appointment setter) — 8 steps\n\n1. Finish the program phases yourself first.\n2. Train them on: IG prospecting; conversations → relationships → booked meetings; weekly Q&A\u002Froleplay\u002Fcall review + shadow; daily workflow; tracking sheet; working independently.\n3. Pay model (decided on onboarding call): per qualified appointment \u002F per close (commission) \u002F per outreach \u002F per show-up \u002F base pay (cheapest). Top performers can move to base + %.\n4. Onboarding call: hours & days, goals & role, daily KPIs (e.g. 100 new DMs, 50 follow-ups), expectations, EOD + EOW reports, payment frequency (weekly recommended) + channel (PayPal\u002FWise\u002FStripe). Give access to market-analysis + tracking sheets.\n5. Start: setter hits daily\u002Fweekly KPIs, fills EOD, follows up. You monitor campaign performance and unblock.\n6. Daily calls early on to build the relationship and solve problems.\n7. Work ethic: show them the vision, make them feel part of it, celebrate wins.\n8. Monthly review on the 1st: what went well, improvement points, next-month plan.\n\n## Onboarding a VA\n\nMake an offer → Orientation call → Set up with software.\n- **Offer conversation** (zoom\u002Fslack): make offer, on-call vs scheduled, internet & power check, set expectations, Q&A → if accepted, set start date + book orientation.\n- **Orientation call (30-60 min):** share about yourself, ask about them, build schedule, go over job description, software, communicate culture, Q&A → ensure they're set up on all software.\n\n## Management rhythm\n\nCommunication via Slack (day-to-day) + Zoom (calls).\n- Daily check-ins; weekly huddle (20-30 min, near start of week); quarterly 1:1 (30-60 min).\n- First 2 weeks: a call EVERY day, 10-15 min (role, SOPs, support).\n- Next 30 days: 2-3 calls\u002Fweek, then reduce to what's needed.\n- **Culture = values + beliefs + standards.** Aim to be their favourite client; even great coaching fails in a toxic culture. Self-audit: do they feel valued, see their impact, believe the work matters, are you upfront vs passive-aggressive?\n\n## Handling issues & firing\n\nMost issues are prevented by strong onboarding. When they arise (lateness, tasks wrong\u002Fundone): address immediately — Slack for small, a call for serious. Be clear, repeat the key parts, reset expectations, get confirmation in writing. **No one should be surprised to be fired** — have the lead-up conversations first.\n\nFiring sequence: wait until they're offline → change passwords \u002F revoke LastPass → remove chat & software access → double-check access removed → inform your team → then reach out and explain.\n\n## Related skills\n\nOnce the setter is hired and onboarded, they need a lead workflow to work from. For reactivating cold\u002Fstale CRM leads (tiering, scripts, email sequences, API pipeline moves), load:\n\n- **crm-reactivation-campaigns** — audit stale CRM data, tier leads by stage, write DM scripts per tier, build email sequences, and tag\u002Fmove via API.\n\n## Common mistakes\n\n- Hiring a VA for strategy\u002Fads\u002Fsetting work that needs an expert or trained setter.\n- No repetitive-task tracking first, so the role is vague and time isn't actually bought back.\n- Skipping the daily-call onboarding window — the relationship and standards never set.\n- Firing as a surprise with no documented lead-up conversations.\n- Cutting access AFTER you message them instead of before.",{"name":5,"description":7},"master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fpersonal\u002Fclient-acquisition",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add S3YED\u002Fappie-kit --skill hiring-and-managing-a-team",{"tool":62,"command":63},"bunx","bunx skills add S3YED\u002Fappie-kit --skill hiring-and-managing-a-team",{"tool":65,"command":66},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill hiring-and-managing-a-team","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fpersonal\u002Fclient-acquisition\u002FSKILL.md",true,[],[71,107,140,165,196,220],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":88,"publishedAt":43},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[77,82,85],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":86,"categoryName":87,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发",[89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":119,"publishedAt":43},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[113,116],{"categoryNo":114,"categoryName":115,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000032","设计师",[120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":148,"publishedAt":43},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[146,147],{"categoryNo":86,"categoryName":87,"taxonomyType":80,"taxonomyTypeDesc":81},{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},[121,149,125,150,151,152,127,153,154,155,156,157,158,159,160,161,162,163,164,28],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":175,"publishedAt":43},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[171,174],{"categoryNo":172,"categoryName":173,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":86,"categoryName":87,"taxonomyType":80,"taxonomyTypeDesc":81},[176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195],"deployment","vercel deployment","vercel","macos","cli","linux","windows","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":203,"publishedAt":43},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[202],{"categoryNo":86,"categoryName":87,"taxonomyType":80,"taxonomyTypeDesc":81},[204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,29],"workflows","quality","software","software quality workflows","review","tdd","workflow","commit","debugging","code","debugger","pre-commit","investigation","code simplification","user","simplification",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":233,"publishedAt":43},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[226,229,232],{"categoryNo":227,"categoryName":228,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":230,"categoryName":231,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":86,"categoryName":87,"taxonomyType":80,"taxonomyTypeDesc":81},[234,235,236,237,238,239,240,241,179,242,243,127,244,182,245,213,246,247,248,249],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","patterns","test-driven-development"]