JaviMontano/alerting-strategy
skills/alerting-strategy/SKILL.md
Alert fatigue prevention, escalation rules, severity classification. [EXPLICIT] Trigger: "alerting strategy"
$ install --global
skillsauthnpx skillsauth add JaviMontano/jm-adk-alfa alerting-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 30, 2026, 4:48 AM24.3s19 files scanned
SKILL.md
- name:
- alerting-strategy
- author:
- JM Labs (Javier Montaño)
- version:
- 1.0.0
- description:
- >
- Trigger:
- alerting strategy
Alerting Strategy
"Method over hacks."
TL;DR
Alert fatigue prevention, escalation rules, severity classification. [EXPLICIT]
Procedure
Step 1: Discover
- Gather context and requirements
Step 2: Analyze
- Evaluate options per Constitution XIII/XIV
Step 3: Execute
- Implement with evidence tags
Step 4: Validate
- Verify quality criteria met
Quality Criteria
- [ ] Evidence tags applied
- [ ] Constitution-compliant
- [ ] Actionable output
Usage
Example invocations:
- "/alerting-strategy" — Run the full alerting strategy workflow
- "alerting strategy on this project" — Apply to current context
Assumptions & Limits
- Assumes access to project artifacts (code, docs, configs) [EXPLICIT]
- Requires English-language output unless otherwise specified [EXPLICIT]
- Does not replace domain expert judgment for final decisions [EXPLICIT]
Edge Cases
| Scenario | Handling | |----------|----------| | Empty or minimal input | Request clarification before proceeding | | Conflicting requirements | Flag conflicts explicitly, propose resolution | | Out-of-scope request | Redirect to appropriate skill or escalate |
Related Skills
JaviMontano/analytics-engineering
development
VerifiedTrustedCommunity
This skill should be used when the user asks to "design analytics models", "set up a dbt project", "plan data transformations", "define data contracts", or "model a star schema", or mentions staging models, marts, incremental strategies, or materializations. It produces analytics pipeline designs with dbt-style transformations, data modeling patterns, testing strategies, and documentation plans. [EXPLICIT] Use this skill whenever the user needs source-to-target mapping, materialization decisions, or transformation framework architecture, even if they don't explicitly ask for "analytics engineering". [EXPLICIT]
1SKILL.mdUpdated May 30, 2026
JaviMontano/ai-workflow-automation
tools
VerifiedTrustedCommunity
LLM-in-the-loop workflows, human-AI handoff, approval gates. [EXPLICIT] Trigger: "ai workflow automation"
1SKILL.mdUpdated May 30, 2026
JaviMontano/ai-testing-strategy
tools
VerifiedTrustedCommunity
Comprehensive testing strategy for AI systems — testing scope matrix (6 types x 6 layers), model prediction testing, data quality testing, compliance and fairness testing, integration approaches, and CI/CD test automation. This skill should be used when the user asks to "define AI testing strategy", "test ML models", "design data quality tests", "plan fairness testing", "test AI pipelines", "design integration tests for ML", or mentions adversarial testing, drift simulation, model regression testing, bias testing, explainability testing, or AI test automation. [EXPLICIT]
1SKILL.mdUpdated May 30, 2026
JaviMontano/ai-software-architecture
development
VerifiedTrustedCommunity
AI software architecture design — modules, layers, boundaries, design patterns, ADRs, quality attributes, and technical debt strategy for AI-enabled systems. This skill should be used when the user asks to "design AI system structure", "define AI module boundaries", "select AI architecture patterns", "document AI architecture decisions", "evaluate AI code architecture", or mentions AI pipelines, feature stores, model serving, drift detection, ML quality attributes, explainability architecture, or AI technical debt. [EXPLICIT]
1SKILL.mdUpdated May 29, 2026