agentleFS
Sign inStart free
bks-labbks-lab/open-bridge/skills/channel/SKILL.md

channel

Skill13 starsChanged 13 days agoMITView on GitHub

Messaging channel management: health checks, deployments, start/stop services. Reads infra/channels/*.yaml. Not for timed sends (→ /schedule) or runs on a machine (→ /workload). Trigger: "/channel", "channel status", "channel health", "channel deploy", "start channel", "stop channel".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the user asks about a scheduled message ("compliment for Mom", "weekly-digest", its send time) route to /schedule.

    line 27

≈ “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

Channel

Manage messaging channels (imessage, email, telegram, whatsapp, signal, teams) and their runtime services. Read the referenced file ONLY when triggered.

Scope boundary

ConcernOwner
Channel inventory, health, deploy, start/stopThis skill
Scheduled messages in infra/channels/_scheduled.yaml/schedule skill
Any other cron/launchd/systemd job on a machine/workload skill
Recipient groups for those messages/mandants skill

When the user asks about a scheduled message ("compliment for Mom", "weekly-digest", its send time) route to /schedule. A job that is not a message (a poller, a nightly sync, a daemon, "is the job still there") is a workload: route to /workload, which declares it in workflow/workloads/ and reads its state from the live service manager. Channel management is the transport layer; scheduling is a separate concern.

Arguments

ArgumentEffectDefault
(none)Channel overview—
{name}Detail view of one channel—
healthHealth check all channels—
deploy {name}Deploy channel service—
start/stop/restart {name}Service control—

Decision Tree

User wants to...
├── Channel overview / status          → Read references/workflow.md (§ Overview)
├── Channel health check               → Read references/workflow.md (§ Health Check)
├── Start/stop a channel               → Read references/workflow.md (§ Start/Stop)
├── Deploy channel services            → Read references/workflow.md (§ Deploy)
├── Scheduled messages                 → Delegate to `/schedule` skill
├── Cron/launchd/systemd jobs          → Delegate to `/workload` skill
├── Recipient group management         → Delegate to `/mandants` skill
└── Questions about channels           → Answer from this file

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.

Check your setup, free