Communication
38 portable Agent Skills for disciplined, reviewable AI-assisted work across Codex, Claude Code, GitHub Copilot, and compatible agents.
npx -y skills add nevitonsantana/adaptive-skills --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.
- 1 stars1 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
Explain changes, failures, options, and handoffs with clarity, evidence, and low noise.
SKILL.md
1.7 KB, as published. Nobody here has run it
Overview
Use this skill when technical work needs to be made legible for humans or for another agent.
When to Use
- status updates
- handoffs
- decision framing
- failure reporting
When NOT to Use
- to replace proof with storytelling
- to bury uncertainty under long prose
Core Moves
- Lead with the main point.
- Separate fact from interpretation when needed.
- Name impact and trade-offs briefly.
- Close with the next step or decision needed.
Optional Modules
- Decision frame — Add options, trade-offs, and a recommendation when a choice is needed.
- Failure report — Describe symptom, likely cause, and blocker shape.
- Handoff packet — Summarize boundary, ownership, and expected continuation.
Activation Triggers
- Use decision frame when multiple options remain.
- Use failure report when progress is blocked or risky.
- Use handoff packet when another owner must continue the work.
Expected Output
- clear status or decision note
- explicit trade-off or blocker
- next step
Verification
- A reader can understand the point in one pass.
- Evidence and recommendation are not blurred together.
- The next action is explicit.
Handoff Signals
- The note is primarily for another owner to continue the work.
- The change crosses team or specialty boundaries.
Pairs Well With
workflowfeature-planningapi-design
Anti-patterns
- Writing chronologically instead of by importance.
- Using vague words instead of naming the decision.
- Reporting work without saying what should happen next.