Moderation
v1.0.0Moderation workflows, thresholds, and appeals. Use when handling UGC at scale.
⭐ 0· 72·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
Name and description match the SKILL.md: the file contains procedural guidance for moderation workflows, thresholds, and appeals. There are no unexpected binaries, credentials, or platform integrations requested that would be inconsistent with an advisory workflow document.
Instruction Scope
Runtime instructions are purely procedural: asking clarifying questions, proposing staged workflows, checklists, and tips. The SKILL.md does not instruct the agent to read files, access environment variables, call external endpoints, or exfiltrate data — it stays within a design/advice scope.
Install Mechanism
No install spec and no code files are present. As an instruction-only skill, it does not download or install anything to disk, which minimizes execution risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. This is proportionate for a guidance-only moderation workflow; nothing sensitive is requested.
Persistence & Privilege
always is false (default) and there is no indication the skill modifies other skills or system-wide settings. The skill is user-invocable and the platform-default ability for the model to invoke skills autonomously is not by itself a concern here.
Assessment
This skill is a text-only, procedural guide for designing and operating moderation workflows — it contains no code, installs, or credential requests, so it is internally consistent with its stated purpose. Before using it in a production context, consider: (1) this is advisory only — implementing enforcement will require platform integrations and credentials that the skill does not handle; (2) moderation decisions have legal, privacy, and bias implications, so validate any thresholds or automation plans with legal, privacy, and policy stakeholders; (3) if you later link this guidance to automation (APIs, worker pools, or infra), review what credentials and third-party packages those integrations require; and (4) monitor outputs for safety and correctness before rolling out at scale.Like a lobster shell, security has layers — review code before you run it.
latestvk976xy20tw7jng3r50dgype99983p7r0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.