[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M730X7XEM4NXNEA4MP7H3PXY":3,"skill-same:01M730X7XEM4NXNEA4MP7H3PXY":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M730X7XEM4NXNEA4MP7H3PXY","unified-notifications-ops",null,"Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002Fskills\u002Funified-notifications-ops\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: unified-notifications-ops\ndescription: Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.\norigin: ECC\n---\n\n# Unified Notifications Ops\n\nUse this skill when the real problem is not a missing ping. The real problem is a fragmented notification system.\n\nThe job is to turn scattered events into one operator surface with:\n- clear severity\n- clear ownership\n- clear routing\n- clear follow-up action\n\n## When to Use\n\n- the user wants a unified notification lane across GitHub, Linear, local hooks, desktop alerts, chat, or email\n- CI failures, review requests, issue updates, and operator events are arriving in disconnected places\n- the current setup creates noise instead of action\n- the user wants to consolidate overlapping notification branches or backlog proposals into one ECC-native lane\n- the workspace already has hooks, MCPs, or connected tools, but no coherent notification policy\n\n## Preferred Surface\n\nStart from what already exists:\n- GitHub issues, PRs, reviews, comments, and CI\n- Linear issue\u002Fproject movement\n- local hook events and session lifecycle signals\n- desktop notification primitives\n- connected email\u002Fchat surfaces when they actually exist\n\nPrefer ECC-native orchestration over telling the user to adopt a separate notification product.\n\n## Non-Negotiable Rules\n\n- never expose tokens, secrets, webhook secrets, or internal identifiers\n- separate:\n  - event source\n  - severity\n  - routing channel\n  - operator action\n- default to digest-first when interruption cost is unclear\n- do not fan out every event to every channel\n- if the real fix is better issue triage, hook policy, or project flow, say so explicitly\n\n## Event Pipeline\n\nTreat the lane as:\n\n1. **Capture** the event\n2. **Classify** urgency and owner\n3. **Route** to the correct channel\n4. **Collapse** duplicates and low-signal churn\n5. **Attach** the next operator action\n\nThe goal is fewer, better notifications.\n\n## Default Severity Model\n\n| Class | Examples | Default handling |\n| --- | --- | --- |\n| Critical | broken default-branch CI, security issue, blocked release, failed deploy | interrupt now |\n| High | review requested, failing PR, owner-blocking handoff | same-day alert |\n| Medium | issue state changes, notable comments, backlog movement | digest or queue |\n| Low | repeat successes, routine churn, redundant lifecycle markers | suppress or fold |\n\nIf the workspace has no severity model, build one before proposing automation.\n\n## Workflow\n\n### 1. Inventory the current surface\n\nList:\n- event sources\n- current channels\n- existing hooks\u002Fscripts that emit alerts\n- duplicate paths for the same event\n- silent failure cases where important things are not being surfaced\n\nCall out what ECC already owns.\n\n### 2. Decide what deserves interruption\n\nFor each event family, answer:\n- who needs to know?\n- how fast do they need to know?\n- should this interrupt, batch, or just log?\n\nUse these defaults:\n- interrupt for release, CI, security, and owner-blocking events\n- digest for medium-signal updates\n- log-only for telemetry and low-signal lifecycle markers\n\n### 3. Collapse duplicates before adding channels\n\nLook for:\n- the same PR event appearing in GitHub, Linear, and local logs\n- repeated hook notifications for the same failure\n- comments or status churn that should be summarized instead of forwarded raw\n- channels that duplicate each other without adding a better action path\n\nPrefer:\n- one canonical summary\n- one owner\n- one primary channel\n- one fallback path\n\n### 4. Design the ECC-native workflow\n\nFor each real notification need, define:\n- **source**\n- **gate**\n- **shape**: immediate alert, digest, queue, or dashboard-only\n- **channel**\n- **action**\n\nIf ECC already has the primitive, prefer:\n- a skill for operator triage\n- a hook for automatic emission\u002Fenforcement\n- an agent for delegated classification\n- an MCP\u002Fconnector only when a real bridge is missing\n\n### 5. Return an action-biased design\n\nEnd with:\n- what to keep\n- what to suppress\n- what to merge\n- what ECC should wrap next\n\n## Output Format\n\n```text\nCURRENT SURFACE\n- sources\n- channels\n- duplicates\n- gaps\n\nEVENT MODEL\n- critical\n- high\n- medium\n- low\n\nROUTING PLAN\n- source -> channel\n- why\n- operator owner\n\nCONSOLIDATION\n- suppress\n- merge\n- canonical summaries\n\nNEXT ECC MOVE\n- skill \u002F hook \u002F agent \u002F MCP\n- exact workflow to build next\n```\n\n## Recommendation Rules\n\n- prefer one strong lane over many weak ones\n- prefer digests for medium and low-signal updates\n- prefer hooks when the signal should emit automatically\n- prefer operator skills when the work is triage, routing, and review-first decision-making\n- prefer `project-flow-ops` when the root cause is backlog \u002F PR coordination rather than alerts\n- prefer `workspace-surface-audit` when the user first needs a source inventory\n- if desktop notifications are enough, do not invent an unnecessary external bridge\n\n## Good Use Cases\n\n- \"We have GitHub, Linear, and local hook alerts, but no single operator flow\"\n- \"Our CI failures are noisy and people ignore them\"\n- \"I want one notification policy across Claude, OpenCode, and Codex surfaces\"\n- \"Figure out what should interrupt versus land in a digest\"\n- \"Collapse overlapping notification PR ideas into one canonical ECC lane\"\n\n## Related Skills\n\n- `workspace-surface-audit`\n- `project-flow-ops`\n- `github-ops`\n- `knowledge-ops`\n- `customer-billing-ops` when the notification pain is billing\u002Fcustomer operations rather than engineering\n","# Unified Notifications Ops\n\nUse this skill when the real problem is not a missing ping. The real problem is a fragmented notification system.\n\nThe job is to turn scattered events into one operator surface with:\n- clear severity\n- clear ownership\n- clear routing\n- clear follow-up action\n\n## When to Use\n\n- the user wants a unified notification lane across GitHub, Linear, local hooks, desktop alerts, chat, or email\n- CI failures, review requests, issue updates, and operator events are arriving in disconnected places\n- the current setup creates noise instead of action\n- the user wants to consolidate overlapping notification branches or backlog proposals into one ECC-native lane\n- the workspace already has hooks, MCPs, or connected tools, but no coherent notification policy\n\n## Preferred Surface\n\nStart from what already exists:\n- GitHub issues, PRs, reviews, comments, and CI\n- Linear issue\u002Fproject movement\n- local hook events and session lifecycle signals\n- desktop notification primitives\n- connected email\u002Fchat surfaces when they actually exist\n\nPrefer ECC-native orchestration over telling the user to adopt a separate notification product.\n\n## Non-Negotiable Rules\n\n- never expose tokens, secrets, webhook secrets, or internal identifiers\n- separate:\n  - event source\n  - severity\n  - routing channel\n  - operator action\n- default to digest-first when interruption cost is unclear\n- do not fan out every event to every channel\n- if the real fix is better issue triage, hook policy, or project flow, say so explicitly\n\n## Event Pipeline\n\nTreat the lane as:\n\n1. **Capture** the event\n2. **Classify** urgency and owner\n3. **Route** to the correct channel\n4. **Collapse** duplicates and low-signal churn\n5. **Attach** the next operator action\n\nThe goal is fewer, better notifications.\n\n## Default Severity Model\n\n| Class | Examples | Default handling |\n| --- | --- | --- |\n| Critical | broken default-branch CI, security issue, blocked release, failed deploy | interrupt now |\n| High | review requested, failing PR, owner-blocking handoff | same-day alert |\n| Medium | issue state changes, notable comments, backlog movement | digest or queue |\n| Low | repeat successes, routine churn, redundant lifecycle markers | suppress or fold |\n\nIf the workspace has no severity model, build one before proposing automation.\n\n## Workflow\n\n### 1. Inventory the current surface\n\nList:\n- event sources\n- current channels\n- existing hooks\u002Fscripts that emit alerts\n- duplicate paths for the same event\n- silent failure cases where important things are not being surfaced\n\nCall out what ECC already owns.\n\n### 2. Decide what deserves interruption\n\nFor each event family, answer:\n- who needs to know?\n- how fast do they need to know?\n- should this interrupt, batch, or just log?\n\nUse these defaults:\n- interrupt for release, CI, security, and owner-blocking events\n- digest for medium-signal updates\n- log-only for telemetry and low-signal lifecycle markers\n\n### 3. Collapse duplicates before adding channels\n\nLook for:\n- the same PR event appearing in GitHub, Linear, and local logs\n- repeated hook notifications for the same failure\n- comments or status churn that should be summarized instead of forwarded raw\n- channels that duplicate each other without adding a better action path\n\nPrefer:\n- one canonical summary\n- one owner\n- one primary channel\n- one fallback path\n\n### 4. Design the ECC-native workflow\n\nFor each real notification need, define:\n- **source**\n- **gate**\n- **shape**: immediate alert, digest, queue, or dashboard-only\n- **channel**\n- **action**\n\nIf ECC already has the primitive, prefer:\n- a skill for operator triage\n- a hook for automatic emission\u002Fenforcement\n- an agent for delegated classification\n- an MCP\u002Fconnector only when a real bridge is missing\n\n### 5. Return an action-biased design\n\nEnd with:\n- what to keep\n- what to suppress\n- what to merge\n- what ECC should wrap next\n\n## Output Format\n\n```text\nCURRENT SURFACE\n- sources\n- channels\n- duplicates\n- gaps\n\nEVENT MODEL\n- critical\n- high\n- medium\n- low\n\nROUTING PLAN\n- source -> channel\n- why\n- operator owner\n\nCONSOLIDATION\n- suppress\n- merge\n- canonical summaries\n\nNEXT ECC MOVE\n- skill \u002F hook \u002F agent \u002F MCP\n- exact workflow to build next\n```\n\n## Recommendation Rules\n\n- prefer one strong lane over many weak ones\n- prefer digests for medium and low-signal updates\n- prefer hooks when the signal should emit automatically\n- prefer operator skills when the work is triage, routing, and review-first decision-making\n- prefer `project-flow-ops` when the root cause is backlog \u002F PR coordination rather than alerts\n- prefer `workspace-surface-audit` when the user first needs a source inventory\n- if desktop notifications are enough, do not invent an unnecessary external bridge\n\n## Good Use Cases\n\n- \"We have GitHub, Linear, and local hook alerts, but no single operator flow\"\n- \"Our CI failures are noisy and people ignore them\"\n- \"I want one notification policy across Claude, OpenCode, and Codex surfaces\"\n- \"Figure out what should interrupt versus land in a digest\"\n- \"Collapse overlapping notification PR ideas into one canonical ECC lane\"\n\n## Related Skills\n\n- `workspace-surface-audit`\n- `project-flow-ops`\n- `github-ops`\n- `knowledge-ops`\n- `customer-billing-ops` when the notification pain is billing\u002Fcustomer operations rather than engineering\n",{"name":5,"origin":24,"description":7},"ECC","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Feverything-claude-code\u002Fskills\u002Funified-notifications-ops",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill unified-notifications-ops",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill unified-notifications-ops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill unified-notifications-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002Fskills\u002Funified-notifications-ops\u002FSKILL.md",true,[],[49,56,61,67,74,81],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]