[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78620NKW02DP9BYFVFCE5Q0":3,"skill-same:01M78620NKW02DP9BYFVFCE5Q0":65},{"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},"01M78620NKW02DP9BYFVFCE5Q0","board-meeting",null,"Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes \u002Fcs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.","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\u002Fboard-meeting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"board-meeting\"\ndescription: \"Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes \u002Fcs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: board-protocol\n  updated: 2026-03-05\n  frameworks: 6-phase-board, two-layer-memory, independent-contributions\n---\n\n# Board Meeting Protocol\n\nStructured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions.\n\n## Keywords\nboard meeting, executive deliberation, strategic decision, C-suite, multi-agent, \u002Fcs:boardroom, founder review, decision extraction, independent perspectives\n\n## Invoke\n`\u002Fcs:boardroom [topic]` — e.g. `\u002Fcs:boardroom Should we expand to Spain in Q3?`\n\n---\n\n## The 6-Phase Protocol\n\n### PHASE 1: Context Gathering\n1. Load `~\u002F.claude\u002Fcompany-context.md`\n2. Load Layer 2 approved decisions from `~\u002F.claude\u002Fdecisions\u002Fapproved\u002F` **(Layer 2 ONLY — never raw transcripts)**\n3. Reset session state — no bleed from previous conversations\n4. Present agenda + activated roles → wait for founder confirmation\n\n**Chief of Staff selects relevant roles** based on topic (not all 14 every time):\n| Topic | Activate |\n|-------|----------|\n| Market expansion | CEO, CMO, CFO, CRO, COO |\n| Product direction | CEO, CPO, CTO, CMO |\n| Hiring\u002Forg | CEO, CHRO, CFO, COO (+ VPE for eng hiring) |\n| Pricing | CMO, CFO, CRO, CPO |\n| Technology | CTO, CPO, CFO, CISO |\n| Contracts \u002F term sheets \u002F legal exposure | GC, CEO, CFO |\n| Data strategy \u002F training-data rights | CDO, CAIO, GC, CISO |\n| AI strategy \u002F model selection \u002F AI risk | CAIO, CTO, CDO, CFO |\n| Retention \u002F churn \u002F customer success | CCO, CRO, CPO |\n| Eng delivery \u002F DORA \u002F team structure | VPE, CTO, CHRO, CFO |\n\n---\n\n### PHASE 2: Independent Contributions (ISOLATED)\n\n**No cross-pollination. Each agent runs before seeing others' outputs.**\n\nOrder: Research (if needed) → CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO → GC → CDO → CAIO → CCO → VPE (activated roles only)\n\n**Reasoning techniques:** CEO: Tree of Thought (3 futures) | CFO: Chain of Thought (show the math) | CMO: Recursion of Thought (draft→critique→refine) | CPO: First Principles | CRO: Chain of Thought (pipeline math) | COO: Step by Step (process map) | CTO: ReAct (research→analyze→act) | CISO: Risk-Based (P×I) | CHRO: Empathy + Data | GC: Risk-Based (clause exposure) | CDO: Decision-Driven (what decision does this data drive) | CAIO: Eval-Demanding (no eval, no ship) | CCO: Retention-Obsessed (GRR over NRR) | VPE: Throughput-First (cycle-time math)\n\n**Contribution format (max 5 key points, self-verified):**\n```\n## [ROLE] — [DATE]\n\nKey points (max 5):\n• [Finding] — [VERIFIED\u002FASSUMED] — 🟢\u002F🟡\u002F🔴\n• [Finding] — [VERIFIED\u002FASSUMED] — 🟢\u002F🟡\u002F🔴\n\nRecommendation: [clear position]\nConfidence: High \u002F Medium \u002F Low\nSource: [where the data came from]\nWhat would change my mind: [specific condition]\n```\n\nEach agent self-verifies before contributing: source attribution, assumption audit, confidence scoring. No untagged claims.\n\n---\n\n### PHASE 3: Critic Analysis\nExecutive Mentor receives ALL Phase 2 outputs simultaneously. Role: adversarial reviewer, not synthesizer.\n\nChecklist:\n- Where did agents agree too easily? (suspicious consensus = red flag)\n- What assumptions are shared but unvalidated?\n- Who is missing from the room? (customer voice? front-line ops?)\n- What risk has nobody mentioned?\n- Which agent operated outside their domain?\n\n---\n\n### PHASE 4: Synthesis\nChief of Staff delivers using the **Board Meeting Output** format (defined in `..\u002Fagent-protocol\u002FSKILL.md`):\n- Decision Required (one sentence)\n- Perspectives (one line per contributing role)\n- Where They Agree \u002F Where They Disagree\n- Critic's View (the uncomfortable truth)\n- Recommended Decision + Action Items (owners, deadlines)\n- Your Call (options if founder disagrees)\n\n---\n\n### PHASE 5: Human in the Loop ⏸️\n\n**Full stop. Wait for the founder.**\n\n```\n⏸️ FOUNDER REVIEW — [Paste synthesis]\n\nOptions: ✅ Approve | ✏️ Modify | ❌ Reject | ❓ Ask follow-up\n```\n\n**Rules:**\n- User corrections OVERRIDE agent proposals. No pushback. No \"but the CFO said...\"\n- 30-min inactivity → auto-close as \"pending review\"\n- Reopen any time with `\u002Fcs:boardroom resume`\n\n---\n\n### PHASE 6: Decision Extraction\nAfter founder approval:\n- **Layer 1:** Write full transcript → `~\u002F.claude\u002Fdecisions\u002Fraw\u002FYYYY-MM-DD-\u003Cslug>.md`\n- **Layer 2:** Write approved decision record → `~\u002F.claude\u002Fdecisions\u002Fapproved\u002FYYYY-MM-DD-\u003Cslug>.md` and append to the index `~\u002F.claude\u002Fdecisions\u002Fapproved\u002Fdecisions.md`\n- Mark rejected proposals `[DO_NOT_RESURFACE]`\n- Confirm to founder with count of decisions logged, actions tracked, flags added\n\n---\n\n## Memory Structure\n\nUses the canonical two-layer decision memory (see `..\u002Fagent-protocol\u002FSKILL.md` → \"Decision Memory (Canonical Layout)\"):\n\n```\n~\u002F.claude\u002Fdecisions\u002F\n├── raw\u002FYYYY-MM-DD-\u003Cslug>.md        # Layer 1 — full transcripts (never auto-loaded)\n├── raw\u002Farchive\u002FYYYY\u002F               # Raw transcripts after 90 days\n├── approved\u002FYYYY-MM-DD-\u003Cslug>.md   # Layer 2 — founder-approved records (Phase 1 loads these)\n└── approved\u002Fdecisions.md           # Layer 2 index — append-only\n```\n\n**Future meetings load Layer 2 only.** Never Layer 1. This prevents hallucinated consensus.\n\nMigration: a legacy `memory\u002Fboard-meetings\u002F` folder may exist from earlier versions; read it for history but write new transcripts and decisions to `~\u002F.claude\u002Fdecisions\u002F`.\n\n---\n\n## Failure Mode Quick Reference\n| Failure | Fix |\n|---------|-----|\n| Groupthink (all agree) | Re-run Phase 2 isolated; force \"strongest argument against\" |\n| Analysis paralysis | Cap at 5 points; force recommendation even with Low confidence |\n| Bikeshedding | Log as async action item; return to main agenda |\n| Role bleed (CFO making product calls) | Critic flags; exclude from synthesis |\n| Layer contamination | Phase 1 loads `~\u002F.claude\u002Fdecisions\u002Fapproved\u002F` only — hard rule |\n\n---\n\n## References\n- `templates\u002Fmeeting-agenda.md` — agenda format\n- `templates\u002Fmeeting-minutes.md` — final output format\n- `references\u002Fmeeting-facilitation.md` — conflict handling, timing, failure modes\n","# Board Meeting Protocol\n\nStructured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions.\n\n## Keywords\nboard meeting, executive deliberation, strategic decision, C-suite, multi-agent, \u002Fcs:boardroom, founder review, decision extraction, independent perspectives\n\n## Invoke\n`\u002Fcs:boardroom [topic]` — e.g. `\u002Fcs:boardroom Should we expand to Spain in Q3?`\n\n---\n\n## The 6-Phase Protocol\n\n### PHASE 1: Context Gathering\n1. Load `~\u002F.claude\u002Fcompany-context.md`\n2. Load Layer 2 approved decisions from `~\u002F.claude\u002Fdecisions\u002Fapproved\u002F` **(Layer 2 ONLY — never raw transcripts)**\n3. Reset session state — no bleed from previous conversations\n4. Present agenda + activated roles → wait for founder confirmation\n\n**Chief of Staff selects relevant roles** based on topic (not all 14 every time):\n| Topic | Activate |\n|-------|----------|\n| Market expansion | CEO, CMO, CFO, CRO, COO |\n| Product direction | CEO, CPO, CTO, CMO |\n| Hiring\u002Forg | CEO, CHRO, CFO, COO (+ VPE for eng hiring) |\n| Pricing | CMO, CFO, CRO, CPO |\n| Technology | CTO, CPO, CFO, CISO |\n| Contracts \u002F term sheets \u002F legal exposure | GC, CEO, CFO |\n| Data strategy \u002F training-data rights | CDO, CAIO, GC, CISO |\n| AI strategy \u002F model selection \u002F AI risk | CAIO, CTO, CDO, CFO |\n| Retention \u002F churn \u002F customer success | CCO, CRO, CPO |\n| Eng delivery \u002F DORA \u002F team structure | VPE, CTO, CHRO, CFO |\n\n---\n\n### PHASE 2: Independent Contributions (ISOLATED)\n\n**No cross-pollination. Each agent runs before seeing others' outputs.**\n\nOrder: Research (if needed) → CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO → GC → CDO → CAIO → CCO → VPE (activated roles only)\n\n**Reasoning techniques:** CEO: Tree of Thought (3 futures) | CFO: Chain of Thought (show the math) | CMO: Recursion of Thought (draft→critique→refine) | CPO: First Principles | CRO: Chain of Thought (pipeline math) | COO: Step by Step (process map) | CTO: ReAct (research→analyze→act) | CISO: Risk-Based (P×I) | CHRO: Empathy + Data | GC: Risk-Based (clause exposure) | CDO: Decision-Driven (what decision does this data drive) | CAIO: Eval-Demanding (no eval, no ship) | CCO: Retention-Obsessed (GRR over NRR) | VPE: Throughput-First (cycle-time math)\n\n**Contribution format (max 5 key points, self-verified):**\n```\n## [ROLE] — [DATE]\n\nKey points (max 5):\n• [Finding] — [VERIFIED\u002FASSUMED] — 🟢\u002F🟡\u002F🔴\n• [Finding] — [VERIFIED\u002FASSUMED] — 🟢\u002F🟡\u002F🔴\n\nRecommendation: [clear position]\nConfidence: High \u002F Medium \u002F Low\nSource: [where the data came from]\nWhat would change my mind: [specific condition]\n```\n\nEach agent self-verifies before contributing: source attribution, assumption audit, confidence scoring. No untagged claims.\n\n---\n\n### PHASE 3: Critic Analysis\nExecutive Mentor receives ALL Phase 2 outputs simultaneously. Role: adversarial reviewer, not synthesizer.\n\nChecklist:\n- Where did agents agree too easily? (suspicious consensus = red flag)\n- What assumptions are shared but unvalidated?\n- Who is missing from the room? (customer voice? front-line ops?)\n- What risk has nobody mentioned?\n- Which agent operated outside their domain?\n\n---\n\n### PHASE 4: Synthesis\nChief of Staff delivers using the **Board Meeting Output** format (defined in `..\u002Fagent-protocol\u002FSKILL.md`):\n- Decision Required (one sentence)\n- Perspectives (one line per contributing role)\n- Where They Agree \u002F Where They Disagree\n- Critic's View (the uncomfortable truth)\n- Recommended Decision + Action Items (owners, deadlines)\n- Your Call (options if founder disagrees)\n\n---\n\n### PHASE 5: Human in the Loop ⏸️\n\n**Full stop. Wait for the founder.**\n\n```\n⏸️ FOUNDER REVIEW — [Paste synthesis]\n\nOptions: ✅ Approve | ✏️ Modify | ❌ Reject | ❓ Ask follow-up\n```\n\n**Rules:**\n- User corrections OVERRIDE agent proposals. No pushback. No \"but the CFO said...\"\n- 30-min inactivity → auto-close as \"pending review\"\n- Reopen any time with `\u002Fcs:boardroom resume`\n\n---\n\n### PHASE 6: Decision Extraction\nAfter founder approval:\n- **Layer 1:** Write full transcript → `~\u002F.claude\u002Fdecisions\u002Fraw\u002FYYYY-MM-DD-\u003Cslug>.md`\n- **Layer 2:** Write approved decision record → `~\u002F.claude\u002Fdecisions\u002Fapproved\u002FYYYY-MM-DD-\u003Cslug>.md` and append to the index `~\u002F.claude\u002Fdecisions\u002Fapproved\u002Fdecisions.md`\n- Mark rejected proposals `[DO_NOT_RESURFACE]`\n- Confirm to founder with count of decisions logged, actions tracked, flags added\n\n---\n\n## Memory Structure\n\nUses the canonical two-layer decision memory (see `..\u002Fagent-protocol\u002FSKILL.md` → \"Decision Memory (Canonical Layout)\"):\n\n```\n~\u002F.claude\u002Fdecisions\u002F\n├── raw\u002FYYYY-MM-DD-\u003Cslug>.md        # Layer 1 — full transcripts (never auto-loaded)\n├── raw\u002Farchive\u002FYYYY\u002F               # Raw transcripts after 90 days\n├── approved\u002FYYYY-MM-DD-\u003Cslug>.md   # Layer 2 — founder-approved records (Phase 1 loads these)\n└── approved\u002Fdecisions.md           # Layer 2 index — append-only\n```\n\n**Future meetings load Layer 2 only.** Never Layer 1. This prevents hallucinated consensus.\n\nMigration: a legacy `memory\u002Fboard-meetings\u002F` folder may exist from earlier versions; read it for history but write new transcripts and decisions to `~\u002F.claude\u002Fdecisions\u002F`.\n\n---\n\n## Failure Mode Quick Reference\n| Failure | Fix |\n|---------|-----|\n| Groupthink (all agree) | Re-run Phase 2 isolated; force \"strongest argument against\" |\n| Analysis paralysis | Cap at 5 points; force recommendation even with Low confidence |\n| Bikeshedding | Log as async action item; return to main agenda |\n| Role bleed (CFO making product calls) | Critic flags; exclude from synthesis |\n| Layer contamination | Phase 1 loads `~\u002F.claude\u002Fdecisions\u002Fapproved\u002F` only — hard rule |\n\n---\n\n## References\n- `templates\u002Fmeeting-agenda.md` — agenda format\n- `templates\u002Fmeeting-minutes.md` — final output format\n- `references\u002Fmeeting-facilitation.md` — conflict handling, timing, failure modes\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"domain":26,"updated":27,"version":28,"category":29,"frameworks":30},"Alireza Rezvani","board-protocol",1772668800000,"1.0.0","c-level","6-phase-board, two-layer-memory, independent-contributions","main","d6d5c82ab65b4a4ffdee7e280959f3fb8451ad4a","skills\u002Fboard-meeting","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 board-meeting",{"tool":43,"command":44},"bunx","bunx skills add sat-yam09\u002Fomni-skill --skill board-meeting",{"tool":46,"command":47},"pnpm","pnpm dlx skills add sat-yam09\u002Fomni-skill --skill board-meeting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fboard-meeting\u002FSKILL.md",true,[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fmeeting-facilitation.md","REFERENCE","参考文档",8210,"https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fboard-meeting\u002Freferences\u002Fmeeting-facilitation.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"templates\u002Fmeeting-agenda.md",1985,"https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fboard-meeting\u002Ftemplates\u002Fmeeting-agenda.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"templates\u002Fmeeting-minutes.md",2522,"https:\u002F\u002Fgithub.com\u002Fsat-yam09\u002Fomni-skill\u002Fblob\u002Fmain\u002Fskills\u002Fboard-meeting\u002Ftemplates\u002Fmeeting-minutes.md",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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",[],[]]