Install
$ agentstack add skill-shiroryu9-community-ops-kit-community-ops-paid-members ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Community Ops Paid Members
Use this skill for paid members, premium users, customers, VIPs, high-value members, or users with special access/benefits.
Project Inputs
Get the segment definition, confirmed benefits, entitlement or access basis, current issue or opportunity, available evidence, support path, and approval boundary for contact, discounts, benefits, roles, or access from the user or an approved project source.
The skill supplies the operating method. It does not include customer lists, payment status, benefits, discounts, role mappings, renewal data, or outreach permission. Do not infer those values from labels such as VIP or from repository examples. Use the minimum necessary user reference and mark missing entitlement or benefit facts for owner confirmation.
Paid Member Loop
access -> value discovery -> benefit use -> support/recognition -> renewal/upgrade signal -> review
Design Questions
- What value does this segment receive beyond basic access?
- Which benefits are confirmed, and which need owner/product approval?
- What activity, support, tutorial, office hour, or showcase is exclusive to them?
- How are payment, entitlement, role, access, or discount issues escalated?
- What proves the segment is getting value?
Output Pattern
**Segment**
[Paid / premium / VIP / customer / high-value user.]
**Value Promise**
[Confirmed benefits only.]
**Operating Plan**
| Need | Action | Surface | Owner gate | Evidence |
|---|---|---|---|---|
**Care List**
- [Minimum necessary user/group reference + issue/opportunity + next follow-up.]
**Risk Boundary**
- Payment/access/discount/role changes require confirmation.
- Do not promise unconfirmed benefits.
**Review Signals**
- benefit usage;
- support resolution;
- participation;
- renewal/upgrade or churn-risk signals if available.
Guardrails
Payment, discounts, role access, paid benefits, priority support promises, and renewal claims are high-stakes. Mark them owner-confirmation needed unless explicitly confirmed. Require confirmation before outreach, mentions, public recognition, access changes, discounts, or benefit promises. Keep sensitive member issues private, use the minimum necessary user-level data, and avoid personal consumption profiles.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ShiroRyu9
- Source: ShiroRyu9/community-ops-kit
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.