Community Ops Creator Assets

Community Ops Creator Assets

Use this skill when community members create value: works, answers, tutorials, demos, reviews, bug reports, templates, workflows, examples, or social proof.

Project Inputs

Get the contribution source, creator attribution, permission status and allowed uses, intended audience and surface, selection criteria, visibility limits, and follow-up approval from the user or an approved project record. A link or record ID is preferable to copying private content.

The skill supplies the creator and asset workflow. It does not include creator lists, member work, permission, showcase rights, ranking criteria, or approved outreach. Treat every example as fictional structure. When permission or attribution is missing, stop at an internal candidate list or permission request draft.

Creator Loop

discover -> qualify -> ask/permission -> polish/package -> showcase -> follow-up -> asset library

What To Extract

For each creator or submission, capture:

• who created it and where it appeared;
• what value it shows;
• whether attribution/permission is clear;
• the approved use, visibility, duration, and any revocation request;
• whether it is safe to showcase;
• where it can be reused: showcase, tutorial, FAQ, case study, social post, product example, onboarding proof;
• next follow-up.

Output Pattern

**Creator/Asset Signals**
| Item | Source | Why it matters | Permission/status | Next step |
|---|---|---|---|---|

**Showcase Plan**
- Surface: ...
- Copy angle: ...
- Attribution: ...
- Owner gate: ...

**Follow-up Plan**
- Creator/member: ...
- Ask: ...
- Timing: ...
- Risk: ...

**Asset Library Update**
- FAQ/tutorial/case/example/social proof: ...

Guardrails

Require explicit confirmation before publishing or reusing member work, contacting or mentioning a creator, ranking submissions, or implying endorsement. Record permission scope and attribution; stop reuse when permission is revoked. Avoid shame rankings or personal profiling. Keep adult, private, sensitive, or paid-member content in the correct visibility context.

Creator recognition can support trust and continued contribution. Treat it as relationship work and review the evidence instead of assuming a retention result.

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.