Community ops support risk
Skill ShiroRyu9/community-ops-kit/skills/community-ops-support-risk
AI-ready community operations SOPs with safe automation, human approval, and verified execution.
npx -y skills add ShiroRyu9/community-ops-kit --skill community-ops-support-riskAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when triaging community support issues, payment or access problems, moderation incidents, trust and safety concerns, permission/role changes, complaints, escalation paths, public-risk copy, evidence gaps, or operations that could affect user rights, privacy, rewards, discounts, webhooks, bots, or official claims.
SKILL.md
2.6 KB, as published. Nobody here has run it
Community Ops Support Risk
Use this skill when a community issue touches support, safety, payments, permissions, public claims, moderation, privacy, rewards, discounts, roles, DMs, webhooks, bots, or official account actions.
Project Inputs
Get the issue type, severity, confirmed facts, timestamps, minimum necessary user or record reference, evidence paths or IDs, applicable policy, desired resolution, and public/private boundary from the user or an approved source.
The skill supplies triage and escalation structure. It does not include a community's policy, compensation rules, account state, payment facts, moderation history, or permission data. Missing evidence remains missing. Do not import outcomes from examples, and do not request secrets, full private-message histories, payment details, or unrelated personal data.
Triage First
Classify the issue:
- access/role/permission;
- payment/discount/entitlement;
- support bug or product issue;
- moderation/safety/rules;
- reward/winner/benefit dispute;
- public copy or official claim risk;
- privacy or sensitive user data.
Risk Rule
Use the minimum access and user data needed to understand the issue. Do not execute public messaging, DMs, mentions, financial actions, rewards, discounts, role/channel/permission changes, bot/webhook changes, deletions, or official claims without explicit confirmation. When evidence is missing, ask for it or mark the item blocked.
Output Pattern
**Issue Type**
[Category and severity.]
**Confirmed Facts**
- [Who/what/where/when/evidence.]
**Missing Evidence**
- [IDs, screenshots, links, logs, policy, owner decision, etc.]
**Recommended Action**
| Priority | Action | Owner | Public/private | Risk |
|---|---|---|---|---|
**Do Not Do Yet**
- [Any send, role edit, reward, discount, DM, public claim, webhook/bot change, or deletion that needs confirmation.]
**User-Facing Draft**
[Only if requested; keep it factual and low-commitment.]
Guardrails
Do not invent policy, compensation, blame, timelines, or official product status. Do not store secrets, webhook URLs, raw private messages, personal profiles, or unnecessary sensitive data. Preserve evidence paths and timestamps when available.