Token导航 LogoToken导航TokenDH.com
效率权限需确认clawhub未标认证来源可访问clear审计通过

game-design-social-satisfaction-matrix游戏设计社会满意度矩阵

Agent Skill

用于辅助界面设计、视觉规范、排版、配色、布局和交互体验优化。它适合让 Agent 根据产品场景整理页面结构、生成 UI 方案、检查视觉一致性或改进组件层级。使用时需要结合现有品牌、设计系统和用户任务,不应只堆装饰元素;涉及真实页面改动时,应通过截图或浏览器预览检查文本溢出、对齐和响应式表现。

总安装

1,622

周安装

65

GitHub Stars

公开资料未说明

下载量

525
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:game-design-social-satisfaction-matrix(游戏设计社会满意度矩阵)
来源仓库:https://github.com/stanestane/game-design-social-satisfaction-matrix
安装命令:
openclaw skills install game-design-social-satisfaction-matrix
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install game-design-social-satisfaction-matrix

简介

评估游戏社交功能带来满意或不满意的潜力。

  • 适用于多人元素、合作机制或竞争系统的设计审核。
  • 构建二维矩阵分析社交影响方向与强度。
  • 输出为定性评估,需结合具体交互细节完善。
  • game-design-social-satisfaction-matrix 属于效率类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
game-design-social-satisfaction-matrix
description
Evaluate a game's social features and multiplayer elements by their potential to create social satisfaction versus social dissatisfaction. Use when auditing chat, voice, friend systems, gifting, lobbies, social hubs, guilds, reporting tools, cooperative mechanics, profile surfaces, or other social elements; when comparing which features are basic, critical, booster, or secondary; or when deciding where to reduce social risk, increase social stickiness, and prioritize improvements to multiplayer or community-facing systems.

Game Design Social Satisfaction Matrix

Use the Social Satisfaction Matrix to classify social elements by how much they can increase social satisfaction, how much they can create social dissatisfaction, and what that implies for design priority.

This skill is especially useful when a team knows a feature is "social" but does not yet understand whether it is an expected basic, a risky high-impact critical element, a nice booster, or mostly secondary.

Core principle

Not all social features matter in the same way.

Some social elements are basic expectations that rarely delight but cause frustration when missing. Some are high-risk, high-value systems that can either deepen connection or amplify harm. Some are nice boosters. Some barely move the needle. The point of the matrix is to stop treating all social features as equally important or equally dangerous.

The matrix

Classify elements into four categories:

Basic

Must-do elements.

  • low potential to create delight
  • high potential to create dissatisfaction if missing or weak
  • expected foundations of the social experience

Typical examples:

  • friend list
  • stable party formation
  • baseline group management
  • basic reporting access

Critical

Make-or-break elements.

  • high potential to create satisfaction
  • high potential to create dissatisfaction
  • socially valuable but risky if handled poorly

Typical examples:

  • voice chat
  • open text chat
  • matchmaking surfaces that strongly affect teammate quality
  • live team communication systems
  • public social reputation surfaces

Booster

Could-do elements that add satisfaction.

  • can make the experience nicer, warmer, or more memorable
  • low downside if absent
  • usually not necessary for functional play

Typical examples:

  • lightweight gifting
  • celebratory emotes
  • temporary cosmetic sharing
  • playful social acknowledgements

Secondary

Low-impact elements.

  • low potential to create strong satisfaction
  • low potential to create strong dissatisfaction
  • may matter for niche segments, but not majorly for the overall social experience

Typical examples depend heavily on audience and context. Something secondary for one game or segment may be critical for another.

What to produce

Generate:

  1. Audit target - what game, mode, or set of social elements is being reviewed
  2. Element map - where each chosen element sits in the matrix
  3. Rationale - why each element belongs there
  4. Risk and opportunity view - what the matrix reveals about the current social landscape
  5. Improvement priorities - what to fix, protect, redesign, add, or deprioritize
  6. Sweet-spot judgment - where the design should aim to increase satisfaction without creating disproportionate social risk

Process

1. Define the social scope

Clarify:

  • what game, feature set, or mode is being audited
  • which social elements are in scope
  • what audience or segment matters most
  • whether the team cares more about retention, safety, delight, community health, matchmaking quality, or social stickiness

Write:

  • Target
  • Audience context
  • Business/design concern

2. Choose the elements to map

Pick one or more social elements.

Good candidates include:

  • game mechanics with social consequences
  • chat and voice systems
  • nonverbal communication systems
  • friend, guild, or party tools
  • shared activities
  • reporting and moderation surfaces
  • profile and identity surfaces
  • social hubs or hangout spaces
  • gifting, acknowledgements, and reciprocal mechanics
  • goal-setting systems that require or encourage social participation

3. Assess satisfaction potential

For each element, ask:

  • can this create positive social moments?
  • does it help players bond, coordinate, celebrate, contribute, or belong?
  • does it increase trust, recognition, or meaningful cooperation?
  • does it align selfish goals with prosocial outcomes?
  • can it make the game feel warmer, stickier, or more socially rewarding?

Possible satisfaction sources:

  • prosocial action
  • bonding and familiarity
  • positive recognition
  • meaningful contribution
  • active participation
  • shared accomplishment
  • belonging and group identity
  • balanced interdependence

4. Assess dissatisfaction potential

For each element, ask:

  • can this facilitate harassment, griefing, or cheating?
  • does it depend on trust that may not exist?
  • can it create conflicting goals or blame?
  • does it require hidden knowledge or high skill from everyone?
  • can it leave weaker players exposed or unsupported?
  • are expectations unclear?
  • does it create open affordances with weak guardrails?

Possible dissatisfaction sources:

  • disruptive behavior
  • trust dependency
  • incompatible goals
  • knowledge dependency
  • skill dependency
  • task interdependence under pressure
  • weak social support
  • unclear expectations
  • abuseable communication affordances

5. Place each element in the matrix

Now classify each element:

  • Basic
  • Critical
  • Booster
  • Secondary

Do not classify by gut feel alone. Tie the placement to its satisfaction and dissatisfaction potential.

Also note if an element is:

  • misclassified by the team today
  • segment-dependent
  • healthy in concept but badly implemented

6. Compare the overall landscape

Step back and ask:

  • is the game overinvested in risky critical systems with weak guardrails?
  • is it missing basic foundations?
  • is it trying to add boosters before basics work?
  • are supposedly secondary features actually critical for the target segment?
  • is the social experience too functional and dry, with no boosters?
  • are there obvious opportunities to move a feature toward the sweet spot?

7. Aim for the sweet spot

The ideal is not zero risk.

The sweet spot is where a social element creates significant satisfaction while keeping dissatisfaction risk manageable through good design, guardrails, and support systems.

Typical improvement strategies:

  • Add a feature to increase positive social value
  • Change a feature to reduce downside or improve readability
  • Bundle features so multiple small supports increase aggregate satisfaction
  • Create a feature system so elements reinforce one another instead of standing alone

8. Convert the matrix into action

For each priority element, specify:

  • Current category
  • Why it matters
  • Main social upside
  • Main social downside
  • Design change
  • Expected effect

Response structure

Target

  • ...

Matrix Map

ElementCategorySatisfaction PotentialDissatisfaction PotentialWhy It Sits Here
...............

Landscape Read

  • ...

Priority Risks

  1. ...
  2. ...
  3. ...

Best Opportunities

  1. ...
  2. ...
  3. ...

Sweet-Spot Recommendations

  1. ...
  2. ...
  3. ...

Fast mode

Use this quick pass when speed matters:

  • which social elements are basic expectations?
  • which are critical and risky?
  • which are nice boosters?
  • which barely matter?
  • where is the game under-protected, overexposed, or missing easy social upside?

Working principle

A socially sticky game is not built by piling on social features. It is built by understanding which social elements are foundational, which are dangerous but powerful, which are delightful extras, and which are mostly noise.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

86.15%
按下载量换算452

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills