[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AVF1Z9FAHDN0MKFSVNDQ4R":3,"skill-same:01M7AVF1Z9FAHDN0MKFSVNDQ4R":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7AVF1Z9FAHDN0MKFSVNDQ4R","notification-routing",null,"Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding","alonf\u002FKeyContextAI","alonf","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F554150?v=4","01M7ATEPSCNKG13BVTKA74VG59","Alon Fliess","01M7ATEPSZ4YMBM9W25SKM3GES",0,"MIT","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fnotification-routing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"notification-routing\"\ndescription: \"Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding\"\ndomain: \"communication\"\nconfidence: \"high\"\nsource: \"earned\"\n---\n\n## Context\n\nWhen a Squad grows beyond a few agents, notifications flood a single channel — failure alerts drown in daily\nbriefings, tech news buries security findings, and everything gets ignored. This is the pub-sub problem:\na single message queue for everything is a recipe for missed alerts.\n\nThe fix is **topic-based routing**: agents tag notifications with a channel type, and a routing function\nsends them to the appropriate destination.\n\n**Trigger symptoms:**\n- Important alerts missed because they're buried in routine notifications\n- Team members turning off notifications entirely (signal overwhelm)\n- Onboarding friction: \"where do I look for X?\"\n\n## Patterns\n\n### Channel Config Schema\n\nDefine a `.squad\u002Fteams-channels.json` (or equivalent) mapping notification types to channel identifiers:\n\n```json\n{\n  \"teamId\": \"your-team-id\",\n  \"channels\": {\n    \"notifications\": \"squad-alerts\",\n    \"tech-news\":     \"tech-news\",\n    \"security\":      \"security-findings\",\n    \"releases\":      \"release-announcements\",\n    \"daily-digest\":  \"daily-digest\"\n  }\n}\n```\n\nPlace this in `.squad\u002F` (git-tracked, shared across the team). For platforms that use channel IDs instead of\nnames (Teams, Slack), store the resolved ID alongside the name to avoid name-collision bugs:\n\n```json\n{\n  \"channels\": {\n    \"notifications\": { \"name\": \"squad-alerts\", \"id\": \"channel-id-opaque-string\" }\n  }\n}\n```\n\n### CHANNEL: Tag Convention\n\nAgents prefix their output with `CHANNEL:\u003Ctype>` to signal where the notification should go:\n\n```\nCHANNEL:security\nWorf found 3 new CVEs in dependency scan: lodash@4.17.15, minimist@1.2.5\n```\n\n### Routing Dispatcher (shell pseudocode)\n\n```bash\ndispatch_notification() {\n  local raw_output=\"$1\"\n  local channel=\"notifications\"  # default\n\n  if echo \"$raw_output\" | grep -qE '^CHANNEL:[a-z][a-z0-9-]*'; then\n    channel=$(echo \"$raw_output\" | head -1 | cut -d: -f2)\n    raw_output=$(echo \"$raw_output\" | tail -n +2)\n  fi\n\n  send_notification --channel \"$channel\" --message \"$raw_output\"\n}\n```\n\n### Provider-Agnostic Adapter\n\nThe routing layer is provider-agnostic. Plug in your platform adapter:\n\n```\n.squad\u002Fnotify-adapter.sh   # Teams \u002F Slack \u002F Discord \u002F webhook -- swappable\n```\n\nThe routing config and CHANNEL: tags never change. Only the adapter changes per deployment.\n\n## Anti-Patterns\n\n**Never send all notification types to one channel:**\n```\nsend_notification --channel \"general\" --message \"$anything\"\n```\n\n**Never use display names as identifiers (name collision risk):**\n```\nsend_to_team --name \"Squad\" --channel \"notifications\"\n```\n\nResolve channel IDs once at setup. Use IDs at runtime.\n\n## Distributed Systems Pattern\n\nThis is **pub-sub with topic routing** -- the same principle as Kafka topics, RabbitMQ routing keys, and\nAWS SNS topic filtering. Route by type. Each consumer subscribes to the topics it cares about.","## Context\n\nWhen a Squad grows beyond a few agents, notifications flood a single channel — failure alerts drown in daily\nbriefings, tech news buries security findings, and everything gets ignored. This is the pub-sub problem:\na single message queue for everything is a recipe for missed alerts.\n\nThe fix is **topic-based routing**: agents tag notifications with a channel type, and a routing function\nsends them to the appropriate destination.\n\n**Trigger symptoms:**\n- Important alerts missed because they're buried in routine notifications\n- Team members turning off notifications entirely (signal overwhelm)\n- Onboarding friction: \"where do I look for X?\"\n\n## Patterns\n\n### Channel Config Schema\n\nDefine a `.squad\u002Fteams-channels.json` (or equivalent) mapping notification types to channel identifiers:\n\n```json\n{\n  \"teamId\": \"your-team-id\",\n  \"channels\": {\n    \"notifications\": \"squad-alerts\",\n    \"tech-news\":     \"tech-news\",\n    \"security\":      \"security-findings\",\n    \"releases\":      \"release-announcements\",\n    \"daily-digest\":  \"daily-digest\"\n  }\n}\n```\n\nPlace this in `.squad\u002F` (git-tracked, shared across the team). For platforms that use channel IDs instead of\nnames (Teams, Slack), store the resolved ID alongside the name to avoid name-collision bugs:\n\n```json\n{\n  \"channels\": {\n    \"notifications\": { \"name\": \"squad-alerts\", \"id\": \"channel-id-opaque-string\" }\n  }\n}\n```\n\n### CHANNEL: Tag Convention\n\nAgents prefix their output with `CHANNEL:\u003Ctype>` to signal where the notification should go:\n\n```\nCHANNEL:security\nWorf found 3 new CVEs in dependency scan: lodash@4.17.15, minimist@1.2.5\n```\n\n### Routing Dispatcher (shell pseudocode)\n\n```bash\ndispatch_notification() {\n  local raw_output=\"$1\"\n  local channel=\"notifications\"  # default\n\n  if echo \"$raw_output\" | grep -qE '^CHANNEL:[a-z][a-z0-9-]*'; then\n    channel=$(echo \"$raw_output\" | head -1 | cut -d: -f2)\n    raw_output=$(echo \"$raw_output\" | tail -n +2)\n  fi\n\n  send_notification --channel \"$channel\" --message \"$raw_output\"\n}\n```\n\n### Provider-Agnostic Adapter\n\nThe routing layer is provider-agnostic. Plug in your platform adapter:\n\n```\n.squad\u002Fnotify-adapter.sh   # Teams \u002F Slack \u002F Discord \u002F webhook -- swappable\n```\n\nThe routing config and CHANNEL: tags never change. Only the adapter changes per deployment.\n\n## Anti-Patterns\n\n**Never send all notification types to one channel:**\n```\nsend_notification --channel \"general\" --message \"$anything\"\n```\n\n**Never use display names as identifiers (name collision risk):**\n```\nsend_to_team --name \"Squad\" --channel \"notifications\"\n```\n\nResolve channel IDs once at setup. Use IDs at runtime.\n\n## Distributed Systems Pattern\n\nThis is **pub-sub with topic routing** -- the same principle as Kafka topics, RabbitMQ routing keys, and\nAWS SNS topic filtering. Route by type. Each consumer subscribes to the topics it cares about.",{"name":5,"domain":24,"source":25,"confidence":26,"description":7},"communication","earned","high","main","176da577bfd98859f793bdd1312690c6c3940c67",".squad\u002Ftemplates\u002Fskills\u002Fnotification-routing","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI","https:\u002F\u002Fgithub.com\u002Falonf","http:\u002F\u002Falonfliess.me","CTO & Founder of Zionet.\r\nMicrosoft Regional Director and Foundry MVP.\r\n","2026-08-28 05:21:35",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add alonf\u002FKeyContextAI --skill notification-routing",{"tool":41,"command":42},"bunx","bunx skills add alonf\u002FKeyContextAI --skill notification-routing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add alonf\u002FKeyContextAI --skill notification-routing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fnotification-routing\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7AVHRWWXA0BQ5PXNA8FG30W","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7AVHABPRYXYM3GWJY1RW92A","versioning-policy","Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7AVH4KNP3TCVQDRVS70VP19","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7AVH18JDSA55Z7KK2GH6X49","test-discipline","Update tests when changing APIs — no exceptions","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftest-discipline\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7AVGVGWYD7NBNXAV4PAZJ92","squad","Squad's command catalog and interactive menu. Invoke via \u002Fsquad (slash command) or natural language (\"squad commands\", \"what can squad do\", \"show me squad options\"). Presents categorized operations (Install & Upgrade, Team Management, Issues & PRs, Plugins & Skills, Model & Cost, Sessions & State) as an interactive picker. Routes to the right squad CLI command or the Squad coordinator agent.","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fsquad\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AVGPSFT1WHW3PK35DHS5XK","squad-version-check","Internals of how @bradygaster\u002Fsquad-cli stamps its version, how `squad upgrade` works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.","https:\u002F\u002Fgithub.com\u002Falonf\u002FKeyContextAI\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fsquad-version-check\u002FSKILL.md",[],[]]