[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M786FM3MBRMP3GWW8TMMXWYF":3,"skill-same:01M786FM3MBRMP3GWW8TMMXWYF":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M786FM3MBRMP3GWW8TMMXWYF","cs-onboard",null,"Founder onboarding interview that captures company context across 7 dimensions. Invoke with \u002Fcs:setup for initial interview or \u002Fcs:update for quarterly refresh. Generates ~\u002F.claude\u002Fcompany-context.md used by all C-suite advisor skills. Use when setting up the C-suite advisors for the first time, or when company context is missing or more than 90 days old — e.g. after a fundraise or pivot.","sat-yam09\u002Fomni-skill","sat-yam09","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F179735311?v=4","01M785VKCWM5DDJGXKCV944P8A","Satyam Choudhary","01M785VKDXSF7W02KZ29ZE0GSY",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fcs-onboard\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"cs-onboard\"\ndescription: \"Founder onboarding interview that captures company context across 7 dimensions. Invoke with \u002Fcs:setup for initial interview or \u002Fcs:update for quarterly refresh. Generates ~\u002F.claude\u002Fcompany-context.md used by all C-suite advisor skills. Use when setting up the C-suite advisors for the first time, or when company context is missing or more than 90 days old — e.g. after a fundraise or pivot.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: orchestration\n  updated: 2026-03-05\n  frameworks: founder-interview, context-capture, quarterly-refresh\n---\n\n# C-Suite Onboarding\n\nStructured founder interview that builds the company context file powering every C-suite advisor. One 45-minute conversation. Persistent context across all roles.\n\n## Commands\n\n- `\u002Fcs:setup` — Full onboarding interview (~45 min, 7 dimensions)\n- `\u002Fcs:update` — Quarterly refresh (~15 min, \"what changed?\")\n\n## Keywords\ncs:setup, cs:update, company context, founder interview, onboarding, company profile, c-suite setup, advisor setup\n\n---\n\n## Conversation Principles\n\nBe a conversation, not an interrogation. Ask one question at a time. Follow threads. Reflect back: \"So the real issue sounds like X — is that right?\" Watch for what they skip — that's where the real story lives. Never read a list of questions.\n\nOpen with: *\"Tell me about the company in your own words — what are you building and why does it matter?\"*\n\n---\n\n## 7 Interview Dimensions\n\n### 1. Company Identity\nCapture: what they do, who it's for, the real founding \"why,\" one-sentence pitch, non-negotiable values.\nKey probe: *\"What's a value you'd fire someone over violating?\"*\nRed flag: Values that sound like marketing copy.\n\n### 2. Stage & Scale\nCapture: headcount (FT vs contractors), revenue range, runway, stage (pre-PMF \u002F scaling \u002F optimizing), what broke in last 90 days.\nKey probe: *\"If you had to label your stage — still finding PMF, scaling what works, or optimizing?\"*\n\n### 3. Founder Profile\nCapture: self-identified superpower, acknowledged blind spots, archetype (product\u002Fsales\u002Ftechnical\u002Foperator), what actually keeps them up at night.\nKey probe: *\"What would your co-founder say you should stop doing?\"*\nRed flag: No blind spots, or weakness framed as a strength.\n\n### 4. Team & Culture\nCapture: team in 3 words, last real conflict and resolution, which values are real vs aspirational, strongest and weakest leader.\nKey probe: *\"Which of your stated values is most real? Which is a poster on the wall?\"*\nRed flag: \"We have no conflict.\"\n\n### 5. Market & Competition\nCapture: who's winning and why (honest version), real unfair advantage, the one competitive move that could hurt them.\nKey probe: *\"What's your real unfair advantage — not the investor version?\"*\nRed flag: \"We have no real competition.\"\n\n### 6. Current Challenges\nCapture: priority stack-rank across product\u002Fgrowth\u002Fpeople\u002Fmoney\u002Foperations, the decision they've been avoiding, the \"one extra day\" answer.\nKey probe: *\"What's the decision you've been putting off for weeks?\"*\nNote: The \"extra day\" answer reveals true priorities.\n\n### 7. Goals & Ambition\nCapture: 12-month target (specific), 36-month target (directional), exit vs build-forever orientation, personal success definition.\nKey probe: *\"What does success look like for you personally — separate from the company?\"*\n\n---\n\n## Output: company-context.md\n\nAfter the interview, generate `~\u002F.claude\u002Fcompany-context.md` using `templates\u002Fcompany-context-template.md`.\n\nFill every section. Write `[not captured]` for unknowns — never leave blank. Add timestamp, mark as `fresh`.\n\nTell the founder: *\"I've captured everything in your company context. Every advisor will use this to give specific, relevant advice. Run \u002Fcs:update in 90 days to keep it current.\"*\n\n---\n\n## \u002Fcs:update — Quarterly Refresh\n\n**Trigger:** Every 90 days or after a major change. Duration: ~15 minutes.\n\nOpen with: *\"It's been [X time] since we did your company context. What's changed?\"*\n\nWalk each dimension with one \"what changed?\" question:\n1. Identity: same mission or shifted?\n2. Scale: team, revenue, runway now?\n3. Founder: role or what's stretching you?\n4. Team: any leadership changes?\n5. Market: any competitive surprises?\n6. Challenges: #1 problem now vs 90 days ago?\n7. Goals: still on track for 12-month target?\n\nUpdate the context file, refresh timestamp, reset to `fresh`.\n\n---\n\n## Context File Location\n\n`~\u002F.claude\u002Fcompany-context.md` — single source of truth for all C-suite skills. Do not move it. Do not create duplicates.\n\n## References\n- `templates\u002Fcompany-context-template.md` — blank template for output\n- `references\u002Finterview-guide.md` — deep interview craft: probes, red flags, handling reluctant founders\n","# C-Suite Onboarding\n\nStructured founder interview that builds the company context file powering every C-suite advisor. One 45-minute conversation. Persistent context across all roles.\n\n## Commands\n\n- `\u002Fcs:setup` — Full onboarding interview (~45 min, 7 dimensions)\n- `\u002Fcs:update` — Quarterly refresh (~15 min, \"what changed?\")\n\n## Keywords\ncs:setup, cs:update, company context, founder interview, onboarding, company profile, c-suite setup, advisor setup\n\n---\n\n## Conversation Principles\n\nBe a conversation, not an interrogation. Ask one question at a time. Follow threads. Reflect back: \"So the real issue sounds like X — is that right?\" Watch for what they skip — that's where the real story lives. Never read a list of questions.\n\nOpen with: *\"Tell me about the company in your own words — what are you building and why does it matter?\"*\n\n---\n\n## 7 Interview Dimensions\n\n### 1. Company Identity\nCapture: what they do, who it's for, the real founding \"why,\" one-sentence pitch, non-negotiable values.\nKey probe: *\"What's a value you'd fire someone over violating?\"*\nRed flag: Values that sound like marketing copy.\n\n### 2. Stage & Scale\nCapture: headcount (FT vs contractors), revenue range, runway, stage (pre-PMF \u002F scaling \u002F optimizing), what broke in last 90 days.\nKey probe: *\"If you had to label your stage — still finding PMF, scaling what works, or optimizing?\"*\n\n### 3. Founder Profile\nCapture: self-identified superpower, acknowledged blind spots, archetype (product\u002Fsales\u002Ftechnical\u002Foperator), what actually keeps them up at night.\nKey probe: *\"What would your co-founder say you should stop doing?\"*\nRed flag: No blind spots, or weakness framed as a strength.\n\n### 4. Team & Culture\nCapture: team in 3 words, last real conflict and resolution, which values are real vs aspirational, strongest and weakest leader.\nKey probe: *\"Which of your stated values is most real? Which is a poster on the wall?\"*\nRed flag: \"We have no conflict.\"\n\n### 5. Market & Competition\nCapture: who's winning and why (honest version), real unfair advantage, the one competitive move that could hurt them.\nKey probe: *\"What's your real unfair advantage — not the investor version?\"*\nRed flag: \"We have no real competition.\"\n\n### 6. Current Challenges\nCapture: priority stack-rank across product\u002Fgrowth\u002Fpeople\u002Fmoney\u002Foperations, the decision they've been avoiding, the \"one extra day\" answer.\nKey probe: *\"What's the decision you've been putting off for weeks?\"*\nNote: The \"extra day\" answer reveals true priorities.\n\n### 7. Goals & Ambition\nCapture: 12-month target (specific), 36-month target (directional), exit vs build-forever orientation, personal success definition.\nKey probe: *\"What does success look like for you personally — separate from the company?\"*\n\n---\n\n## Output: company-context.md\n\nAfter the interview, generate `~\u002F.claude\u002Fcompany-context.md` using `templates\u002Fcompany-context-template.md`.\n\nFill every section. Write `[not captured]` for unknowns — never leave blank. Add timestamp, mark as `fresh`.\n\nTell the founder: *\"I've captured everything in your company context. Every advisor will use this to give specific, relevant advice. Run \u002Fcs:update in 90 days to keep it current.\"*\n\n---\n\n## \u002Fcs:update — Quarterly Refresh\n\n**Trigger:** Every 90 days or after a major change. Duration: ~15 minutes.\n\nOpen with: *\"It's been [X time] since we did your company context. What's changed?\"*\n\nWalk each dimension with one \"what changed?\" question:\n1. Identity: same mission or shifted?\n2. Scale: team, revenue, runway now?\n3. Founder: role or what's stretching you?\n4. Team: any leadership changes?\n5. Market: any competitive surprises?\n6. Challenges: #1 problem now vs 90 days ago?\n7. Goals: still on track for 12-month target?\n\nUpdate the context file, refresh timestamp, reset to `fresh`.\n\n---\n\n## Context File Location\n\n`~\u002F.claude\u002Fcompany-context.md` — single source of truth for all C-suite skills. Do not move it. Do not create duplicates.\n\n## References\n- `templates\u002Fcompany-context-template.md` — blank template for output\n- `references\u002Finterview-guide.md` — deep interview craft: probes, red flags, handling reluctant founders\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"domain":26,"updated":27,"version":28,"category":29,"frameworks":30},"Alireza Rezvani","orchestration",1772668800000,"1.0.0","c-level","founder-interview, context-capture, quarterly-refresh","main","d6d5c82ab65b4a4ffdee7e280959f3fb8451ad4a","skills\u002Fcs-onboard","https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill","https:\u002F\u002Fgithub.com\u002Fsat-yam09","2026-07-06 00:53:30",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add sat-yam09\u002Fomni-skill --skill cs-onboard",{"tool":43,"command":44},"bunx","bunx skills add sat-yam09\u002Fomni-skill --skill cs-onboard",{"tool":46,"command":47},"pnpm","pnpm dlx skills add sat-yam09\u002Fomni-skill --skill cs-onboard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fcs-onboard\u002FSKILL.md",true,[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Finterview-guide.md","REFERENCE","参考文档",7739,"https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fcs-onboard\u002Freferences\u002Finterview-guide.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"templates\u002Fcompany-context-template.md",3100,"https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fcs-onboard\u002Ftemplates\u002Fcompany-context-template.md",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M787Z42K68F3YYHVGX19GHFE","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M787YY3VXY14Z17NRA1RBG4Q","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M787XSPKX8KF9RWR2VG4JQN9","webinar-marketing","When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fwebinar-marketing\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M787XE49FGB5FA588NEXZDM7","vpe-advisor","VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad\u002Ftribe\u002Fchapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.","https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fvpe-advisor\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M787WXZX8SYT198PW5W62GHH","vendor-management","Use when reviewing, scoring, or auditing third-party SaaS \u002F vendor relationships — running a vendor scorecard with industry tuning, tracking SLA compliance with credit-claim flags, classifying third-party risk across 4 risk vectors, preparing a tier-1 vendor review, or auditing the SaaS portfolio. Forks context so large vendor catalogs (50-500 line items) and SLA logs don't pollute the parent thread. Triggers on \"vendor SLA\", \"vendor scorecard\", \"third-party risk\", \"TPRM\", \"vendor review\", \"supplier performance\", \"vendor health check\", \"renewal review\".","https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-management\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M787SQPQ26ENTE51G9RGK769","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[]]