File Monitor Feishu Notify

文件监控并自动通知到飞书群

Security Scan

The skill's code and instructions mostly match its stated purpose (monitor a directory and send Feishu group notifications), but there are a few missing files and operational details you should verify before installing and giving it secrets.

Purpose & Capability

Name/description match the included Python scripts: simple-monitor.py detects new files and writes a notify file; auto-send.py reads that file and posts to Feishu's API. Requested resources (none) are proportional.

Instruction Scope

SKILL.md and README instruct running start-monitor.ps1 and rely on HEARTBEAT, but start-monitor.ps1 (and HEARTBEAT configuration) is not present in the file manifest. The README also references several helper ps1 scripts (publish/start) that are missing. This mismatch means the runtime instructions are incomplete and you'll need to create or inspect a start script before running. Also note the scripts will include file names and full paths in notifications (possible information exposure).

Install Mechanism

No install spec; this is an instruction-and-script skill only. No downloads or third-party package installs are requested.

Credentials

No env vars are required; credentials (Feishu App ID/Secret and chat_id) are stored in config.json (a file under the skill directory). Storing secrets in a local config file is functional but risky if you publish the repo or forget to .gitignore config.json—the included docs even show GitHub publish steps. Ensure config.json is not committed to any remote.

Persistence & Privilege

always is false and the skill does not request elevated platform privileges. It relies on an external HEARTBEAT/monitoring process to restart processes but does not appear to modify other skills or global configs.

Assessment

This skill appears to implement exactly what it claims: a local file watcher that posts notifications to a Feishu group. Before installing: - Confirm or supply the missing start-monitor.ps1 (the README references it but it is not included). Don't run unreviewed startup scripts if you don't have them. - Do not put your Feishu app_secret/app_id into a repo-tracked config.json. Use config.example.json as suggested and ensure config.json is in .gitignore before any git push. - Review and, if necessary, limit the watch_dir you configure — the monitor will read file names and include full paths in notifications, which may leak sensitive paths/names. - Verify network endpoints: the code calls open.feishu.cn (official Feishu API) — if you use a different endpoint, inspect it. - If you want heartbeat/autostart behavior, create or inspect the HEARTBEAT/start script locally rather than relying on unspecified automated configuration. If any of the above items are unacceptable or unclear, treat this skill as incomplete until you correct them.

File Monitor Feishu Notify Skill

Description

监控指定目录的文件变化，新文件自动发送到飞书群聊。

Trigger

• 文件监控自动触发
• HEARTBEAT 守护进程运行

Usage

安装

# 已本地安装，无需额外操作

配置

编辑 config.json：

{
  "watch_dir": "D:\\云文档同步",
  "notify_file": ".data/.pending_notify.md",
  "feishu": {
    "app_id": "cli_xxx",
    "app_secret": "xxx",
    "chat_id": "oc_xxx"
  },
  "check_interval": 2,
  "log_file": "logs/auto-send.log"
}

启动

# HEARTBEAT 会自动启动，或手动运行：
powershell -ExecutionPolicy Bypass -File "skills/file-monitor-feishu-notify/start-monitor.ps1"

Files

• scripts/simple-monitor.py - 文件监控器
• scripts/auto-send.py - 自动发送器
• start-monitor.ps1 - 启动脚本
• config.json - 配置文件
• logs/auto-send.log - 日志文件

Tags

file, monitor, feishu, notification, automation

Compatibility

• OpenClaw: ✅
• HEARTBEAT: ✅
• Windows: ✅