Agent Skills › tzachbon/smart-ralph › communication-style

communication-style

GitHub

指导Ralph智能体生成规范文档及输出时，采用极致简洁、易扫描的格式。要求牺牲语法换取精简，优先使用片段、表格和列表，结构遵循概述、内容、疑问、行动步骤顺序，以提升效率和降低Token成本。

plugins/ralph-specum/skills/communication-style/SKILL.md tzachbon/smart-ralph

Trigger Scenarios

生成spec artifacts（research.md等）格式化agent输出结构化阶段结果需要简洁可读的输出指南

Install

npx skills add tzachbon/smart-ralph --skill communication-style -g -y

More Options

Non-standard path

npx skills add https://github.com/tzachbon/smart-ralph/tree/main/plugins/ralph-specum/skills/communication-style -g -y

Use without installing

npx skills use tzachbon/smart-ralph@communication-style

指定 Agent (Claude Code)

npx skills add tzachbon/smart-ralph --skill communication-style -a claude-code -g -y

安装 repo 全部 skill

npx skills add tzachbon/smart-ralph --all -g -y

预览 repo 内 skill

npx skills add tzachbon/smart-ralph --list

SKILL.md

Frontmatter

{
    "name": "communication-style",
    "version": "0.2.0",
    "description": "This skill should be used when generating spec artifacts (research.md, requirements.md, design.md, tasks.md), formatting agent output, structuring phase results, or when any Ralph agent needs guidance on concise, scannable output formatting. Applies to all Ralph spec phase agents.",
    "user-invocable": false
}

Communication Style

Be extremely concise. Sacrifice grammar for concision.

Rationale

Plans should not be novels
Terminal reads bottom-up
Scanning beats reading
Fewer tokens = faster, cheaper

Output Rules

1. Brevity First

Instead of	Write
"The user will be able to..."	"User can..."
"This component is responsible for..."	"Handles..."
"In order to achieve this, we need to..."	"Requires:"
"It should be noted that..."	(delete)

Use:

Fragments over full sentences
Tables over paragraphs
Bullets over prose
Diagrams over descriptions

2. Structure for Scanning

Every output follows this order:

1. Brief overview (2-3 sentences MAX)
2. Main content (tables, bullets, diagrams)
3. Unresolved questions (if any)
4. Numbered action steps (ALWAYS LAST)

3. End with Action Steps

Action steps appear last because terminal output is read bottom-up -- the most important content occupies the most visible position.

## Next Steps

1. Create auth module at src/auth/
2. Add JWT dependency
3. Implement login endpoint
4. Add tests

4. Surface Questions Early

Before action steps, list unresolved questions:

## Unresolved Questions

- OAuth provider preference? (Google, GitHub, both)
- Session duration requirement?
- Rate limiting needed?

Catches ambiguities before they become bugs.

Anti-Patterns

Don't	Do
Long prose explanations	Bullet points
Nested sub-bullets (3+ levels)	Flat structure, tables
"Let me explain..."	(just explain)
Repeating context	Reference by ID
Hedging language	Direct statements