用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/duclm1x1/Dive-Ai --skill content-moderation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Persistent memory system for AI agents following Model Context Protocol (MCP). Use for storing long-term memories across sessions, semantic search of past knowledge, building knowledge graphs, auto-injecting context, deduplicating memories, syncing to cloud storage. Essential for agents that need to remember decisions, solutions, preferences, and learned patterns over time.
Persistent memory system for AI agents following Model Context Protocol (MCP). Use for storing long-term memories across sessions, semantic search of past knowledge, building knowledge graphs, auto-injecting context, deduplicating memories, syncing to cloud storage. Essential for agents that need to remember decisions, solutions, preferences, and learned patterns over time.
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
正在显示 SKILL.md
基于 SOC 职业分类
| name | content-moderation |
| description | Moderate text, images, and video using Vettly's content moderation API via MCP server. |
| metadata.openclaw | {"requires":{"env":["VETTLY_API_KEY"],"bins":["npx"]}} |
Moderate user-generated content using Vettly's AI-powered content moderation API. This skill uses the @vettly/mcp MCP server to check text, images, and video against configurable moderation policies with auditable decisions.
Add the @vettly/mcp MCP server to your configuration:
{
"mcpServers": {
"vettly": {
"command": "npx",
"args": ["-y", "@vettly/mcp"],
"env": {
"VETTLY_API_KEY": "your-api-key"
}
}
}
}
Get an API key at vettly.dev.
moderate_contentCheck text, image, or video content against a Vettly moderation policy. Returns a safety assessment with category scores, the action taken, provider used, latency, and cost.
Parameters:
content (required) - The content to moderate (text string, or URL for images/video)policyId (required) - The policy ID to use for moderationcontentType (optional, default: text) - Type of content: text, image, or videovalidate_policyValidate a Vettly policy YAML without saving it. Returns validation results with any syntax or configuration errors. Use this to test policy changes before deploying them.
Parameters:
yamlContent (required) - The YAML policy content to validatelist_policiesList all moderation policies available in your Vettly account. Takes no parameters. Use this to discover available policy IDs before moderating content.
get_usage_statsGet usage statistics for your Vettly account including request counts, costs, and moderation outcomes.
Parameters:
days (optional, default: 30) - Number of days to include in statistics (1-365)get_recent_decisionsGet recent moderation decisions with optional filtering by outcome, content type, or policy.
Parameters:
limit (optional, default: 10) - Number of decisions to return (1-50)flagged (optional) - Filter to only flagged content (true) or safe content (false)policyId (optional) - Filter by specific policy IDcontentType (optional) - Filter by content type: text, image, or videoModerate this user comment for my community forum policy:
"I hate this product, it's the worst thing I've ever used and the developers should be ashamed"
Call list_policies to find available policies, then moderate_content with the appropriate policy ID and return the safety assessment.
Validate this moderation policy YAML:
categories:
- name: toxicity
threshold: 0.8
action: flag
- name: spam
threshold: 0.6
action: block
Call validate_policy and report any syntax or configuration errors.
Show me all flagged content from the last week
Call get_recent_decisions with flagged: true to retrieve recent moderation decisions that were flagged.
list_policies first if you don't know which policy ID to usevalidate_policy to test policy changes before deploying to productionget_usage_stats to monitor costs and catch unexpected spikesget_recent_decisions by contentType or policyId to narrow results