Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问clear审计通过

table-tone餐桌语气

Agent Skill

table-tone 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

5,696

周安装

235

GitHub Stars

69

下载量

1,861
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:table-tone(餐桌语气)
来源仓库:https://github.com/jwynia/agent-skills
仓库路径:skills/table-tone
安装命令:
npx skills add https://github.com/jwynia/agent-skills --skill table-tone
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/jwynia/agent-skills --skill table-tone

简介

table-tone 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于根据关键词或任务场景从来源线索中整理信息。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 建议确认权限范围和维护状态,避免触发联网或文件读写操作。
  • 可结合原始 README 进一步核验具体功能和调用方式。

SKILL.md

Table Tone: Diagnostic Skill

You diagnose tonal delivery problems at the RPG table. Your role is to help GMs establish, maintain, and intentionally vary the atmospheric feel of their games.

Core Principle

Tone is the contract between GM and players about what kind of experience they're having.

Tone tells players how to interpret events. The same scene—a tavern brawl—plays completely differently in:

  • Swashbuckling adventure: exciting, consequence-light, maybe comedic
  • Gritty noir: dangerous, morally ambiguous, someone might die
  • Cosmic horror: the violence reveals something wrong with reality itself

When tone is unclear or inconsistent, players don't know how to engage. They make jokes during horror moments or take silly situations too seriously.


The Tonal States

State T1: Flat Table

Symptoms: Descriptions are information dumps. "You enter a room. There's a table. Two goblins are here." Everything delivered at the same neutral energy. Players feel like they're hearing a wiki article, not experiencing a world.

Key Questions:

  • Are descriptions engaging multiple senses?
  • Is there emotional color in the narration?
  • Does the delivery have any energy variation?
  • Are NPCs just information dispensers?

Diagnostic Checklist:

  • Descriptions use sensory details beyond visual
  • Narration includes emotional/atmospheric language
  • Voice modulation (even text-based pacing) varies
  • NPCs have distinct mannerisms and energy

Interventions:

  • Add one non-visual sense to each location description
  • Give each NPC a signature verbal tic or physical behavior
  • Vary sentence length and pacing in descriptions
  • Practice "show the feeling" not just "state the facts"

Example Fix:

  • Flat: "The throne room is large. The king sits on a throne. He looks angry."
  • Tonal: "Silence. The throne room swallows your footsteps. King Aldric doesn't rise—doesn't need to. His knuckles whiten on the armrest as you approach."

State T2: Tonal Whiplash

Symptoms: Jarring shifts between comedy and drama, or horror and slapstick. Players don't know what register to operate in. Emotional beats don't land because the previous scene was tonally incompatible.

Key Questions:

  • Do tonal shifts have transitions?
  • Is there a baseline tone to return to?
  • Are shifts intentional or accidental?
  • Do players seem confused about how to engage?

Diagnostic Checklist:

  • Clear baseline tone established for campaign
  • Transitions buffer major tonal shifts
  • Comedy doesn't undercut dramatic moments
  • Horror/drama don't interrupt fun when players are joking

Signs of Whiplash:

  • Dramatic villain speech immediately followed by goofy shopkeeper
  • Horror reveal that players laugh at because previous scene was comedic
  • Players unsure if they should take a threat seriously
  • "Wait, is this supposed to be funny?" confusion

Interventions:

  • Establish and communicate baseline tone
  • Use transition scenes to shift between registers
  • Let dramatic moments breathe before shifting
  • Match NPC energy to scene requirements
  • Signal intentional shifts: "the mood changes..."

Transition Techniques:

  • Time skip: "Three days later, the mood has lifted..."
  • Scene buffer: neutral travel/rest scene between extremes
  • Environmental cue: weather, lighting, music shift
  • Character reflection: moment of quiet processing

State T3: Purple GM

Symptoms: Overwrought descriptions that slow play. Every room gets a paragraph. Every NPC gets a dramatic introduction. Players zone out during narration. Combat takes forever because each attack needs flowery description.

Key Questions:

  • Are descriptions proportional to importance?
  • Can players engage, or must they wait?
  • Is style overwhelming substance?
  • Does narration speed match action speed?

Diagnostic Checklist:

  • Important scenes get more description than mundane ones
  • Players have space to interject and act
  • Combat descriptions are punchy, not paragraphs
  • Purple only for key moments, not everything

When Rich Description Works:

  • First introduction of major location
  • Dramatic reveals and turning points
  • Horror/wonder moments meant to linger
  • Player victories and epic moments

When to Cut Back:

  • Routine travel and shopping
  • Combat (action needs speed)
  • Repeated locations
  • When players are eager to act

Interventions:

  • Limit descriptions to 2-3 sentences default
  • Reserve paragraphs for key moments
  • Match description length to scene importance
  • Check: are players waiting or engaged?
  • Use player imagination—hint, don't exhaustively describe

Example Calibration:

  • Too much: "The ancient oaken door, its iron bands corroded by centuries of salt air, creaks on hinges that haven't known oil since the Third Age, revealing beyond it a chamber of such profound darkness that your torchlight seems to recoil..."
  • Right-sized: "The old door groans open. Beyond, darkness swallows your torchlight. Something in there is breathing."

State T4: Monotone Energy

Symptoms: Everything delivered at the same intensity. Combat doesn't feel more urgent than shopping. The climactic battle has the same energy as a random encounter. Players never feel tension rising or falling.

Key Questions:

  • Does pacing vary between scenes?
  • Do high-stakes moments feel different?
  • Is there a sense of rising/falling tension?
  • Does the climax feel climactic?

Diagnostic Checklist:

  • High-stakes scenes have urgency
  • Quiet moments actually feel quiet
  • Pacing accelerates toward climaxes
  • Resolution scenes decompress

Energy Calibration by Scene Type:

Scene TypeEnergy LevelPacing
ExplorationMediumMeasured, atmospheric
Social/RPVariableResponsive to players
CombatHighFast, punchy
InvestigationLow-MediumDeliberate, building
ClimaxMaximumIntense, accelerating
DenouementLowSlow, reflective

Interventions:

  • Consciously shift energy between scene types
  • Use pacing as a tool: slow for tension, fast for action
  • Build to climaxes through escalating energy
  • Allow decompression after intense moments
  • Practice "reading the room" for when to push or pull back

State T5: Genre Mismatch

Symptoms: Tone doesn't match the game's genre expectations. Running a horror game like an action movie. Playing D&D like Call of Cthulhu. The mechanics and tone are fighting each other.

Key Questions:

  • What genre is this game supposed to be?
  • Does the tone match genre conventions?
  • Are mechanics and tone aligned?
  • Do players expect this genre's tropes?

Genre-Tone Mapping:

GenreTonal BaselineKey Elements
Heroic FantasyHopeful, adventurousGood vs. evil, triumph, wonder
GrimdarkCynical, harshMoral ambiguity, costly victories
Cosmic HorrorDread, insignificanceUnknown, madness, no true victory
Pulp AdventureExciting, lightTwo-fisted action, daring escapes
NoirCynical, atmosphericMoral compromise, femme fatales
SwashbucklingDashing, romanticWit, style over substance
Survival HorrorTense, resource-scarceVulnerability, hard choices

Interventions:

  • Identify target genre explicitly
  • Study genre conventions (films, books, other games)
  • Align NPC behavior with genre expectations
  • Match consequence weight to genre (pulp: light, grimdark: heavy)
  • Use genre-appropriate language and imagery

Establishing Baseline Tone

Before play begins, establish:

1. The Tonal Anchor

One sentence describing how this campaign should FEEL:

  • "Desperate heroes against impossible odds"
  • "Competent professionals doing morally gray work"
  • "Wide-eyed adventurers discovering wonder"
  • "Survivors barely holding on in a broken world"

2. The Humor Policy

Where does comedy fit?

  • Integrated: Comedy woven throughout naturally
  • Bracketed: Comedy in downtime, serious in action
  • Rare: Comedy as relief valve only
  • None: Straight-faced throughout

3. The Consequence Dial

How heavy are outcomes?

  • Light: Death rare, setbacks temporary
  • Medium: Real stakes, recoverable failure
  • Heavy: Consequences stick, death possible
  • Brutal: The world is not fair

4. The Wonder/Horror Ratio

What emotional notes dominate?

  • More wonder → sense of discovery, magic is amazing
  • More horror → sense of dread, the unknown is threatening
  • Balanced → both present, shifting by context

Reading the Room

Tone isn't just GM output—it's a conversation with players.

Signs Players Want Different Tone:

Player BehaviorMay Indicate
Joking during serious scenesNeed lighter tone or transition
Quiet/withdrawnScene too intense or wrong register
Checking phonesEnergy too low, pacing too slow
Interrupting descriptionsReady to act, cut the narration
Leaning in, engagedTone is working, maintain

Adjusting in Real Time:

  • If jokes derail drama → either lean into comedy or clearly signal "let's refocus"
  • If players seem lost → clarify what register you're in
  • If energy flags → accelerate pacing or shift scene
  • If tension overwhelms → provide relief valve moment

Anti-Patterns

The Shakespeare GM

Pattern: Every NPC speaks in elevated language regardless of station. Problem: Kills verisimilitude, exhausts players, blurs NPC distinction. Fix: Match NPC language to character and context. The peasant doesn't talk like the wizard.

The Edgelord

Pattern: Grimdark everything. Constant horror. No hope. Problem: Numbness. Horror needs contrast to work. Fix: Light makes shadow. Include moments of warmth, humor, hope to make the dark matter.

The Theme Park GM

Pattern: Every zone has different tone. Forest = whimsy, dungeon = horror, city = comedy. Problem: World feels like a theme park, not a place. Fix: Establish world-level baseline. Individual locations can shade it, not contradict it.

The Emotional Ambush

Pattern: Heavy emotional content without warning or consent. Problem: Players feel blindsided, not immersed. Fix: Establish content agreements. Approach heavy content with player buy-in.

The One-Note Band

Pattern: Same tone, always. Action movie pace for everything. Problem: No contrast, no breathing room, eventual exhaustion. Fix: Vary deliberately. Quiet after loud. Slow after fast.


Diagnostic Process

When a GM reports tone problems:

1. Identify the Problem Type

  • Does narration feel boring? → T1 (Flat Table)
  • Are tonal shifts jarring? → T2 (Tonal Whiplash)
  • Are descriptions overwhelming? → T3 (Purple GM)
  • Does everything feel the same? → T4 (Monotone Energy)
  • Does tone not fit the game? → T5 (Genre Mismatch)

2. Check Baseline

  • Is there an established baseline tone?
  • Is it communicated to players?
  • Is it appropriate for the game/genre?

3. Look for Pattern

  • Is the problem consistent or situational?
  • When does it break down? (combat, drama, NPCs?)
  • What's the GM's natural tendency? (too sparse, too rich?)

4. Recommend Interventions

Based on identified state, provide specific fixes.


Integration with Other Skills

Related SkillWhen to Hand Off
scene-sequencingWhen pacing issues are structural, not tonal
dialogueWhen NPC voice specifically needs work
genre-conventionsWhen genre knowledge gap is the issue
game-facilitatorWhen the issue is player management, not delivery

Prerequisites

Do NOT use table-tone when:

  • Players aren't engaged because the STORY is broken (use story-sense)
  • The issue is mechanical, not tonal
  • Player conflict is the real problem

Quick Reference: Tone Calibration

Before Session:

  • What's the baseline tone for today?
  • Any major tonal shifts planned?
  • What energy level are we starting at?

During Session:

  • Am I matching scene importance with description weight?
  • Are my transitions smooth or jarring?
  • What's the room energy? Match or shift it?

After Session:

  • Did the tone land?
  • Were there jarring moments?
  • What worked? What didn't?

Output Persistence

This skill writes primary output to files so work persists across sessions.

Output Discovery

Before doing any other work:

  1. Check for context/output-config.md in the project
  2. If found, look for this skill's entry
  3. If not found or no entry for this skill, ask the user first:

- "Where should I save output from this table-tone session?" - Suggest: explorations/table-tone/ or a sensible location for this project

  1. Store the user's preference:

- In context/output-config.md if context network exists - In .table-tone-output.md at project root otherwise

Primary Output

For this skill, persist:

  • Tone diagnosis - current state and issues identified
  • Intended tone definition - what the GM is aiming for
  • Toolkit selections - techniques and elements that reinforce tone
  • Session notes - what worked and what didn't

Conversation vs. File

Goes to FileStays in Conversation
Tone definitionDiscussion of preferences
Toolkit checklistClarifying questions
Session retrospectivesReal-time feedback
Technique recommendationsPlayer dynamic discussion

File Naming

Pattern: {campaign}-tone-{date}.md Example: dnd-campaign-tone-2025-01-15.md

What You Do NOT Do

  • You do not dictate what tone a campaign "should" be
  • You do not diagnose when the problem is player conflict
  • You do not impose your preferences over the table's
  • You do not assume one tone is better than another

Your role is diagnostic: identify tonal problems, explain why they're problems, and guide toward solutions. The GM establishes their own tone.


Key Insight

Tone is a promise. When you establish a tone, players calibrate their engagement, emotional investment, and expectations to match. Break that promise carelessly and you break immersion. Honor it and players will follow you anywhere—into comedy, tragedy, horror, or wonder.

The goal isn't "correct" tone. The goal is intentional tone—knowing what feeling you're creating and creating it on purpose.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

Claude Code

29.57%
按下载量换算550

Codex

23.88%
按下载量换算444

OpenCode

17.21%
按下载量换算320

Antigravity

11.83%
按下载量换算220

Gemini CLI

8.04%
按下载量换算150

windsurf

3.72%
按下载量换算69

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills