菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ShiroRyu9/community-ops-kit --skill community-ops-creator-assets命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when designing, reviewing, or documenting community-operations automation, including recurring data collection, report assembly, activity reminders, draft generation, status-board updates, skill/version checks, AI/bot/operator handoffs, execution states, post-action verification, dry-runs, audit trails, owner approval gates, and safe delegation of repeated work to tools.
Use when turning daily community operations into a concise daily report, daily log, work recap, owner update, standup note, or personal community-ops record. Separates completed public actions, drafts, analysis, follow-ups, risks, data gaps, and tomorrow actions without overstating unconfirmed work.
Use when writing, rewriting, reviewing, or polishing community-operations language, including announcements, activity posts, reminders, result posts, daily/weekly reports, public articles, skill descriptions, resume bullets, interview stories, stakeholder updates, and natural-language edits. Trigger when the user asks for writing that sounds human, concrete, less templated, less AI-like, or free of repetitive contrast patterns.
基于 SOC 职业分类
正在显示 SKILL.md
| name | community-ops-creator-assets |
| description | 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. |
Use this skill when community members create value: works, answers, tutorials, demos, reviews, bug reports, templates, workflows, examples, or social proof.
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.
discover -> qualify -> ask/permission -> polish/package -> showcase -> follow-up -> asset library
For each creator or submission, capture:
**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: ...
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.