Community ops creator assets

Skill ShiroRyu9/community-ops-kit/skills/community-ops-creator-assets

AI-ready community operations SOPs with safe automation, human approval, and verified execution.

Install

npx -y skills add ShiroRyu9/community-ops-kit --skill community-ops-creator-assets

Assembled 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 identifying, nurturing, or operating community creators, contributors, superusers, ambassadors, featured members, user-generated content, showcases, tutorials, case studies, attribution, permissions, or turning submissions into reusable community/product content assets.

SKILL.md

2.6 KB, as published. Nobody here has run it

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.