Sending notifications to your users' own channels: the notification as a routed artefact rather than an email, channel selection and the fan-out across email, push, in-app and SMS, delivery receipts and the retry paths that differ per channel, quiet hours and user preference as routing inputs, templates with per-channel context, digest and batch policies that respect attention, and the written notification record. It explains how a notification platform behaves; it never recommends a vendor and never decides how often to interrupt a user. Use when asking "notification system", "push notification", "in-app notification", "fan out", "notification preferences", "quiet hours", "digest", "read receipts", "cross-channel notification", "why did users turn off notifications". Not for mobile push implementation on one platform (ac-mobile-client-engineering), not for webhook delivery to endpoints you do not own (ac-webhook-and-async-delivery), not for email deliverability mechanics (ac-email-deliverability).
cp -r cryptoskill/skills/exchanges/anoscranel-ac-notification-systems .claude/skills/clawhub install anoscranel-ac-notification-systemsCapabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.
read_only Phase 1 single-mode classification — multi-mode breakdown deferred to Phase 2.
We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.
No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →
SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →
Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed