diff --git a/.tasks/STATUS.md b/.tasks/STATUS.md
index 0f11db6..375594f 100644
--- a/.tasks/STATUS.md
+++ b/.tasks/STATUS.md
@@ -799,3 +799,23 @@ Mode: `auto` — skill is purely behavioral (trigger-and-guidance for an MCP ser
 <!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-05-12T16:21:51.686Z -->
 
 ---
+
+## ⚪ [using-synology-ops-test-trigger] — Behavioral smoke-test for `using-synology-ops` trigger phrases. Verify the skill activates on its declared triggers AND does NOT activate on close-but-not-NAS phrases (false-positive check).
+
+Sub-task: after first real-world usage, tune triggers if false-pos / false-neg observed (e.g. skill misfires on "modulair-rag deploy scheduled tomorrow" — non-incident mention should be skipped).
+
+**Status:** ready
+**Where I stopped:** (not started)
+**Next action:** 1. In a fresh Claude Code session, test positive triggers (skill should activate):
+   - RU: "посмотри что с modulair-pipeline", "опс мсп проверь стек", "контейнер lightrag-modulair падает", "что у нас на NAS с tier1-converter"
+   - EN: "synology-ops show me the modulair stack", "what's wrong with tier1-converter", "check restart-loop on modulair-mcp"
+2. Test negative triggers (skill should NOT activate):
+   - "modulair-rag deploy scheduled tomorrow" (non-incident mention)
+   - "open Portainer GUI and check logs" (explicit Portainer-only flow)
+   - "restart-loop in books-pipeline" (different host, vps-books, not NAS)
+3. If skill misfires (or fails to fire), edit `description` in `~/projects/claude-skills/skills/using-synology-ops/SKILL.md`, rerun install + reload-plugins, repeat.
+4. Record verified triggers + any tuning notes in `where_stopped`.
+**Branch:** n/a
+<!-- created-by: OpeItcLoc03@DESKTOP-NSEF0UK / from: OpeItcLoc03/workshop / 2026-05-12T16:21:55.887Z -->
+
+---