Token导航 LogoToken导航

Agent Skill · 效率

vendor-onboarding-workflow(供应商入职工作流程)

vendor-onboarding-workflow 用于整理文档、README、Markdown 和说明材料,适合在 OpenClaw 中需要把零散信息整理成结构清晰的文档时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

vendor-onboarding-workflow 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 7,377。

总安装 8,185周安装 348GitHub Stars 公开资料未说明下载 2,868核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:vendor-onboarding-workflow(供应商入职工作流程)
来源仓库:https://github.com/flynndavid/vendor-onboarding-workflow
安装命令:
openclaw skills install vendor-onboarding-workflow
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install vendor-onboarding-workflow

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

通过 5 个关口工作流程简化供应商入职流程,以高效收集信息、验证文档、获得批准、配置系统和激活供应商。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install vendor-onboarding-workflow;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

vendor-onboarding-workflow 怎么安装?

在终端执行 openclaw skills install vendor-onboarding-workflow。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

vendor-onboarding-workflow 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

vendor-onboarding-workflow 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

vendor-onboarding-workflow 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

vendor-onboarding-workflow 用的人多吗?

公开数据是累计安装 8,185 次,近一周安装 348 次,下载 2,868 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

vendor-onboarding-workflow 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
github

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
vendor-onboarding-workflow

供应商入职工作流程 · 本页

8,185—只读MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Vendor Onboarding Workflow — VendorGate System

Framework: VendorGate System Price: FREE Category: Productivity / Vendor Management Tags: vendor management, onboarding, procurement, ops, compliance last_validated: 2026-03-03


What This Is

The VendorGate System is a complete vendor onboarding operating system for mid-market ops teams. It replaces ad-hoc email chains and scattered spreadsheets with a structured, repeatable intake-to-activation workflow that any team can execute from day one.

Problem it solves: Most organizations lose 3-5 hours per new vendor onboarding to back-and-forth emails, missing documents, and unclear approval ownership. VendorGate closes the gate until all requirements are met — then opens it on command.

Output: A fully onboarded vendor with all documents collected, all approvals signed off, and a welcome communication sent — with a complete audit trail.


The VendorGate Framework

VendorGate operates across 5 sequential gates. A vendor cannot advance to the next gate until the current gate is cleared. Each gate has a defined owner, checklist, and exit condition.

GATE 1: Intake & Qualification
        ↓ (Pass/Fail)
GATE 2: Document Collection
        ↓ (Complete/Incomplete)
GATE 3: Internal Approval Routing
        ↓ (Approved/Rejected/Conditional)
GATE 4: System Setup & Access
        ↓ (Configured/Pending)
GATE 5: Welcome & Activation
        ↓
    VENDOR ACTIVE ✓

GATE 1: Intake & Qualification

Owner: Procurement / Ops Timeline: Day 1 Exit Condition: Vendor passes basic qualification criteria

1.1 — Vendor Intake Form Fields

Collect the following at intake (use a form tool: Typeform, JotForm, Google Form, or intake email template):

Company Information

  • Legal entity name
  • DBA name (if applicable)
  • State of incorporation / country of origin
  • Business address (physical + mailing)
  • EIN / Tax ID number
  • Website URL
  • Year founded
  • Number of employees (range: 1-10 / 11-50 / 51-200 / 200+)

Primary Contact

  • Name, title, email, phone
  • Accounts payable contact (if different)
  • Emergency / escalation contact

Services / Products

  • Category of service or product (dropdown: Technology / Professional Services / Facilities / Marketing / Logistics / Other)
  • Description of what they'll be providing
  • Estimated annual spend (range)
  • Contract start date (anticipated)

Certifications & Compliance (initial self-report)

  • Is your business licensed to operate in [our state]? (Y/N)
  • Do you carry general liability insurance? (Y/N) If yes, coverage amount?
  • Do you carry workers' compensation? (Y/N)
  • Are you minority/women/veteran-owned? (Y/N — for reporting purposes)
  • Do you have any active litigation against your business? (Y/N)

1.2 — Qualification Decision Matrix

Score the intake responses using the following logic:

FactorDisqualifying Condition
EIN / Tax IDMissing or invalid → cannot proceed
Business license"No" for regulated service categories → hold
Active litigation"Yes" → flag for legal review before advancing
Insurance self-report"No" for GL → flag for Gate 2 follow-up
Estimated spend > $50KRequires executive approval added to Gate 3

Gate 1 Exit: All non-flagged fields complete + disqualifying conditions resolved (or escalated). Log decision in vendor tracker with timestamp.


GATE 2: Document Collection

Owner: Ops / Vendor (vendor submits, ops verifies) Timeline: Days 2-5 Exit Condition: All required documents received, not expired, legible

2.1 — Document Checklist by Vendor Category

All Vendors (Universal)

  • [ ] W-9 (US vendors) or W-8BEN (international)
  • [ ] Certificate of Insurance (COI) — see COI skill for full requirements
  • [ ] Signed NDA / Confidentiality Agreement (use your standard template)
  • [ ] Business license or equivalent registration

Technology / SaaS Vendors (additional)

  • [ ] SOC 2 Type II report (or equivalent security certification)
  • [ ] Data Processing Agreement (DPA) — required if handling any personal data
  • [ ] Subprocessor list (if applicable)
  • [ ] Penetration test summary (if accessing internal systems)

Professional Services (additional)

  • [ ] E&O / Professional Liability proof of coverage
  • [ ] Proof of relevant professional licenses / certifications
  • [ ] References (minimum 2 client contacts)

Facilities / Contractors (additional)

  • [ ] Contractor's license (state-specific)
  • [ ] Workers' Compensation certificate
  • [ ] Equipment / tool insurance (if applicable)
  • [ ] OSHA compliance certification (if applicable)

Logistics / Shipping (additional)

  • [ ] Cargo insurance certificate
  • [ ] DOT number (if motor carrier)
  • [ ] Operating authority / MC number

2.2 — Document Review Standards

For each document received:

  1. Verify authenticity — Is it on letterhead? Signed? From a recognized insurer/authority?
  2. Check expiration — No document should expire within 60 days of receipt. If expiring soon, request renewal before completing Gate 2.
  3. Confirm coverage/scope — Does it cover the work being contracted? (e.g., tech vendor COI must list "technology services")
  4. Log receipt — Date received, document type, expiration date, reviewer initials

2.3 — Missing Document Follow-Up Protocol

Day 0: Send initial document request (use Template A below) Day 3: If incomplete — send reminder (use Template B below) Day 7: If still incomplete — escalate to vendor's senior contact Day 10: If no response — pause onboarding, notify internal requestor

Template A — Initial Document Request
Subject: [Your Company] Vendor Onboarding — Documents Required

Hi [Contact Name],

Thank you for your interest in partnering with [Your Company]. To complete your onboarding, we need the following documents by [DATE — 5 business days]:

[List required documents from checklist above]

Please send to: [ops email or portal link]

Questions? Reply to this email or call [contact].

Best,
[Your Name]
[Your Company] Operations
Template B — Follow-Up Reminder
Subject: Action Required: Outstanding Documents for [Vendor Name] Onboarding

Hi [Contact Name],

We're still waiting on the following documents to complete your onboarding:

[List missing items with checkboxes]

We need these by [DATE] to keep your start date on track. If there's a delay, please let us know so we can plan accordingly.

[Your Name]

GATE 3: Internal Approval Routing

Owner: Ops (routing) + Department Heads (approvals) Timeline: Days 5-8 Exit Condition: All required approvals received

3.1 — Approval Routing Matrix

Spend TierRequired Approvers
Under $10K/yearDepartment head only
$10K-$50K/yearDepartment head + Finance
$50K-$100K/yearDepartment head + Finance + COO/VP Ops
Over $100K/yearAll above + CEO/Executive team
Any vendor with data accessAll above + IT/Security sign-off
Any vendor with legal exposureAll above + Legal/Counsel review

3.2 — Approval Package (what each approver receives)

Send each approver a package containing:

  1. Vendor Summary Sheet (1 page): vendor name, service category, estimated spend, contract term, key contacts
  2. Gate 1 Intake Summary: qualification responses
  3. Gate 2 Document Status: confirmation all docs received + any flags
  4. Risk Flags (if any): litigation, expiring coverage, missing certs
  5. Requestor's Business Case: why we need this vendor (brief — 3-5 sentences)
  6. Approval Action Requested: Approve / Reject / Approve with Conditions

3.3 — Approval Conditions

If an approver approves with conditions:

  • Document the condition in the vendor record
  • Set a calendar reminder to verify the condition is met within 30 days
  • Do NOT pause onboarding for minor conditions — note and track

If rejected:

  • Document reason
  • Notify internal requestor with reason
  • Pause onboarding
  • If vendor resubmits with corrections, restart at Gate 2

3.4 — Approval Turnaround SLA

Approvers have 3 business days to respond. If no response:

  • Day 4: Ops sends a nudge ("Quick approval needed for [Vendor]")
  • Day 6: Ops escalates to approver's supervisor
  • Day 8: Decision defaults to "hold" — document and notify requestor

GATE 4: System Setup & Access

Owner: IT / Ops Timeline: Days 8-10 Exit Condition: Vendor configured in all required systems

4.1 — System Setup Checklist

Finance / Accounting

  • [ ] Vendor added to accounting system (QuickBooks, NetSuite, etc.)
  • [ ] Payment terms set (Net 30, Net 60, etc.)
  • [ ] ACH banking info collected (via secure form — never email)
  • [ ] W-9 / tax document filed in accounting system
  • [ ] Vendor contact assigned to PO workflow

Procurement / Contracts

  • [ ] Signed contract uploaded to contract management system (or shared drive folder)
  • [ ] Contract start date, end date, renewal date logged
  • [ ] Reminder set for 90 days before contract end
  • [ ] Contract assigned an internal owner

Operations / Project Management

  • [ ] Vendor added to relevant project boards (if applicable)
  • [ ] Scope of work documented and linked to vendor record
  • [ ] Performance review schedule set (quarterly or annually per contract value)

IT / Security (if vendor has system access)

  • [ ] Access permissions defined per least-privilege principle
  • [ ] SSO / 2FA configured if accessing internal tools
  • [ ] Vendor's security questionnaire responses filed
  • [ ] Access provisioned with expiration date tied to contract end

Compliance Record

  • [ ] COI expiration date entered in compliance tracker
  • [ ] Business license expiration entered
  • [ ] Next compliance review date set

GATE 5: Welcome & Activation

Owner: Ops / Department Head Timeline: Day 10-12 Exit Condition: Vendor confirmed active and relationship initiated

5.1 — Welcome Communication

Send a welcome email to the vendor's primary contact upon activation:

Template C — Vendor Welcome Email
Subject: Welcome to the [Your Company] Vendor Network

Hi [Contact Name],

Congratulations — you've completed our vendor onboarding process and are now an approved vendor for [Your Company]. We're looking forward to working with you.

Here's what to expect:

**Your key contacts at [Your Company]:**
- Day-to-day: [Name], [Title] — [email]
- Invoicing / Payments: [Name], [Title] — [email]
- Escalations: [Name], [Title] — [email]

**How to submit invoices:**
[Payment process — email to AP, portal link, etc.]

**Payment terms:** Net [X] days from invoice approval

**Your contract start date:** [DATE]

**Quarterly check-ins:** We conduct brief performance reviews with our key vendors each quarter. You'll hear from [Name] to schedule your first one.

If you have questions, reply to this email or contact [Name] directly.

Welcome aboard.

[Your Name]
[Title]
[Your Company]

5.2 — Internal Activation Notice

Notify the internal requestor and relevant team members:

Subject: ✅ [Vendor Name] — Onboarding Complete

[Vendor Name] has completed our vendor onboarding process and is now active in our system.

Key details:
- Service: [What they're providing]
- Contract start: [DATE]
- Contract end: [DATE]
- Internal owner: [Name]
- Payment terms: Net [X]
- Next compliance review: [DATE]

All documents are on file. Questions → [ops contact].

Vendor Tracker Setup

Required Fields in Your Vendor Master List

Create a tracker (spreadsheet or your vendor management tool) with these columns:

FieldTypeNotes
Vendor IDAuto-generatede.g., VEN-001
Vendor NameTextLegal entity name
DBATextIf applicable
CategoryDropdownTechnology / Services / Facilities / etc.
StatusDropdownIntake / Gate 2 / Gate 3 / Gate 4 / Active / Inactive / Terminated
Internal OwnerTextWho manages this relationship
Contract StartDate
Contract EndDate
Renewal Alert DateDate90 days before end
Estimated Annual SpendCurrency
W-9 on fileY/N
COI on fileY/N
COI ExpirationDateAlert 60 days before
Business License ExpirationDateAlert 60 days before
Last Performance ReviewDate
Next Performance ReviewDate
Risk TierDropdownGreen / Yellow / Red
NotesText

Tracker Automation (if using spreadsheet)

Set up conditional formatting:

  • Red highlight: COI Expiration or License Expiration within 30 days
  • Yellow highlight: Expiration within 60 days
  • Orange highlight: Status = Gate 2 or Gate 3 for more than 7 days (stalled onboarding)

VendorGate Implementation Checklist (First 30 Days)

Use this to stand up VendorGate in your organization:

Week 1: Foundation

  • [ ] Customize intake form with your company fields
  • [ ] Identify your approval routing matrix (fill in the spend tiers)
  • [ ] Create vendor tracker (copy the field list above into your tool)
  • [ ] Set up document collection folder structure (shared drive or vendor portal)
  • [ ] Customize all email templates with your branding

Week 2: Process

  • [ ] Run a test onboarding with one current vendor to validate the flow
  • [ ] Identify gaps and update checklists
  • [ ] Brief your team on the 5-gate process and their responsibilities
  • [ ] Define who owns each gate

Week 3: Automation

  • [ ] Set up expiration alerts (calendar reminders or spreadsheet alerts)
  • [ ] Connect to your accounting system if possible
  • [ ] Create a shared "Vendor Onboarding" email alias for document submission

Week 4: Launch

  • [ ] Begin using VendorGate for all new vendors
  • [ ] Review your backlog of existing vendors — identify any compliance gaps
  • [ ] Schedule first quarterly vendor review for your top 5 vendors

Expected Outputs

After running a vendor through VendorGate, you should have:

  1. ✅ Complete vendor intake record (all fields populated)
  2. ✅ All required documents collected, verified, and filed
  3. ✅ All required approvals documented with timestamps
  4. ✅ Vendor configured in accounting, contracts, and relevant systems
  5. ✅ Welcome communication sent and confirmed received
  6. ✅ Compliance calendar reminders set for document renewals
  7. ✅ Vendor tracker updated with active status and all key dates

Time to onboard (target): 10-12 business days for a standard vendor Time to onboard (expedited): 5-7 business days with dedicated ops focus


*VendorGate System — Part of the Vendor & Compliance Operations Pack by Remy Claw* *More at remyclaw.com | @Remy_Claw on X*

平台分布

OpenClaw

75.56%
按下载量换算2,167

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills