Discord Thread Naming Backstop Workflow
v1.0.0用于执行 Discord 线程命名兜底（backstop）巡检与改名，专门处理某个 guild 下指定 parent channel 中“最近新建但未命名规范”的线程，补上 prehook 漏网，而不是批量回扫历史。遇到“线程重命名兜底”“dispatch 线程命名规范”“只检查最近 20 分钟线程”“JSON...
⭐ 0· 110·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name and description declare a narrowly-focused Discord thread renaming backstop for one guild and one parent channel; all instructions, hardcoded IDs (guildId/channelId), and notification targets align with that purpose. The fixed-channel design is explicit in the text rather than surprising, so the requested capabilities match the stated purpose.
Instruction Scope
SKILL.md confines actions to reading the thread list, filtering by creation time/heuristics, and performing at-most-two attempts at channel-edit with a final channel-info consistency check. It explicitly forbids scanning archives or broader channels and emphasizes silence-on-success and limited-notification rules. There are no instructions to read arbitrary local files, environment variables, or exfiltrate data to unknown endpoints.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk or downloaded. That minimizes install-time risk and matches the content of SKILL.md.
Credentials
The skill does not declare environment variables or credentials, yet it presumes the agent/platform can perform Discord actions (thread-list, channel-edit, channel-info). This is coherent if the platform supplies a Discord connector; however, users should verify that the connector's credentials and bot permissions are scoped minimally (to the specified guild/channel and only to the actions required). The hardcoded notification channel ID is also plausible for its purpose but worth confirming.
Persistence & Privilege
The skill is not always-enabled and is user-invocable; model invocation is allowed (normal). It does not request persistent system-level changes or modification of other skills' configs. No privilege escalation or always:true flag is present.
Assessment
This skill is narrowly scoped and internally consistent, but before installing/checking it you should: (1) confirm the agent environment provides a Discord connector and that its bot token/credentials are limited to the intended guild and minimal permissions (thread listing, channel-edit, channel-info) to reduce blast radius; (2) verify the hardcoded guildId/channelId and the notification channel ID (1478996389727043584) are intended — the skill will send P2/RESOLVED messages there; (3) test in a staging guild/channel to ensure the heuristics (20-minute window, JSON/long-title detection, regex) behave as you expect; (4) if you need reuse across guilds/channels, request a configurable version rather than relying on hardcoded IDs. If you cannot confirm connector permissions or notification targets, treat installation as higher risk.Like a lobster shell, security has layers — review code before you run it.
latestvk97dg701s2ssv334kx270sh01d83ckv4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🧵 Clawdis