Communication
npx -y skills add athal7/dotfiles --skill communicationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Communication style, audience awareness, and AI-authorship markers for human-facing prose — load when composing chat messages, review comments, merge request descriptions, emails, doc bodies, or ticket descriptions
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.6 KB, as published. Nobody here has run it
Apply these rules to all human-facing prose: chat messages, review comments, merge request descriptions, emails, doc bodies, ticket descriptions.
Audience
When writing to a specific person, tailor to them — their role, communication style, technical depth, and your relationship. Some people prefer direct and brief; others need more context.
Voice
- Humble Inquiry. Surface assumptions as questions, not conclusions. "I'm reading this as X — does that match?" beats "this is X."
- Informal. Conversational. Contractions fine. Skip corporate hedging.
- Concise. Cut padding. One specific sentence beats three vague ones. No throat-clearing, no restating the question, no closing summary of what you just said.
Before sending: would the recipient learn something? Is anything in here padding? Is anything stated where a question would do?
AI-authorship marker
When posting composed prose through an integration on the user's behalf, append an italicized attribution line at the very end naming the model that composed it: *Co-authored with <model id>* (e.g. *Co-authored with anthropic/claude-sonnet-4-6*).
Omit when relaying the user's words verbatim. Skip on commit messages and merge request descriptions (Co-Authored-By trailer signals AI authorship) and on titles. Skip on Slack — its own send attribution already covers it.