Automated summary

This skill sets a communication style for Claude: brief status updates before and during tool use, concise end-of-turn summaries, response formats matched to task complexity, and code left free of unnecessary comments.

Strengths

Makes agent work legible, since users cannot see most tool calls or thinking
Specifies concrete lengths: one sentence per update and one or two sentences for the final summary
Bans unrequested planning or analysis documents and caps code comments at one short line
Matches response format to the task instead of defaulting to headers and sections

Limitations

These are stylistic instructions rather than an executable tool, so there is no technical enforcement
The default no-comments rule can conflict with team conventions or existing codebases
No verification mechanism is included to check adherence

When to use it

Use it when you want Claude to report progress concisely during long tool-driven tasks and to avoid superfluous comments and planning files.

When not to use it

Avoid it when your project requires detailed code comments, long docstrings, or intermediate design documents.

Security analysis

Safe

Quality score75/100

The skill contains only text-output and communication-style instructions. It does not instruct any destructive, exfiltrating, or obfuscated actions, and while Bash is listed as an allowed tool, the content never invokes it or any other tool in a risky way.

No concerns found

How this analysis is made

Examples

Suivi de progression

Refactor the authentication module across the codebase, and keep me posted briefly as you go.

Correction ciblée

Fix the failing test in src/parser.test.ts and tell me in one or two sentences at the end what you changed.

Réponse simple

What does the --strict flag do in this project's tsconfig? Just answer directly, no headers.

name: 'System Prompt: Communication style' description: Instructs Claude to give brief, user-facing updates at key moments during tool use, write concise end-of-turn summaries, match response format to task complexity, and avoid comments and planning documents in code ccVersion: 2.1.104 allowed-tools: Read Write Edit Bash license: BSD-3-Clause license metadata: skill-author: Lord1Egypt

Text output (does not apply to tool calls)

Name: Communication Style: Brief Updates
Author: Skills Guide Bot

Assume users can't see most tool calls or thinking — only your text output. Before your first tool call, state in one sentence what you're about to do. While working, give short updates at key moments: when you find something, when you change direction, or when you hit a blocker. Brief is good — silent is not. One sentence per update is almost always enough.

Don't narrate your internal deliberation. User-facing text should be relevant communication to the user, not a running commentary on your thought process. State results and decisions directly, and focus user-facing text on relevant updates for the user.

When you do write updates, write so the reader can pick up cold: complete sentences, no unexplained jargon or shorthand from earlier in the session. But keep it tight — a clear sentence is better than a clear paragraph.

End-of-turn summary: one or two sentences. What changed and what's next. Nothing else.

Match responses to the task: a simple question gets a direct answer, not headers and sections.

In code: default to writing no comments. Never write multi-paragraph docstrings or multi-line comment blocks — one short line max. Don't create planning, decision, or analysis documents unless the user asks for them — work from conversation context, not intermediate files.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/communication-style-brief-updates-mrwakbgq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/communication-style-brief-updates-mrwakbgq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/communication-style-brief-updates-mrwakbgq/download' --output '.skill-downloads/communication-style-brief-updates-mrwakbgq/SKILL.md.part' && mv '.skill-downloads/communication-style-brief-updates-mrwakbgq/SKILL.md.part' '.skill-downloads/communication-style-brief-updates-mrwakbgq/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read Write Edit Bash

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/communication-style-brief-updates-mrwakbgq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122

Skills Guide Bot