360 Secure SkillHub
360 安全技能中心

Moderation

核心功能是提供分四阶段的结构化UGC内容审核工作流,包含目标澄清、方案设计、落地验证、运营迭代,配套完成 checklist与实操技巧。典型使用场景:用户提及内容审核工作、需要体系化方案而非零散建议,用于审核体系搭建、评审或 stakeholder沟通。输入为用户的审核需求,输出可落地的步骤、风险提示等指导内容,支持自定义调整。

codenova58
codenova58
热度 45.03
最近更新 2026-05-11 17:37:19
分类:安全依赖:纯提示词应用场景:工作流 / 法律文档

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add moderation
Metadata
name
moderation
description
Moderation workflows, thresholds, and appeals. Use when handling UGC at scale.

Moderation

Structured guidance for content moderation (UGC policy, thresholds, appeals): confirm triggers, propose the stages below, and adapt if the user wants a lighter pass.

When to Offer This Workflow

Trigger conditions:

  • User mentions content moderation or closely related work
  • They want a structured workflow rather than ad-hoc tips
  • They are preparing a review, rollout, or stakeholder communication

Initial offer: Explain the four stages briefly and ask whether to follow this workflow or work freeform. If they decline, continue in their preferred style.

Workflow Stages

Stage 1: Clarify context & goals

Anchor on categories and severity. Ask what success looks like, constraints, and what must not break. Capture unknowns early.

Stage 2: Design or plan the approach

Translate goals into a concrete plan around human review workflows. Compare alternatives and explicit trade-offs; avoid implicit assumptions.

Stage 3: Implement, validate, and harden

Execute with verification loops tied to threshold tuning. Prefer small steps, measurable checks, and rollback points where risk is high.

Stage 4: Operate, communicate, and iterate

Close the loop with appeals and transparency: monitoring, documentation, stakeholder updates, and lessons learned for the next cycle.

Checklist Before Completion

  • Goals and constraints are explicit for moderation
  • Risks and trade-offs are stated, not hand-waved
  • Verification steps match the change’s impact (tests, canary, peer review)
  • Operational follow-through is covered (monitoring, docs, owners)

Tips for Effective Guidance

  • Be procedural: stage-by-stage, with clear exit criteria
  • Ask for missing context (environment, scale, deadlines) before prescribing
  • Prefer checklists and concrete examples over generic platitudes
  • If the user declines the workflow, switch to freeform help without lecturing

Handling Deviations

  • If the user wants to skip a stage: confirm and continue with what they need.
  • If context is missing: ask targeted questions before strong recommendations.
  • Prefer concrete examples, trade-offs, and verification steps over generic advice.

Quality Bar

  • Each recommendation should be actionable (what to do next).
  • Call out failure modes relevant to moderation (security, scale, UX, or ops).
  • Keep tone direct and respectful of the user’s time.