Independent reviews. IonBin has no partnerships with the tools on this page and was not paid for these listings. Our evaluations are our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Source reviewedWriting & commsExplored

Anthropic / skills/internal-comms/SKILL.md

Internal Comms

A small router that picks a format guide for status reports, newsletters, FAQs and other internal updates.

Read upstream skill GitHub repository Add to comparison

Source reviewed · reviewed · Named sources were inspected. No runtime results are established by this label.

01 / Task fit

Where it may help.

These are intended uses indicated by the upstream material. They are not measured outcomes.

  • Recurring internal updates that should follow one structure
  • Teams willing to adapt the bundled format guides

What it is

Internal Comms gives an agent a short list of internal message types and points it to a separate guide file for each one, such as Progress/Plans/Problems updates, company newsletters and FAQ answers. The SKILL.md itself is brief. The useful detail sits in the example guides, which IonBin did not review.

Why you might use it

Use it when you write the same kinds of internal updates often and want a consistent structure. It's most useful once you replace or edit the example guides to match how your own team writes. If a request doesn't fit any guide, the skill tells the agent to ask instead of guessing.

Put it in context.

Illustrative requests and outputs to review. These examples are separate from the recorded evaluation below.

Draft a weekly team update

Example request

Turn these bullet notes into a Progress, Plans and Problems update for the ops team. Keep it under 200 words and flag anything that needs a decision.

What to look for. A short update in three sections, with open decisions listed separately.

Before you rely on it. The facts come from your notes. Check names, dates and numbers before you send it.

Answer a repeated staff question

Example request

Write an FAQ answer about the new expense deadline using only the policy text I paste below.

What to look for. A short answer that sticks to the pasted policy.

Before you rely on it. If the policy text is out of date, the answer will be too. Keep the policy owner in the loop.

02 / Setup & access

What it asks of your environment.

Requirements

  • An agent that can load the skill folder, including its examples/ guide files.
  • No account or script is needed. Source material for the update comes from you.

Permissions & data access

  • Reads the bundled guide files and whatever notes or documents you provide.
  • Writes draft text only; sending or posting is a separate step you control.
Check the host, too.

Instructions alone do not enforce a sandbox. The agent host, connected tools and approvals determine what the skill can actually read, change or send.

03 / Things to check

Security concerns & practical limits.

These concerns follow from the reviewed sources. They describe possible exposure or required review; they are not confirmed vulnerabilities.

Review before use

The format guides are examples, not your house style

The entrypoint defers formatting and tone to bundled example guides. Review and edit those guides before relying on them, or the drafts will follow someone else's conventions.

Limits and nuances

  • Source review of SKILL.md and the per-skill license only. The four example guide files were not reviewed, and no draft was generated or judged.
  • No writing-quality, tone or accuracy result is claimed.

04 / Review record

What we checked. What’s still open.

Source reviewed

Recorded review scope

  • skills/internal-comms/SKILL.md
  • skills/internal-comms/LICENSE.txt
Not verified

Not tested or established

  • Source review of SKILL.md and the per-skill license only. The four example guide files were not reviewed, and no draft was generated or judged.
  • No writing-quality, tone or accuracy result is claimed.
Review date
Source revision
dbd4588f9e1033efb41dad4bef2f7947c8993d44
Our relationship
Explored. Investigated through the recorded review. No use or replication is claimed.

Upstream content can change after review. A repository revision identifies source scope; it does not prove that every script, dependency or runtime behavior was tested. How freshness is handled.

Recorded evaluation / Source review

Results with their limits attached.

Completed within scope

Completed 4 bounded source checks on the pinned entrypoint and license. No skill workflow was executed.

Passed
4
Failed
0
Total recorded
4

These counts refer to the cases in this report. They are not a benchmark against other skills. A source review does not establish runtime behavior.

Read the evidence report

The report provides the case definitions, observations and baseline scope. Missing baselines or untested behaviors remain limitations.

Recorded environment

  • Pinned public UTF-8 sources fetched from raw.githubusercontent.com at the recorded commit and hashed with SHA-256.
  • Linux; Python 3.13.5 source-condition check. No account, credentials, private documents or live business data.
Recorded commands (2)

Commands document this evaluation. They are not setup instructions for your environment.

Read each pinned file listed in sourceManifest.
python3 r6_skills.py: check each recorded source condition and reconcile report counts.

Findings from this evaluation

Needs attention

The format guides are examples, not your house style

The entrypoint defers formatting and tone to bundled example guides. Review and edit those guides before relying on them, or the drafts will follow someone else's conventions.

Observation

Asks rather than guesses on unknown formats

The entrypoint tells the agent to ask for clarification when a request matches none of the guides.

Evaluation limitations

  • Source review of SKILL.md and the per-skill license only. The four example guide files were not reviewed, and no draft was generated or judged.
  • No writing-quality, tone or accuracy result is claimed.

05 / Reuse & discovery

License, attribution & popularity.

Apache-2.0

Apache-2.0 license text inspected at this revision. Keep the license and any NOTICE when redistributing covered files. The services and accounts the skill uses have their own terms.

Why it is in this collection

GitHub displayed 182,047 stars for the anthropics/skills repository on the observation date. Repository-wide; not individual skill usage, quality or safety.

182,047 repository stars

Scope
Entire anthropics/skills repository, not this individual skill
Observed
Time window
Snapshot observed 2026-10-19
Discovery source ↗

Popularity and inclusion do not establish quality, compatibility or security. Counts belong to their named metric and date; they are not a current ranking.

06 / Follow the evidence

Go to the original.

  1. Pinned skill instructions github.com
  2. Pinned license github.com
  3. Repository (dated star count) github.com

IonBin’s source notes are independent assessments. Upstream authors retain their work and attribution. This page does not install or execute the skill.