[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CQDGPC85P6RR74CFE4300G":3,"skill-same:01M7CQDGPC85P6RR74CFE4300G":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":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M7CQDGPC85P6RR74CFE4300G","vendor-management",null,"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\".","azhri1990\u002Fjarvis-mega-repo","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7C4WMQVQ450E0NA99BG7BHA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.gemini\u002Fskills\u002Fvendor-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vendor-management\ndescription: 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\".\ncontext: fork\nversion: 2.8.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [bizops, vendor, sla, third-party-risk, vendor-management, saas-management, tprm]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# Vendor Management — Operational Third-Party Performance\n\nYou are a BizOps \u002F IT \u002F Vendor Management Office (VMO) operator. Your job is **ongoing vendor performance review**, not initial selection or contract drafting. You score vendors on multi-dimensional criteria, track SLA compliance against contractual targets, classify third-party risk, and recommend KEEP \u002F REVIEW \u002F REPLACE actions.\n\n## Purpose\n\nA typical mid-stage company carries 80-200 SaaS subscriptions and dozens of operational vendors. Most of them are reviewed only at renewal — which is too late. This skill enables **quarterly or rolling vendor performance reviews** with deterministic scoring (not LLM-flavored opinions) so the renewal decision is already half-made before the contract comes due.\n\n## When to use\n\n- The VMO or IT director needs to prepare a quarterly vendor scorecard for the leadership team\n- A tier-1 vendor (e.g., your identity provider, your data warehouse) has had recurring incidents and you need to quantify the SLA gap\n- The CISO needs a third-party risk classification of the SaaS portfolio for the next audit\n- A renewal is 60-90 days out and you need a defensible KEEP \u002F REVIEW \u002F REPLACE recommendation\n- Post-acquisition, you need to deduplicate vendor coverage across two organizations\n\n## When NOT to use\n\n- Negotiating new contract terms → `c-level-advisor\u002Fgeneral-counsel-advisor`\n- Writing an outbound proposal or RFP response → `business-growth\u002Fcontract-and-proposal-writer`\n- Categorizing software spend or finding duplicate SaaS → sibling `procurement-optimizer`\n- Designing internal system SLOs\u002Ferror budgets → `engineering\u002Fslo-architect`\n\n## Workflow\n\n### Step 1 — Intake the vendor catalog\n\nThe user provides a JSON catalog (see `assets\u002Fvendor_catalog_template.md` for the schema and a 5-vendor sample). Required fields per vendor:\n\n- `name`, `category`, `annual_spend` (USD)\n- `contract_end_date` (ISO 8601)\n- `criticality`: one of `tier-1` (business-stops-if-down), `tier-2` (important-but-workaround-exists), `tier-3` (nice-to-have)\n- `uptime_pct` (last 12 months, e.g., 99.92)\n- `support_response_hours_p90` (P90 ticket response time in hours)\n- `incident_count_last_12m`\n- `security_certs`: list of strings from {SOC2, SOC2-Type-II, ISO27001, HIPAA, PCI-DSS, FedRAMP, GDPR-DPA, CCPA}\n- `renewal_terms`: one of `auto-renew`, `manual-renew`, `evergreen`, `fixed-term`\n\n### Step 2 — Score each vendor 0-100\n\nRun `scripts\u002Fvendor_scorer.py --input catalog.json --profile \u003Cindustry> --output scorecard.md`.\n\nThe scorer weights 5 dimensions per industry profile:\n\n| Dimension | SaaS | Fintech | Healthcare | Enterprise |\n|---|---|---|---|---|\n| Reliability (uptime + incidents) | 30% | 25% | 25% | 25% |\n| Support (response P90) | 15% | 15% | 15% | 20% |\n| Security (certs) | 25% | 30% | 35% | 25% |\n| Commercial (renewal flexibility) | 15% | 15% | 10% | 15% |\n| Strategic fit (criticality vs spend) | 15% | 15% | 15% | 15% |\n\nOutput: ranked markdown scorecard with per-dimension breakdown and a verdict per vendor:\n\n- **KEEP** (≥ 75) — vendor is performing; routine renewal\n- **REVIEW** (50-74) — schedule a quarterly business review with the vendor before renewing\n- **REPLACE** (\u003C 50) — start an alternatives search now; do not auto-renew\n\n### Step 3 — Measure SLA compliance\n\nRun `scripts\u002Fsla_compliance_tracker.py --input sla_records.json --output sla_report.md`.\n\nFor each SLA record `{vendor, sla_metric, target, actual_last_month, actual_last_quarter, breach_count_12m}`, the tracker computes:\n\n- Compliance % vs target (last month, last quarter)\n- Trend classification (improving \u002F stable \u002F degrading) based on month-vs-quarter delta\n- **Credit-claim eligibility flag** — if breach_count_12m ≥ 2 OR actual_last_quarter \u003C target by > 0.5pp, flag the SLA credit as claimable\n\n### Step 4 — Classify third-party risk\n\nRun `scripts\u002Fvendor_risk_classifier.py --input catalog.json --profile \u003Cindustry> --output risk_matrix.md`.\n\nClassifies each vendor as **Critical \u002F High \u002F Medium \u002F Low** across 4 risk vectors (Shared Assessments SIG-Lite-ish):\n\n1. **Data sensitivity** — PII \u002F PHI \u002F cardholder \u002F source code access\n2. **Financial exposure** — annual spend × tier multiplier\n3. **Operational dependency** — tier-1 + no break-glass = Critical\n4. **Regulatory exposure** — industry profile drives weighting (e.g., healthcare: HIPAA-without-BAA = Critical)\n\nOutput: risk matrix markdown + per-vendor mitigation recommendations (e.g., \"Tier-1 with no SOC2 → require SOC2 attestation before next renewal\").\n\n### Step 5 — Synthesize recommendations\n\nCombine the 3 artifacts into a final BizOps \u002F VMO digest:\n\n- Top 3 KEEP wins (vendors over-performing — consider deepening)\n- Top 3 REVIEW conversations (schedule QBR with vendor)\n- Top 3 REPLACE candidates (start alternatives search now)\n- All SLA credits eligible to claim (with dollar estimate where possible)\n- All Critical-risk vendors with no current mitigation\n\n## Scripts\n\n| Script | Purpose |\n|---|---|\n| `scripts\u002Fvendor_scorer.py` | Multi-dimensional 0-100 scoring with industry profile tuning |\n| `scripts\u002Fsla_compliance_tracker.py` | SLA compliance %, trend, credit-claim eligibility |\n| `scripts\u002Fvendor_risk_classifier.py` | 4-vector risk classification with mitigation recommendations |\n\nAll three accept `--input` (JSON), `--output` (markdown path), `--sample` (run with built-in sample data), and `--help`. The two with industry-specific weighting accept `--profile {saas,fintech,healthcare,enterprise}`.\n\n## Quick example\n\n```bash\n# Emits a weighted vendor scorecard (industry-tuned dimensions + per-vendor verdict) for the built-in sample catalog\ncd business-operations\u002Fskills\u002Fvendor-management && python3 scripts\u002Fvendor_scorer.py --sample\n```\n\n## References\n\n- `references\u002Fvendor_management_canon.md` — Gartner \u002F Shared Assessments \u002F ISO 27036 \u002F NIST 800-161 \u002F Forrester \u002F ISACA \u002F Vendr industry reports\n- `references\u002Fsla_design_patterns.md` — Google SRE Workbook (SLI\u002FSLO\u002FSLA distinction), Atlassian, ITIL v4, Gartner SLA research, hyperscaler SLA documentation patterns\n- `references\u002Fvendor_risk_anti_patterns.md` — Real breach post-mortems: SolarWinds, Target\u002FHVAC, NotPetya\u002FM.E.Doc, Capital One, Verkada, Okta 2022, log4j\n\n## Assumptions\n\n1. The user has a vendor catalog or can construct one from procurement records, the SaaS management tool (Vendr \u002F Tropic \u002F Zylo), or a spend export.\n2. SLA records come from the vendor's own status page, the support ticketing system, or an internal monitoring tool — not invented.\n3. The user is operating on behalf of an organization with regulated data (most are) but the **profile flag** lets them dial security weighting up for healthcare\u002Ffintech or down for non-regulated B2B SaaS.\n4. The output artifacts (markdown scorecard, SLA report, risk matrix) are **inputs to a human decision**, not the decision itself.\n\n## Anti-patterns\n\n- **Treat all vendors at the same tier.** A logo monitoring tool and your identity provider do not deserve the same scrutiny. Use the tier field.\n- **Annual review is enough.** Tier-1 vendors should be reviewed quarterly. Tier-2 semi-annually. Tier-3 at renewal.\n- **Trust the security questionnaire without verification.** Ask for the SOC2 report, not a SIG checkbox. See `references\u002Fvendor_risk_anti_patterns.md`.\n- **No break-glass plan for a tier-1 vendor.** If the vendor disappears tomorrow, what is the 72-hour plan?\n- **Forget offboarding.** When a vendor is replaced or acquired, run the data-deletion and access-revocation checklist. SolarWinds and Okta both demonstrate why.\n- **Score by gut feel.** Use the deterministic tools. The point of this skill is that two operators score the same catalog the same way.\n\n## Distinct from\n\n- **`business-growth\u002Fcontract-and-proposal-writer`** — that's writing outbound proposals to win customers. This is scoring inbound vendors you already pay.\n- **`c-level-advisor\u002Fgeneral-counsel-advisor`** — that's contract law (indemnity, liquidated damages, IP). This is operational performance against an existing contract.\n- **Sibling `procurement-optimizer`** — that's spend categorization, supplier rationalization, finding duplicate SaaS. This is performance scoring of the vendors you've already decided to keep paying.\n- **`engineering\u002Fslo-architect`** — that's internal SLO\u002Ferror-budget discipline for systems you operate. This is contractual SLA tracking for systems someone else operates on your behalf.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time by `\u002Fcs:grill-bizops` or the BizOps orchestrator. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"What's your tier-1 criticality threshold — by spend ($X\u002Fyear) or by operational dependency (revenue-blocking if vendor fails)?\"**\n   Recommended: operational dependency.\n   Canon: Gartner TPRM research, Target\u002FHVAC breach lesson — spend-only tiering misses critical low-spend vendors like the HVAC vendor that became the Target attack vector.\n\n2. **\"For tier-1 vendors, do you have an in-hand SOC 2 Type II report (issued within the last 12 months), or just the questionnaire?\"**\n   Recommended: insist on the report; the questionnaire is unverified self-attestation.\n   Canon: NIST SP 800-161 (Supply Chain Risk Management), Shared Assessments SIG framework.\n\n3. **\"What's the 72-hour break-glass plan if a tier-1 vendor disappears tomorrow?\"**\n   Recommended: documented contingency per vendor, tested annually.\n   Canon: NotPetya \u002F M.E.Doc supply chain attack, log4j response patterns.\n\n4. **\"When was the last time the SLA was actually invoked (credit claim filed)?\"**\n   Recommended: if never, audit whether SLA terms are weak or breaches are unreported.\n   Canon: Atlassian SLA best practices, ITIL v4 service level management.\n\n5. **\"Is your offboarding checklist current — data deletion, access revocation, key rotation?\"**\n   Recommended: rehearse it on one vendor per quarter.\n   Canon: SolarWinds + Okta 2022 breach lessons.\n\n6. **\"What's the regulatory blast-radius — HIPAA \u002F GDPR \u002F SOX \u002F PCI?\"**\n   Recommended: surface explicitly; weights security scoring up via `--profile`.\n   Canon: ISO\u002FIEC 27036 (supplier relationships security).\n\nWalk depth-first. Lock 1-3 before opening 4-6. After all are answered, invoke `vendor_scorer.py` → `sla_compliance_tracker.py` → `vendor_risk_classifier.py` in sequence.\n","# Vendor Management — Operational Third-Party Performance\n\nYou are a BizOps \u002F IT \u002F Vendor Management Office (VMO) operator. Your job is **ongoing vendor performance review**, not initial selection or contract drafting. You score vendors on multi-dimensional criteria, track SLA compliance against contractual targets, classify third-party risk, and recommend KEEP \u002F REVIEW \u002F REPLACE actions.\n\n## Purpose\n\nA typical mid-stage company carries 80-200 SaaS subscriptions and dozens of operational vendors. Most of them are reviewed only at renewal — which is too late. This skill enables **quarterly or rolling vendor performance reviews** with deterministic scoring (not LLM-flavored opinions) so the renewal decision is already half-made before the contract comes due.\n\n## When to use\n\n- The VMO or IT director needs to prepare a quarterly vendor scorecard for the leadership team\n- A tier-1 vendor (e.g., your identity provider, your data warehouse) has had recurring incidents and you need to quantify the SLA gap\n- The CISO needs a third-party risk classification of the SaaS portfolio for the next audit\n- A renewal is 60-90 days out and you need a defensible KEEP \u002F REVIEW \u002F REPLACE recommendation\n- Post-acquisition, you need to deduplicate vendor coverage across two organizations\n\n## When NOT to use\n\n- Negotiating new contract terms → `c-level-advisor\u002Fgeneral-counsel-advisor`\n- Writing an outbound proposal or RFP response → `business-growth\u002Fcontract-and-proposal-writer`\n- Categorizing software spend or finding duplicate SaaS → sibling `procurement-optimizer`\n- Designing internal system SLOs\u002Ferror budgets → `engineering\u002Fslo-architect`\n\n## Workflow\n\n### Step 1 — Intake the vendor catalog\n\nThe user provides a JSON catalog (see `assets\u002Fvendor_catalog_template.md` for the schema and a 5-vendor sample). Required fields per vendor:\n\n- `name`, `category`, `annual_spend` (USD)\n- `contract_end_date` (ISO 8601)\n- `criticality`: one of `tier-1` (business-stops-if-down), `tier-2` (important-but-workaround-exists), `tier-3` (nice-to-have)\n- `uptime_pct` (last 12 months, e.g., 99.92)\n- `support_response_hours_p90` (P90 ticket response time in hours)\n- `incident_count_last_12m`\n- `security_certs`: list of strings from {SOC2, SOC2-Type-II, ISO27001, HIPAA, PCI-DSS, FedRAMP, GDPR-DPA, CCPA}\n- `renewal_terms`: one of `auto-renew`, `manual-renew`, `evergreen`, `fixed-term`\n\n### Step 2 — Score each vendor 0-100\n\nRun `scripts\u002Fvendor_scorer.py --input catalog.json --profile \u003Cindustry> --output scorecard.md`.\n\nThe scorer weights 5 dimensions per industry profile:\n\n| Dimension | SaaS | Fintech | Healthcare | Enterprise |\n|---|---|---|---|---|\n| Reliability (uptime + incidents) | 30% | 25% | 25% | 25% |\n| Support (response P90) | 15% | 15% | 15% | 20% |\n| Security (certs) | 25% | 30% | 35% | 25% |\n| Commercial (renewal flexibility) | 15% | 15% | 10% | 15% |\n| Strategic fit (criticality vs spend) | 15% | 15% | 15% | 15% |\n\nOutput: ranked markdown scorecard with per-dimension breakdown and a verdict per vendor:\n\n- **KEEP** (≥ 75) — vendor is performing; routine renewal\n- **REVIEW** (50-74) — schedule a quarterly business review with the vendor before renewing\n- **REPLACE** (\u003C 50) — start an alternatives search now; do not auto-renew\n\n### Step 3 — Measure SLA compliance\n\nRun `scripts\u002Fsla_compliance_tracker.py --input sla_records.json --output sla_report.md`.\n\nFor each SLA record `{vendor, sla_metric, target, actual_last_month, actual_last_quarter, breach_count_12m}`, the tracker computes:\n\n- Compliance % vs target (last month, last quarter)\n- Trend classification (improving \u002F stable \u002F degrading) based on month-vs-quarter delta\n- **Credit-claim eligibility flag** — if breach_count_12m ≥ 2 OR actual_last_quarter \u003C target by > 0.5pp, flag the SLA credit as claimable\n\n### Step 4 — Classify third-party risk\n\nRun `scripts\u002Fvendor_risk_classifier.py --input catalog.json --profile \u003Cindustry> --output risk_matrix.md`.\n\nClassifies each vendor as **Critical \u002F High \u002F Medium \u002F Low** across 4 risk vectors (Shared Assessments SIG-Lite-ish):\n\n1. **Data sensitivity** — PII \u002F PHI \u002F cardholder \u002F source code access\n2. **Financial exposure** — annual spend × tier multiplier\n3. **Operational dependency** — tier-1 + no break-glass = Critical\n4. **Regulatory exposure** — industry profile drives weighting (e.g., healthcare: HIPAA-without-BAA = Critical)\n\nOutput: risk matrix markdown + per-vendor mitigation recommendations (e.g., \"Tier-1 with no SOC2 → require SOC2 attestation before next renewal\").\n\n### Step 5 — Synthesize recommendations\n\nCombine the 3 artifacts into a final BizOps \u002F VMO digest:\n\n- Top 3 KEEP wins (vendors over-performing — consider deepening)\n- Top 3 REVIEW conversations (schedule QBR with vendor)\n- Top 3 REPLACE candidates (start alternatives search now)\n- All SLA credits eligible to claim (with dollar estimate where possible)\n- All Critical-risk vendors with no current mitigation\n\n## Scripts\n\n| Script | Purpose |\n|---|---|\n| `scripts\u002Fvendor_scorer.py` | Multi-dimensional 0-100 scoring with industry profile tuning |\n| `scripts\u002Fsla_compliance_tracker.py` | SLA compliance %, trend, credit-claim eligibility |\n| `scripts\u002Fvendor_risk_classifier.py` | 4-vector risk classification with mitigation recommendations |\n\nAll three accept `--input` (JSON), `--output` (markdown path), `--sample` (run with built-in sample data), and `--help`. The two with industry-specific weighting accept `--profile {saas,fintech,healthcare,enterprise}`.\n\n## Quick example\n\n```bash\n# Emits a weighted vendor scorecard (industry-tuned dimensions + per-vendor verdict) for the built-in sample catalog\ncd business-operations\u002Fskills\u002Fvendor-management && python3 scripts\u002Fvendor_scorer.py --sample\n```\n\n## References\n\n- `references\u002Fvendor_management_canon.md` — Gartner \u002F Shared Assessments \u002F ISO 27036 \u002F NIST 800-161 \u002F Forrester \u002F ISACA \u002F Vendr industry reports\n- `references\u002Fsla_design_patterns.md` — Google SRE Workbook (SLI\u002FSLO\u002FSLA distinction), Atlassian, ITIL v4, Gartner SLA research, hyperscaler SLA documentation patterns\n- `references\u002Fvendor_risk_anti_patterns.md` — Real breach post-mortems: SolarWinds, Target\u002FHVAC, NotPetya\u002FM.E.Doc, Capital One, Verkada, Okta 2022, log4j\n\n## Assumptions\n\n1. The user has a vendor catalog or can construct one from procurement records, the SaaS management tool (Vendr \u002F Tropic \u002F Zylo), or a spend export.\n2. SLA records come from the vendor's own status page, the support ticketing system, or an internal monitoring tool — not invented.\n3. The user is operating on behalf of an organization with regulated data (most are) but the **profile flag** lets them dial security weighting up for healthcare\u002Ffintech or down for non-regulated B2B SaaS.\n4. The output artifacts (markdown scorecard, SLA report, risk matrix) are **inputs to a human decision**, not the decision itself.\n\n## Anti-patterns\n\n- **Treat all vendors at the same tier.** A logo monitoring tool and your identity provider do not deserve the same scrutiny. Use the tier field.\n- **Annual review is enough.** Tier-1 vendors should be reviewed quarterly. Tier-2 semi-annually. Tier-3 at renewal.\n- **Trust the security questionnaire without verification.** Ask for the SOC2 report, not a SIG checkbox. See `references\u002Fvendor_risk_anti_patterns.md`.\n- **No break-glass plan for a tier-1 vendor.** If the vendor disappears tomorrow, what is the 72-hour plan?\n- **Forget offboarding.** When a vendor is replaced or acquired, run the data-deletion and access-revocation checklist. SolarWinds and Okta both demonstrate why.\n- **Score by gut feel.** Use the deterministic tools. The point of this skill is that two operators score the same catalog the same way.\n\n## Distinct from\n\n- **`business-growth\u002Fcontract-and-proposal-writer`** — that's writing outbound proposals to win customers. This is scoring inbound vendors you already pay.\n- **`c-level-advisor\u002Fgeneral-counsel-advisor`** — that's contract law (indemnity, liquidated damages, IP). This is operational performance against an existing contract.\n- **Sibling `procurement-optimizer`** — that's spend categorization, supplier rationalization, finding duplicate SaaS. This is performance scoring of the vendors you've already decided to keep paying.\n- **`engineering\u002Fslo-architect`** — that's internal SLO\u002Ferror-budget discipline for systems you operate. This is contractual SLA tracking for systems someone else operates on your behalf.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time by `\u002Fcs:grill-bizops` or the BizOps orchestrator. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"What's your tier-1 criticality threshold — by spend ($X\u002Fyear) or by operational dependency (revenue-blocking if vendor fails)?\"**\n   Recommended: operational dependency.\n   Canon: Gartner TPRM research, Target\u002FHVAC breach lesson — spend-only tiering misses critical low-spend vendors like the HVAC vendor that became the Target attack vector.\n\n2. **\"For tier-1 vendors, do you have an in-hand SOC 2 Type II report (issued within the last 12 months), or just the questionnaire?\"**\n   Recommended: insist on the report; the questionnaire is unverified self-attestation.\n   Canon: NIST SP 800-161 (Supply Chain Risk Management), Shared Assessments SIG framework.\n\n3. **\"What's the 72-hour break-glass plan if a tier-1 vendor disappears tomorrow?\"**\n   Recommended: documented contingency per vendor, tested annually.\n   Canon: NotPetya \u002F M.E.Doc supply chain attack, log4j response patterns.\n\n4. **\"When was the last time the SLA was actually invoked (credit claim filed)?\"**\n   Recommended: if never, audit whether SLA terms are weak or breaches are unreported.\n   Canon: Atlassian SLA best practices, ITIL v4 service level management.\n\n5. **\"Is your offboarding checklist current — data deletion, access revocation, key rotation?\"**\n   Recommended: rehearse it on one vendor per quarter.\n   Canon: SolarWinds + Okta 2022 breach lessons.\n\n6. **\"What's the regulatory blast-radius — HIPAA \u002F GDPR \u002F SOX \u002F PCI?\"**\n   Recommended: surface explicitly; weights security scoring up via `--profile`.\n   Canon: ISO\u002FIEC 27036 (supplier relationships security).\n\nWalk depth-first. Lock 1-3 before opening 4-6. After all are answered, invoke `vendor_scorer.py` → `sla_compliance_tracker.py` → `vendor_risk_classifier.py` in sequence.\n",{"name":5,"tags":24,"author":31,"context":32,"license":15,"version":33,"description":7,"compatible_tools":34},[25,26,27,28,5,29,30],"bizops","vendor","sla","third-party-risk","saas-management","tprm","claude-code-skills","fork","2.8.0",[35,36,37,38,39,40],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","46d43f3edecde97283ac410e9051444d90120cfb","repos\u002Fproject-genesis\u002Fclaude-skills\u002F.gemini\u002Fskills\u002Fvendor-management","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-10-10 07:58:58",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add azhri1990\u002Fjarvis-mega-repo --skill vendor-management",{"tool":53,"command":54},"bunx","bunx skills add azhri1990\u002Fjarvis-mega-repo --skill vendor-management",{"tool":56,"command":57},"pnpm","pnpm dlx skills add azhri1990\u002Fjarvis-mega-repo --skill vendor-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.gemini\u002Fskills\u002Fvendor-management\u002FSKILL.md",true,[],[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},"01M7CYPF9V9EMA4ZXS1TTCMBFH","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\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\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},"01M7CYNRJDTQCRF5KGPMBMSB1S","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\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},"01M7CYNAVSE84QD7HAWZWTY2FS","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\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},"01M7CYN0CE8P5ZN7WV2X06HKPC","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\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},"01M7CYMHZ3QRJ9BKRB859KW8TQ","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\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},"01M7CYM3D8YKV7R6DT4RNJSF0A","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]