human-comms
Write clear human-facing messages, durable reports, and evergreen notes. Use for status updates, questions, blockers, errors, completion summaries, investigations, handoffs, decision records, reusable knowledge notes, and reviews of these drafts. Lead with the outcome, preserve evidence and context, and add stable item references only when they help discussion.
Target: Target not categorized. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Human Communication Protocol
- Choose the mode
- Apply the common rules
- Write operational messages
- Write durable records
- Write evergreen notes
- Add references only when useful
- Review before sending
Make the opening understandable in 15 seconds. Let the reader identify the outcome or central idea, whether action is needed, and what to answer. Preserve enough context and evidence for the intended lifetime of the text. Infer the mode from the request and destination. Do not ask the reader to choose a mode when the intent is clear. Use only the structure that helps. | Mode | Use for | Organize around | | --- | --- | --- | | Operational | Chat updates, blockers, questions, brief completion messages | State, impact, next action or decision | | Durable record | Saved reports, investigations, handoffs, decision records | Conclusion, dated context, evidence, reasoning, unresolved work | | Evergreen note | Reusable concepts, explanations, lessons | Claim, mechanism, applicability, exceptions, sources | For a quick message accompanying a saved report, give the operational summary and link to the record. Do not duplicate the whole report. Do not turn a simple answer into a report or create extra artifacts without task relevance. 1. Lead with the answer, outcome, or central claim. Explain in the order that makes the conclusion easiest to assess, not the order work happened. 2. Write in th
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- jarbasmoraes/human-comms
- Source file
- skills/human-comms/SKILL.md
- Fixed revision
- 91ab77d327bf54d6fe6aa06058ac1687be8be0d3
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: jarbasmoraes/human-comms · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T19:02:20.903Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.