OpenClaw/clawhub-security-signals huggingface dataset:
Skill: bytesagain3/stochastic (version 1.0.0)

--- name: "stochastic" version: "1.0.0" description: "Stochastic reference tool. Use when working with stochastic in finance contexts." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [stochastic, finance, finance, reference, cli] category: "finance" --- # Stochastic Stochastic reference tool. Use when working with stochastic in finance contexts. ## When to Use - Working with stochastic and need quick reference - Looking up finance standards or best practices for stochastic - Troubleshooting stochastic issues - Need a checklist or guide for stochastic tasks ## Commands ### `intro` ```bash scripts/script.sh intro ``` Overview and fundamentals ### `formulas` ```bash scripts/script.sh formulas ``` Key formulas and calculations ### `regulations` ```bash scripts/script.sh regulations ``` Regulatory framework and compliance ### `risks` ```bash scripts/script.sh risks ``` Risk factors and mitigation ### `instruments` ```bash scripts/script.sh instruments ``` Instruments and tools overview ### `strategies` ```bash scripts/script.sh strategies ``` Common strategies and approaches ### `glossary` ```bash scripts/script.sh glossary ``` Key terms and definitions ### `checklist` ```bash scripts/script.sh checklist ``` Due diligence checklist ### `help` ```bash scripts/script.sh help ``` ### `version` ```bash scripts/script.sh version ``` --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wjd6910502/kernel-cve-tracker (version 1.0.0)

--- name: kernel-cve-tracker description: 跟踪 Ubuntu Linux 内核 CVE 漏洞的工具技能。当用户需要以下操作时使用此技能：(1) 查询特定内核版本（如 5.10/5.15）的 CVE 列表和修复状态；(2) 分析 Ubuntu Security Notice (USN) 中的内核漏洞详情；(3) 获取漏洞发现方式（发现者/发现方法）；(4) 汇总某个内核系列的漏洞报告；(5) 对比不同 Ubuntu 版本的内核 CVE 状态矩阵。 --- # Kernel CVE Tracker 从 Ubuntu Security 官方来源抓取、汇总和跟踪 Linux 内核 CVE 漏洞。 ## 数据来源 - **CVE 搜索**：https://ubuntu.com/security/cves?package=linux-hwe-5.10 - **USN 列表**：https://ubuntu.com/security/notices - **CVE 详情**：https://ubuntu.com/security/CVE-YYYY-NNNNN - **OVAL 机器可读**：https://ubuntu.com/security/oval ## 内核版本对应关系（Ubuntu HWE） | 包名 | 对应上游版本 | 维护者 | |------|------------|-------| | `linux-hwe-5.10` | 5.10 LTS (HWE) | Ubuntu Kernel Team | | `linux-hwe-5.15` | 5.15 LTS (HWE) | Ubuntu Kernel Team | | `linux-hwe-6.8` | 6.8 LTS (HWE) | Ubuntu Kernel Team | | `linux-oem-5.10` | OEM 定制 | OEM Vendor | | `linux-aws-5.10` | AWS 定制 | Ubuntu Kernel Team | | `linux-azure-5.10` | Azure 定制 | Ubuntu Kernel Team | | `linux-gcp-5.10` | GCP 定制 | Ubuntu Kernel Team | ## 漏洞状态标记说明 | 状态 | 含义 | |------|------| | `Fixed` | 已修复（含修复版本号） | | `Vulnerable, work in progress` | 修复中 | | `Ignored` / `Ignored end of standard support` | 已忽略（生命末期） | | `Not in release` | 该版本未发布此包 | | `Not affected` | 不受影响 | ## 抓取流程 ### Step 1: 搜索 CVE 列表 ```bash web_fetch("https://ubuntu.com/security/cves?package=linux-hwe-5.15") ``` 解析状态矩阵，提取所有 `Fixed` 和 `Vulnerable` 条目。 ### Step 2: 获取 USN 详情 ```bash web_fetch("https://ubuntu.com/security/notices/USN-XXXX-N") ``` Details 区包含： - 受影响子系统列表（Subsystems） - CVE 引用列表（References） - 修复包版本号 ### Step 3: 单个 CVE 详情 ```bash web_fetch("https://ubuntu.com/security/CVE-YYYY-NNNNN") ``` 包含：各包各发行版状态矩阵、漏洞描述、发现者信息。 ### Step 4: 汇总漏洞发现方式 参考 `references/cve-list.md`，按以下分类汇总： | 发现方式 | 特征 | |--------|------| | **安全研究员主动挖掘** | USN/CVE 页面会标注发现者姓名 | | **内部代码审计/fuzzer** | 漏洞描述提及"incorrectly handled"或"did not properly validate" | | **社区/红队被动报告** | 描述简单，仅注明"discovered that..."，未署名 | | **自动化工具/CVA** | 无具体发现者信息，系统性测试发现 | ## 漏洞发现方式分类 ### 1. 安全研究员主动发现（署名） | CVE | 发现者 | 漏洞类型 | |-----|-------|---------| | CVE-2023-2640 | Stonejiajia、Shir Tamari、Sagi Tzadik | OverlayFS 权限检查不当 | | CVE-2023-32629 | Shir Tamari、Sagi Tzadik | OverlayFS 权限检查不当 | | CVE-2026-31431 | Ubuntu 安全团队（内部审计） | algif_aead Copy Fail | ### 2. 社区被动报告（未署名） | CVE | 子系统 | 描述 | |-----|-------|------| | CVE-2026-23351 | io_uring | Several security issues discovered | | CVE-2026-23274 | Netfilter | Several security issues discovered | | CVE-2024-50060 | SMB | Several security issues discovered | | CVE-2024-35862 | 未知 | Several security issues discovered | ### 3. 外部安全研究者（署名） | CVE | 发现者 | 漏洞类型 | |-----|-------|---------| | ngtcp2 栈溢出 | Zou Dikai | 固定 1024 字节栈缓冲区无边界检查 | ## 快速命令 ```bash # 查看当前内核版本 uname -r # 查看已安装内核包 dpkg -l | grep linux-image # 查看 USN 详情 # https://ubuntu.com/security/notices/USN-NNNN-N # 下载 OVAL 数据（机器可读） wget https://ubuntu.com/security/oval/com.ubuntu.focal.cve.stanza.xz ``` ## 数据更新频率 - USN 通知：每工作日更新 - 建议每周抓取一次全量 CVE 列表做对比 ## 完整漏洞数据 详细 CVE 列表、USN 引用和版本对应关系，见 `references/cve-list.md`。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: underbench2-gif/ub2-markdown-report-generator (version 1.0.0)

# Markdown Report Generator A skill that enables Claw to compile information from multiple sources into a polished, well-structured Markdown report with tables, sections, and optional PDF export. ## What This Skill Does This skill provides a complete report generation workflow: 1. **Content Collection** — Gather information from provided text, files, URLs, or prior conversation context 2. **Structure Planning** — Organize content into logical sections with a table of contents 3. **Formatting** — Apply consistent Markdown formatting with headers, lists, tables, code blocks, and emphasis 4. **Table Generation** — Convert raw data into well-formatted Markdown tables 5. **Export** — Save as `.md` file, and optionally convert to PDF or HTML ## How to Use Ask Claw to generate a report on any topic or from any data: - "Create a project status report from these meeting notes" - "Generate a comparison report of these three products with a feature table" - "Write a technical documentation report for this codebase" - "Compile a weekly summary report from these data points" ## Report Structure Generated reports follow this template: ``` # Report Title ## Table of Contents ## Executive Summary ## Section 1: [Topic] ### Subsection with details ## Section 2: [Topic] ## Data Tables ## Conclusions & Recommendations ## Appendix (if applicable) ``` ## Customization Options - **Tone** — Formal, technical, executive summary, or casual - **Length** — Brief (1-2 pages), standard (3-5 pages), or comprehensive (5+ pages) - **Sections** — Specify which sections to include or exclude - **Branding** — Add a custom header or footer text ## Output - A `.md` file saved to the specified location - Optional HTML or PDF conversion if requested - Clean, consistent formatting ready for sharing or publishing


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: marjoriebroad/skillboss-tiny (version 1.0.0)

--- name: skillboss description: "Multi-AI gateway. 50+ models: chat, image, video, TTS, music, search." allowed-tools: Bash, Read metadata: {"clawdbot":{"requires":{"bins":["node"],"env":["SKILLBOSS_API_KEY"]},"primaryEnv":"SKILLBOSS_API_KEY"}} --- # SkillBoss One API key, 50+ models across providers. Chat, image, video, TTS, STT, music, web search. ## List Models ```bash node {baseDir}/scripts/run.mjs models node {baseDir}/scripts/run.mjs models image node {baseDir}/scripts/run.mjs models chat ``` ## Run a Model ```bash node {baseDir}/scripts/run.mjs run bedrock/claude-4-5-sonnet "Explain quantum computing" node {baseDir}/scripts/run.mjs run mm/img "A sunset over mountains" node {baseDir}/scripts/run.mjs run minimax/speech-01-turbo "Hello world" ``` ## Smart Mode ```bash node {baseDir}/scripts/run.mjs tasks node {baseDir}/scripts/run.mjs task image "A sunset" node {baseDir}/scripts/run.mjs task chat "Hello" node {baseDir}/scripts/run.mjs task tts "Hello world" ``` ## Save Media Image/video/audio results print a URL. Save with curl: ```bash URL=$(node {baseDir}/scripts/run.mjs run mm/img "A sunset") curl -sL "$URL" -o sunset.png ``` Notes: - Get SKILLBOSS_API_KEY at https://www.skillboss.co - Use `models` to discover available models


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: gigshow/decker-polymarket (version 1.1.0)

--- name: decker-polymarket description: "Use when user asks about Polymarket prediction market via Decker. Triggers: Polymarket, 폴리마켓, 예측시장, PM 매수, PM 시장 검색, PM 카테고리, PM 이벤트, 시장 slug, YES/NO." user-invocable: true metadata: version: 1.1.0 extends: decker --- # Decker + Polymarket (예측시장) 스킬 ## Goal Decker를 통해 **Polymarket 예측시장**에서 시장 조회·YES/NO 주문 실행. 메인 decker 스킬을 확장. ClawHub polymarket-odds 흡수. ## Quick Reference | 사용자 말 | 액션 | 비고 | |-----------|------|------| | "PM 시장 검색 비트코인", "폴리마켓 검색 트럼프" | 시장 검색 | Gamma API search | | "PM 카테고리", "폴리마켓 태그" | 태그/카테고리 목록 | Gamma tags | | "PM 이벤트 crypto", "폴리마켓 이벤트 정치" | 이벤트 목록 | tag_slug 선택 | | "PM 시장 will-bitcoin-100k", "폴리마켓 will-x" | 시장 slug 상세 | Gamma market by slug | | "Polymarket will-x-win yes 10 매수", "PM 시장 slug yes 매수" | order-request **exchange_id=polymarket** | symbol=market_slug, outcome=yes/no | | "Polymarket 시장 가격", "PM 확률" | Assistant API 또는 시장 조회 | | | "PM 포지션" | Assistant API | JWT 필요 | ## DECKER_API_URL https://api.decker-ai.com ## 주문 (Polymarket) **order-request에 exchange_id=polymarket 추가**: ``` GET {DECKER_API_URL}/api/v1/link/slack/order-request?slack_user_id={sender_id}&symbol=will-x-win&side=buy&quantity=10&exchange_id=polymarket&outcome=yes&openclaw_secret={OPENCLAW_SECRET} ``` - **exchange_id=polymarket** 필수 - **symbol**: Polymarket 시장 slug (예: will-joe-biden-get-coronavirus-before-the-election) - **outcome**: yes | no (YES/NO 토큰) - **quantity**: 주식 수 (shares) - **price**: Limit 주문 시 0.01~0.99 (선택) ## 전제 조건 - Decker 가입 + Slack 연동 - **Polymarket 키 연동** (Decker 설정 → 거래소 API 설정) - 시장 slug는 Polymarket에서 확인 ## Polymarket 키 설정 (에이전트 안내용) 1. **Polygon 지갑**: MetaMask에서 Polygon 네트워크(Chain ID 137) 추가 2. **Polymarket 가입**: https://polymarket.com → 지갑 연결 → USDC.e 입금(거래용) 3. **개인키 추출**: MetaMask → 계정 세부정보 → Export Private Key 4. **Decker 설정**: 로그인 → 설정 → 거래소 API 설정 → Polymarket - Secret Key: Polygon 지갑 개인키(0x로 시작) — **필수** 5. **거래소 선택**: exchange_preference를 "Polymarket"로 설정 후 저장 6. **주문**: "Polymarket 시장-slug yes 10 매수" (slug는 polymarket.com에서 확인) ⚠️ USDC.e 필요. 개인키는 절대 공유하지 마세요. ## 참고 - 메인 decker 스킬: `docs/openclaw_skills/decker/SKILL.md` - Polymarket: 예측시장 (YES/NO 이진 시장)


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: utopiabenben/video-organizer (version 1.0.0)

--- name: video-organizer description: 视频文件批量重命名和整理工具，支持按时间、格式、分辨率等方式整理视频，批量重命名，预览模式和撤销功能！ --- # Video Organizer - 视频文件批量重命名和整理工具 ## 功能特性 - ✅ 自动识别视频文件格式（mp4, avi, mov, mkv, flv, wmv, webm 等） - ✅ 按时间整理（文件修改时间） - ✅ 按格式/扩展名整理 - ✅ 按分辨率整理（720p, 1080p, 4K 等，可选） - ✅ 批量重命名（支持多种命名模式、正则表达式） - ✅ 预览模式（先看效果再执行） - ✅ 撤销操作（安全可靠） ## 安装 ```bash # 方法一：通过 clawhub 安装 clawhub install video-organizer # 方法二：作为 Python 脚本运行 git clone <repo-url> cd video-organizer ``` ## 快速开始 ### 1. 按时间整理视频 ```bash video-organizer organize ./videos --by date --output ./organized ``` ### 2. 按格式整理视频 ```bash video-organizer organize ./videos --by format --output ./organized ``` ### 3. 批量重命名视频 ```bash video-organizer rename ./videos --pattern "video_{001}.mp4" ``` ### 4. 预览模式 ```bash video-organizer organize ./videos --by date --preview ``` ### 5. 撤销操作 ```bash video-organizer undo ./organized ``` ## 详细使用说明 ### organize 命令参数 - `directory`：（必需）要整理的视频目录 - `--by`：整理方式，可选 `date`（按时间，默认）或 `format`（按格式） - `--output`：输出目录，默认在输入目录下创建 `organized` 文件夹 - `--preview`：预览模式，只显示方案不实际执行 ### rename 命令参数 - `directory`：（必需）要重命名的视频目录 - `--pattern`：（必需）命名模式 - `--regex`：正则表达式替换 - `--preview`：预览模式 ### 支持的视频格式 | 格式 | 说明 | |-----|------| | mp4 | MP4 视频 | | avi | AVI 视频 | | mov | QuickTime 视频 | | mkv | Matroska 视频 | | flv | Flash 视频 | | wmv | Windows Media 视频 | | webm | WebM 视频 | ## 示例场景 ### 场景 1：整理下载的视频 ```bash # 按时间整理下载文件夹里的视频 video-organizer organize ~/Downloads --by date --output ~/Videos/Organized ``` ### 场景 2：批量重命名视频 ```bash # 将视频重命名为 video_001.mp4, video_002.mp4... video-organizer rename ./videos --pattern "video_{001}.mp4" ``` ### 场景 3：先预览，再执行 ```bash # 第一步：预览 video-organizer organize ./videos --by format --preview # 第二步：确认没问题后执行 video-organizer organize ./videos --by format --output ./organized ``` ## 注意事项 - 确保有文件的读写权限 - 建议先用 --preview 预览效果 - 大量文件整理可能需要一些时间 - 整理前建议先备份原文件 ## 更新日志 ### v1.0.0 (2026-03-06) - 初始版本发布 - 支持按时间/格式整理 - 支持批量重命名 - 支持预览模式 - 支持撤销操作


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: xushen-ma/apple-cal-anywhere (version 1.3.1)

--- name: apple-cal-anywhere description: Your Apple Calendar, on any platform. iCloud Calendar skill via CalDAV (RFC 4791) — works on macOS/Linux, and Windows with env/keyring auth. Supports event CRUD, multi-calendar queries, managed attachments (RFC 8607), and free/busy lookups. homepage: https://github.com/xushen-ma/apple-cal-anywhere metadata: {"openclaw":{"requires":{"bins":["python3"],"env":["APPLECAL_PASSWORD"]},"primaryEnv":"APPLECAL_PASSWORD"}} --- # apple-cal-anywhere Advanced Apple Calendar integration using CalDAV (RFC 4791) and Managed Attachments (RFC 8607). ## Primary CLI `scripts/applecal.py` ## Capabilities - **Event CRUD**: List, Create, Update, Delete. - **Multi-Calendar Support**: Query multiple calendars in a single command. - **True Attachments**: RFC 8607 compatible (works on iPhone/iPad). - **Free/Busy**: CalDAV scheduling lookup with event-derived fallback. ## Common Commands ### List Events (Combined) Check multiple calendars at once: ```bash python3 scripts/applecal.py events list \ --apple-id [REDACTED_SECRET] \ --calendar Family \ --calendar Work \ --from "2026-02-26T00:00:00Z" \ --to "2026-02-26T23:59:59Z" ``` ### Create All-Day Event ```bash python3 scripts/applecal.py events create \ --apple-id [REDACTED_SECRET] \ --calendar Family \ --summary "Birthday" \ --start "2026-02-26" \ --end "2026-02-26" \ --all-day ``` ### Attach a File (iPhone Safe) ```bash python3 scripts/applecal.py attach add \ --apple-id [REDACTED_SECRET] \ --calendar Family \ --uid <UID> \ --file /path/to/document.pdf ``` ### Free/Busy Check ```bash python3 scripts/applecal.py freebusy \ --apple-id [REDACTED_SECRET] \ --calendar Family \ --from "2026-02-26T00:00:00Z" \ --to "2026-02-26T23:59:59Z" ``` ## Notes - **Birthdays**: The virtual "Birthdays" calendar is not searchable via CalDAV. Key birthdays should be added as physical recurring events in the **Family** calendar for agent visibility. - **Auth**: Resolution order is `APPLECAL_PASSWORD` → Python `keyring` (if installed/configured) → macOS Keychain fallback. Run `doctor` to verify connectivity. - **Event update clearing**: Use `events update --clear-location` / `--clear-description` to explicitly remove optional fields. - **Attachment safety**: `attach add` blocks sensitive paths/names, allowlists file extensions, and supports optional directory scoping via `APPLECAL_ATTACH_DIR`. - **Apple ID**: Always pass `--apple-id [REDACTED_SECRET]` (the iCloud account email, not necessarily your Apple ID login).


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: drodecker/dfs-reset (version 1.0.0)

--- name: dfs-reset description: Detect DFS radar events and reset Ubiquiti airOS devices to restore configured frequencies, managed by UISP NMS. Use when checking whether WISP APs were forced off their configured DFS channels, listing devices from UISP, inspecting AP health or clients, or rebooting a DFS-affected AP after operator confirmation. --- # DFS Reset Use the MCP endpoint configured for this deployment. Placeholder example: `https://example.invalid:8443` Source project for this MCP server: `https://github.com/wispnet/wisp-reset-airos-mcp/` This MCP server uses streamable HTTP with session-based MCP initialization. ## Expected workflow 1. Initialize an MCP session. 2. Send `notifications/initialized`. 3. Call tools on the same session. ## Core workflow 1. Detect: use `detect_dfs` on an AP to compare configured vs actual frequency. 2. Report: tell the operator which APs shifted and what channels they moved to. 3. Reset: use `reset_device` only after operator confirmation. 4. Verify: re-run `detect_dfs` after about 60 seconds. ## Tool reference ### `list_devices(site=None)` List UISP-managed devices, optionally filtered by site. ### `get_device(identifier)` Get detailed device information by name, IP, or UISP device ID. ### `detect_dfs(ip)` Compare UISP configured frequency with the device's actual operating frequency. ### `reset_device(identifier)` Reboot a device through UISP. Always confirm with the operator first. ### `get_clients(ip)` Fetch connected stations for an AP. ### `get_device_stats(ip)` Fetch AP health details including uptime, CPU, memory, and temperature. ### `sweep_clients(site=None)` Collect client tables across APs concurrently. ## Safety rules 1. Never call `reset_device` without explicit operator confirmation. 2. Do not mix broad sweep actions with reset actions in one step. 3. Treat DFS shifts as informational until the operator wants corrective action. 4. Verify every reset with a follow-up `detect_dfs`. 5. Expect partial sweep results when some APs are unreachable. ## Signal interpretation - Better than -65 dBm: good - -65 to -75 dBm: fair - -75 to -80 dBm: poor - Worse than -80 dBm: unusable Typical clean noise floor is around -90 to -95 dBm. Noise above -85 dBm suggests interference.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: zfanmy/openclaw-deploy (version 1.0.4)

# SKILL.md 元数据格式示例 --- name: openclaw-deploy description: Build and deploy OpenClaw as Docker images or portable packages author: zfanmy-梦月儿 version: 1.0.1 homepage: license: MIT keywords: - openclaw - deploy - docker - portable - backup - migration requires: bins: - node - npm - tar --- # OpenClaw Deploy Build and deploy OpenClaw as Docker images or portable packages. ## Features - 🐳 Build Docker images (clean/full versions) - 📦 Create portable packages for deployment - 🚀 Deploy to remote servers with one command - 💾 Backup and restore configurations ## Quick Start ### Build Portable Packages ```bash # Build both clean and full versions ./scripts/build-portable.sh # Export for deployment ./scripts/export-portable.sh ``` ### Deploy to Remote Server ```bash # Deploy clean version ./export/deploy.sh user@remote-server clean /opt/openclaw # Deploy full version ./export/deploy.sh user@remote-server full /opt/openclaw ``` ## Directory Structure ``` openclaw-deploy/ ├── portable/clean/ # Clean version (no personal data) ├── portable/full/ # Full version (with config) ├── export/ # Deployment packages │ ├── openclaw-clean-portable.tar.gz │ ├── openclaw-full-portable.tar.gz │ └── deploy.sh └── scripts/ ├── build-portable.sh ├── export-portable.sh └── deploy.sh ``` ## Usage on Target Server ```bash # Install Node.js ./install-node.sh # Start OpenClaw cd clean && ./start.sh # or cd full && ./start.sh # Access WebUI open http://localhost:18789 ``` ## Requirements - Node.js 22.x - Docker (optional, for Docker builds) - curl, rsync (for deployment) ## Configuration ### Environment Variables You can customize paths using environment variables: ```bash # OpenClaw installation directory (default: auto-detect) export OPENCLAW_INSTALL_DIR=/path/to/openclaw # OpenClaw config directory (default: ~/.openclaw) export OPENCLAW_CONFIG_DIR=/path/to/.openclaw # Output directory (default: ./openclaw-portable-output) export OUTPUT_DIR=/path/to/output ``` ### Example with Custom Paths ```bash export OPENCLAW_INSTALL_DIR=/opt/openclaw export OPENCLAW_CONFIG_DIR=/opt/config/.openclaw export OUTPUT_DIR=/tmp/openclaw-packages ./scripts/build-portable.sh ``` ## Changelog ### v1.0.1 - Fixed hardcoded paths - Added environment variable support - Improved error handling and dependency checks - Added path validation ### v1.0.0 - Initial release ## Author zfanmy-梦月儿


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (HIGH)
Skill: cloudyxuq/sam-food-onboarding (version 1.0.1)

--- name: sam-food-onboarding description: 指导食品企业完成山姆超市产品上架全流程，包含客户需求分析、合规准备、申请提交、审核跟进、上架执行各阶段操作要点；当用户需要山姆上架指导、食品合规咨询或上架问题应对时使用 --- # 山姆超市食品上架指导 ## 任务目标 本 Skill 用于指导食品企业完成山姆超市产品上架全流程操作。 能力包含：客户需求分析、合规资质准备、上架申请流程、审核跟进、问题整改。 触发条件：用户咨询山姆上架流程、食品合规要求、上架问题应对，或提供客户需求需要分析可行性。 ## 前置准备 无特殊系统依赖。需要用户准备以下信息： - 产品基本信息（品名、规格、配料表、营养成分表） - 企业资质文件（营业执照、食品生产许可证等） - 客户具体需求（如有） ## 操作步骤 ### 标准流程 #### 阶段一：客户需求分析 1. **需求收集**：获取客户对产品的具体要求 - 产品规格要求（包装规格、净含量等） - 质量标准要求（有机、无添加、特定认证等） - 价格与成本要求 - 交付时间要求 2. **可行性评估**：分析企业能力是否匹配 - 生产线能力评估 - 资质合规性评估 - 成本利润测算 - 交付周期评估 详见 [references/onboarding-process.md](references/onboarding-process.md) 的"需求分析阶段"章节。 #### 阶段二：合规准备 1. **资质文件梳理**：确认所需证照完整性 - 基础资质：营业执照、食品生产许可证 - 产品资质：第三方检测报告、认证证书 - 标签合规：营养成分表、配料表、标签审核 2. **材料准备**：整理申请所需文档 - 产品技术规格书 - 样品及检测报告 - 企业资质文件 详见 [references/compliance-guide.md](references/compliance-guide.md) 的"资质清单"章节。 #### 阶段三：申请提交 1. **供应商入驻申请** - 通过山姆供应商门户网站提交申请 - 填写企业信息、产品信息 - 上传资质文件 2. **产品上架申请** - 提交产品详细信息 - 上传产品图片、标签图片 - 提交检测报告及认证证书 详见 [references/onboarding-process.md](references/onboarding-process.md) 的"申请阶段"章节。 #### 阶段四：审核跟进 1. **审核状态跟踪** - 定期查询审核进度 - 关注审核反馈意见 2. **问题整改** - 根据审核意见进行整改 - 补充缺失材料 - 重新提交审核 详见 [references/stage-checklist.md](references/stage-checklist.md) 的"审核阶段检查清单"。 #### 阶段五：上架执行 1. **合同签订**：确认合作条款 2. **样品确认**：提供确认样品 3. **首批供货**：按订单要求发货 4. **持续跟进**：销售表现跟踪、补货协调 详见 [references/stage-checklist.md](references/stage-checklist.md) 的"上架阶段检查清单"。 ### 可选分支 - **当客户需求涉及特殊认证**（有机、绿色食品、清真等）：参考 [references/compliance-guide.md](references/compliance-guide.md) 的"特殊认证要求"章节 - **当审核不通过需要整改**：参考 [references/onboarding-process.md](references/onboarding-process.md) 的"常见问题与整改"章节 - **当涉及进口食品**：参考 [references/compliance-guide.md](references/compliance-guide.md) 的"进口食品要求"章节 ## 资源索引 - 上架流程详解：见 [references/onboarding-process.md](references/onboarding-process.md)（何时读取：需要了解各阶段详细操作时） - 合规要求指南：见 [references/compliance-guide.md](references/compliance-guide.md)（何时读取：需要确认资质要求、标签规范时） - 阶段检查清单：见 [references/stage-checklist.md](references/stage-checklist.md)（何时读取：需要在各阶段进行自查核验时） ## 注意事项 - 山姆超市对食品质量要求严格，务必确保所有资质文件真实有效 - 标签合规是常见审核不通过原因，建议提前进行标签预审 - 审核周期通常为 2-4 周，需预留充足时间 - 保持与采购的及时沟通，了解审核进度和反馈意见 - 本 Skill 中的流程指导由智能体根据用户提供的信息进行分析和建议，具体操作需根据山姆官方要求执行 ## 使用示例 ### 示例一：客户需求分析 用户表达："客户要求供应一款有机坚果，规格 500g，需要有机认证，我们厂能不能做？" 执行方式：智能体处理 - 分析需求要点：有机认证、500g 规格 - 评估资质要求：有机产品认证证书、生产许可证 - 提供可行性建议：确认企业是否已获有机认证，如无则指导申请流程 ### 示例二：上架申请指导 用户表达："资质都齐了，接下来怎么申请上架？" 执行方式：智能体处理 - 指导访问山姆供应商门户 - 说明需要填写的信息和上传的材料 - 提供申请提交注意事项 ### 示例三：审核问题整改 用户表达："审核不通过，说营养成分表标注不符合要求，怎么改？" 执行方式：智能体处理 - 分析问题原因：营养成分表标注规范 - 提供整改建议：根据 GB 28050 标准调整标注方式 - 建议整改后重新提交


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)