Simple Man

High-compression professional communication mode. Use when the user wants fewer tokens, less reading, no filler, compact coding-agent status, terse technical answers, or low-cognitive-load collaboration without reducing effort, validation, proactivity, or accuracy. Do not use when the user asks for a tutorial, teaching explanation, detailed report, design document, or other long-form writing whose purpose is thoroughness.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Maksim-Burtsev/simple-man --skill simple-man
Manual install
git clone --depth 1 https://github.com/Maksim-Burtsev/simple-man.git /tmp/simple-man
mkdir -p ~/.claude/skills
cp -r /tmp/simple-man/skills/simple-man ~/.claude/skills/simple-man

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Simple Man

Goal: minimum user-facing words; same work quality.

Same work quality means no reduction in repo search, usage search, dependency tracing, impact analysis, validation, tests, lint, typecheck, or reported findings. That list is the test: if any of it shrank, the compression was wrong.

Core rule: preserve the user's next decision. Compress water, not work.

## Decide the mode first

A requested shape is a contract: exact counts of items, sections, paragraphs or words, a given order, a required example or code block. Meet it exactly, keep the order given, and check the answer against it before sending. Never re-sort items the user ordered.

Write a requested tutorial, teaching explanation, detailed report or long-form prose in full. Compress your own narration around the artifact, never the artifact itself.

Everything else gets the compact mode below.

## Output

- Answer first. Add only what changes the user's next decision or trust.
- Delete water only: preamble, praise, recap, filler, outro, generic reassurance, restating the question, repeated context, duplicate reasons, hedging without decision value, and generic next steps.
- Short — unless brevity hides order, condition, approval, validation, risk or meaning. Then expand until clear, and compress again.
- Use fragments, labels, colons, direct nouns/verbs, exact code and exact commands.
- Answer yes/no/status directly and only the asked thing.
- Neutral professional tone; brevity is not curtness.
Read the full skill on GitHub

Details

Skill name
simple-man
Path
skills/simple-man/SKILL.md
License
MIT
Repo updated
1 October 2026

FAQ

What does the Simple Man skill do?

High-compression professional communication mode. Use when the user wants fewer tokens, less reading, no filler, compact coding-agent status, terse technical answers, or low-cognitive-load collaboration without reducing effort, validation, proactivity, or accuracy. Do not use when the user asks for a tutorial, teaching explanation, detailed report, design document, or other long-form writing whose purpose is thoroughness.

How do I install the Simple Man skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Maksim-Burtsev/simple-man --skill simple-man. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Simple Man popular?

It lives in Maksim-Burtsev/simple-man, which has 12 GitHub stars and 0 forks, and is included in 2 curated skill lists.

Related skills

SEO Geo Blog Writer

16

weipanux/seo-geo-blog-writer

Create blog posts optimized for traditional search engines (SEO) and generative AI citations (GEO). Supports two modes - keyword-driven (user provides target keyword) or topic expansion (automated keyword research). Complete workflow from keyword research through schema markup generation.

Writing & Content

Novel Deconstruct

17

QQ-L-XX/novel-deconstruct

拆书——对网络小说进行深度结构分析。输入番茄小说等平台的链接,自动抓取、解码、分析,输出七步骨架/冲突三层/人物弧光/对话技法/节奏控制等维度的拆书报告。触发词:拆书、拆解、分析这本小说、帮我看看这本书。

Writing & Content

Chinese Grammar Proofreader

19

orange4664/chinese-grammar-proofreader

纯中文病句辨析与修改 Skill。严格面向现代汉语句法、语义、逻辑和标点规范, 检查成分残缺或赘余、搭配不当、语序不当、结构混乱/句式杂糅、指代不明、 歧义、不合逻辑、关联词错误、两面对一面、否定失当、数量范围和标点问题。 适用于“找语病”“检查病句”“辨析并修改病句”“按高考语文标准检查” “这句话有没有问题”等任务。默认只纠正明确问题,采用最小修改,不做泛润色、 风格改写、段落美化或事实核查。段落和长文必须逐句通读、逐句诊断, 不允许粗略扫读或只挑可疑句。

Writing & Content

Magicmd

18

didilili/MagicMD

Use when the user wants public article URLs from WeChat, Juejin, CSDN, or technical blogs converted into Markdown packages, including batch conversion, local media, metadata, and extraction reports.

Writing & Content

Grok Skill

17

mikedemarais/grok-skill

Search and analyze X (Twitter) using xAI Grok 4 via OpenRouter with Live Search. Trigger on prompts that explicitly or implicitly ask to "search Twitter/X", "what's trending", "tweets from @handle", "hashtag #…", "what are people saying", or that require tweet-level activity/engagement from X.

Writing & Content

Diataxis Docs Framework

18

anivar/developer-docs-framework

Enterprise technical documentation best practices, patterns, and frameworks for developer and partner adoption. Covers content architecture (Diataxis four quadrants), 14 content types (tutorials, how-to guides, API reference, SDK docs, migration guides, changelogs, runbooks, integration guides, troubleshooting, architecture docs), pluggable writing styles (Diataxis, Google, Microsoft, Stripe, Canonical, Minimal), information architecture, docs-as-code workflows, documentation audit, anti-patterns checklist, and developer experience (DX) strategy. 27 rules, 5 references, 6 style guides. Baselin

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.