ntfy-notifications
Skill1 starsChanged 28 days agoMITView on GitHub
Use when sending a notification to ntfy from a homelab service, loop, script, or agent.
- Sends data out
2 other projects use a version of this.
Adopted by
Most recently taken up by
- sammasak/skillsword for word, first seen Oct 17, 2026
- ddnetters/homelab-agent-skillstheir own version, first seen Mar 18, 2026
Other versions2 projects use a version of this.
Word for word · 1
- sammasak/skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 1
- ddnetters/homelab-agent-skills★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- agent-handoffSkill
- agent-orchestrationSkill
- assigning-subagent-modelsSkill
- credentialsSkill
- deep-modulesSkill
- device-protocol-investigationSkill
- e2e-testingSkill
- herdr-operationsSkill
- herdrSkill
- knowledge-vaultSkill
- kubernetes-gitopsSkill
- lean-codeSkill
- nix-audit-operatorSkill
- nix-flake-developmentSkill
- orchestrated-reviewSkill
- pcap-evidence-analysisSkill
- pi-offloadSkill
- pi-ticketSkill
- rf-chaos-experiment-reviewSkill
- rust-engineeringSkill
- sdlc-pipelineSkill
- secrets-managementSkill
- tooling-feedbackSkill
- verify-serviceSkill
- wireless-lab-diagnosticsSkill
The file
Files
ntfy Notifications
ntfy runs in namespace ntfy on the control-plane node (lenovo) and is the paging path. It is deliberately unauthenticated (no Authentik forward-auth since 2026-08-26, so pages still deliver when SSO is down); ntfy.sammasak.dev resolves only on LAN/tailnet. Do not add auth middleware to it.
Publish
Pick the URL by where the caller runs:
| Caller | URL |
| pod, Job, Alertmanager webhook, host resolving cluster DNS | http://ntfy.ntfy.svc.cluster.local/<topic> (preferred) |
| LAN or tailnet host without cluster DNS | https://ntfy.sammasak.dev/<topic> |
| cluster network reach, no DNS at all | http://10.43.19.253/<topic> (ClusterIP, not stable across Service recreation; re-check with kubectl get svc -n ntfy ntfy) |
curl -fsS -X POST -H "Title: <title>" -H "Tags: <tag>" -H "Priority: <prio>" -d "<body>" <url>Success is exit 0 with a JSON body containing "id". Use -f: with plain -s a redirect or error page (e.g. if someone re-adds auth) looks like success.
Topics
Reuse existing topics; if you add one, add a row here in the same change.
| Topic | Used by |
homelab-alerts | Alertmanager (via alertmanager-ntfy-bridge) |
homelab-improvements | improvement/DevEx loops |
Headers: Title short subject; Tags emoji shortcodes (wrench, white_check_mark, warning); Priority min / default / high.
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
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.