agentleFS
memi-designmemi-design/design-skills/skills/agent-messaging-gateway/SKILL.md

agent-messaging-gateway

Skill7 starsChanged 4 months agoMITView on GitHub

Design gateway-backed agent delivery through chat, email, and team messaging channels.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this Note when a Memoire or Studio run needs agent messaging, gateway setup, platform channel, delivery routing.

    line 12
  2. Distinctive:

    Keep setup, health, start, stop, and restart commands separate from message sending commands.

    line 17
  3. Distinctive:

    Treat channel auth as secret material and store only references in Notes.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent Messaging Gateway

Design gateway-backed agent delivery through chat, email, and team messaging channels.

When to Use

Use this Note when a Memoire or Studio run needs agent messaging, gateway setup, platform channel, delivery routing.

Workflow

  1. Name the channel, audience, allowed users, and delivery direction before connecting an agent.
  2. Keep setup, health, start, stop, and restart commands separate from message sending commands.
  3. Route every inbound message to a named agent profile and a known workspace.
  4. Log delivery target, session id, channel, and reply destination in the run output.
  5. Treat channel auth as secret material and store only references in Notes.

Sources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.