Tsh Implementing Observability
TheSoftwareHouse/copilot-collections
Observability patterns for logging, monitoring, alerting, and distributed tracing.
Agent skill
Deploying Monitoring Stacks
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Monitor use when deploying monitoring stacks including Prometheus, Grafana, and Datadog.
Install Deploying Monitoring Stacks
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deploying-monitoring-stacks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deploying-monitoring-stacks --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/deploying-monitoring-stacks .claude/skills/deploying-monitoring-stacks && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deploying-monitoring-stacks" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/deploying-monitoring-stacks into .claude/skills/deploying-monitoring-stacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-monitoring-stacks", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/deploying-monitoring-stacksType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deploying-monitoring-stacks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deploying-monitoring-stacks --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/deploying-monitoring-stacks .agents/skills/deploying-monitoring-stacks && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deploying-monitoring-stacks" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/deploying-monitoring-stacks into .agents/skills/deploying-monitoring-stacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-monitoring-stacks", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deploying-monitoring-stacks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deploying-monitoring-stacks --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/deploying-monitoring-stacks .cursor/skills/deploying-monitoring-stacks && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deploying-monitoring-stacks" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/deploying-monitoring-stacks into .cursor/skills/deploying-monitoring-stacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-monitoring-stacks", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/deploying-monitoring-stacks--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deploying-monitoring-stacks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deploying-monitoring-stacks --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/deploying-monitoring-stacks .gemini/skills/deploying-monitoring-stacks && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deploying-monitoring-stacks" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/deploying-monitoring-stacks into .gemini/skills/deploying-monitoring-stacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-monitoring-stacks", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deploying-monitoring-stacksInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deploying-monitoring-stacks -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/deploying-monitoring-stacks .github/skills/deploying-monitoring-stacks && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deploying-monitoring-stacks" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/deploying-monitoring-stacks into .github/skills/deploying-monitoring-stacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-monitoring-stacks", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deploying-monitoring-stacks -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deploying-monitoring-stacks --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/deploying-monitoring-stacks .opencode/skills/deploying-monitoring-stacks && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deploying-monitoring-stacks" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/deploying-monitoring-stacks into .opencode/skills/deploying-monitoring-stacks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploying-monitoring-stacks", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
deploying-monitoring-stacks- GitHub stars
- 2.8k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 498 words
- Files
- 10 (incl. scripts, references, assets)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Monitor use when deploying monitoring stacks including Prometheus, Grafana, and Datadog.
- Works in 10 steps: Select the monitoring platform:… → Deploy the monitoring stack: helm… → Install exporters on monitored systems:… → …
- Deploying monitoring stacks including Prometheus
- SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 3 more sections
- Runs Python scripts from its folder; calls helm
What it does
Deploying Monitoring Stacks is an agent skill from jeremylongshore/tons-of-skills-marketplace. Monitor use when deploying monitoring stacks including Prometheus, Grafana, and Datadog. Trigger with phrases like "deploy monitoring stack", "setup prometheus", "configure grafana", or "install datadog agent". Generates production-ready configurations with metric collection, visualization dashboards, and alerting rules.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts, reference files and assets (for example `assets/README.md`, `assets/datadog_agent_config_template.yml` and `assets/grafana_dashboard_template.json`). Compatibility notes: Designed for Claude Code
It sits in DevOps & Cloud, covering Monitoring and alerting. It works with Prometheus, Grafana, Datadog and Kubernetes. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Deploying monitoring stacks including Prometheus
- With phrases like deploy monitoring stack
- Setup prometheus
- Configure grafana
Example prompts
- “deploy monitoring stack”
- “setup prometheus”
- “configure grafana”
- “/deploying-monitoring-stacks”
Requirements
- Python 3
- Docker
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(docker:*), Bash(kubectl:*)
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Select the monitoring platform: Prometheus + Grafana for open-source self-hosted, Datadog for managed SaaS, Victoria Metrics for…
- Deploy the monitoring stack: helm install kube-prometheus-stack prometheus-community/kube-prometheus-stack or Docker Compose for…
- Install exporters on monitored systems: node-exporter for host metrics, kube-state-metrics for Kubernetes object states…
- Configure scrape targets in prometheus.yml: define job names, scrape intervals, and relabeling rules for service discovery
- Create recording rules for frequently queried aggregations to reduce dashboard query load
- Define alerting rules with meaningful thresholds: high CPU (>80% for 5m), high memory (>90%), error rate (>1%), latency P99 (>500ms)
- Configure Alertmanager with routing, grouping, and notification channels (Slack, PagerDuty, email)
- Build Grafana dashboards: RED metrics (Rate, Errors, Duration) for services, USE metrics (Utilization, Saturation, Errors) for resources
- Set up data retention: configure TSDB retention period (15-30 days local), set up Thanos/Cortex for long-term storage if needed
- Test the full pipeline: trigger a test alert and verify notification delivery
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGrepGlobBash(docker:*)Bash(kubectl:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 4 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
helm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
prometheus.iografana.comgithub.comdocs.datadoghq.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Deploying Monitoring Stacks loads about 1.2k tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 498 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 498 words, ~1,239 tokens.
Download SKILL.mdSave it as
.claude/skills/deploying-monitoring-stacks/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- deploying-monitoring-stacks
- description
- Monitor use when deploying monitoring stacks including Prometheus, Grafana, and Datadog. Trigger with phrases like "deploy monitoring stack", "setup prometheus", "configure grafana", or "install datadog agent". Generates production-ready configurations with metric collection, visualization dashboards, and alerting rules.
- allowed-tools
- Read, Write, Edit, Grep, Glob, Bash(docker:*), Bash(kubectl:*)
- compatibility
- Designed for Claude Code
- version
- 1.26.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- devops, deployment, monitoring, dashboard
Deploying Monitoring Stacks
Overview
Deploy production monitoring stacks (Prometheus + Grafana, Datadog, or Victoria Metrics) with metric collection, custom dashboards, and alerting rules. Configure exporters, scrape targets, recording rules, and notification channels for comprehensive infrastructure and application observability.
Prerequisites
- Target infrastructure identified: Kubernetes cluster, Docker hosts, or bare-metal servers
- Metric endpoints accessible from the monitoring platform (application
/metrics, node exporters) - Storage backend capacity planned for time-series data (Prometheus TSDB, Thanos, or Cortex for long-term)
- Alert notification channels defined: Slack webhook, PagerDuty integration key, or email SMTP
- Helm 3+ for Kubernetes deployments using kube-prometheus-stack or similar charts
Instructions
- Select the monitoring platform: Prometheus + Grafana for open-source self-hosted, Datadog for managed SaaS, Victoria Metrics for high-cardinality workloads
- Deploy the monitoring stack:
helm install kube-prometheus-stack prometheus-community/kube-prometheus-stackor Docker Compose for non-Kubernetes - Install exporters on monitored systems: node-exporter for host metrics, kube-state-metrics for Kubernetes object states, application-specific exporters
- Configure scrape targets in
prometheus.yml: define job names, scrape intervals, and relabeling rules for service discovery - Create recording rules for frequently queried aggregations to reduce dashboard query load
- Define alerting rules with meaningful thresholds: high CPU (>80% for 5m), high memory (>90%), error rate (>1%), latency P99 (>500ms)
- Configure Alertmanager with routing, grouping, and notification channels (Slack, PagerDuty, email)
- Build Grafana dashboards: RED metrics (Rate, Errors, Duration) for services, USE metrics (Utilization, Saturation, Errors) for resources
- Set up data retention: configure TSDB retention period (15-30 days local), set up Thanos/Cortex for long-term storage if needed
- Test the full pipeline: trigger a test alert and verify notification delivery
Output
- Helm values file or Docker Compose for the monitoring stack
- Prometheus configuration with scrape targets, recording rules, and alerting rules
- Alertmanager configuration with routing tree and notification receivers
- Grafana dashboard JSON files for infrastructure and application metrics
- Exporter deployment manifests (node-exporter DaemonSet, application ServiceMonitor)
Show full SKILL.md (193 more words)Show less
Error Handling
| Error | Cause | Solution |
|---|---|---|
No data points in dashboard | Scrape target not reachable or metric name wrong | Check Targets page in Prometheus UI; verify service discovery and metric name |
Too many time series (high cardinality) | Labels with unbounded values (user IDs, request IDs) | Remove high-cardinality labels with metric_relabel_configs; use recording rules for aggregation |
Alert condition met but no notification | Alertmanager routing or receiver misconfigured | Verify Alertmanager config with amtool check-config; test receiver with amtool silence |
Prometheus OOMKilled | Insufficient memory for series count | Increase memory limits; reduce scrape targets or retention; add WAL compression |
Grafana datasource connection failed | Wrong Prometheus URL or network policy blocking access | Verify datasource URL in Grafana; check Kubernetes service name and port; review network policies |
Examples
- "Deploy kube-prometheus-stack on Kubernetes with alerts for node CPU > 80%, pod restart count > 5, and API error rate > 1%, sending to Slack."
- "Set up Prometheus + Grafana on Docker Compose for monitoring 10 application servers with node-exporter and custom application metrics."
- "Create Grafana dashboards for the four golden signals (latency, traffic, errors, saturation) for a microservices application."
Resources
- Prometheus documentation: https://prometheus.io/docs/
- Grafana documentation: https://grafana.com/docs/grafana/latest/
- kube-prometheus-stack: https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack
- Alerting best practices: https://prometheus.io/docs/practices/alerting/
- Datadog documentation: https://docs.datadoghq.com/
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files (scripts, references, assets) in skills/.curated/deploying-monitoring-stacks of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- assets/README.md
- assets/datadog_agent_config_template.yml
- assets/grafana_dashboard_template.json
- assets/prometheus_config_template.yml
- references/README.md
- scripts/README.md
- scripts/deploy_datadog_agent.py
- scripts/deploy_grafana.py
- scripts/deploy_prometheus.py
Open the folder on GitHubat commit cfae287
Compare with similar skills
Deploying Monitoring Stacks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deploying Monitoring Stacks this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Tsh Implementing ObservabilityTheSoftwareHouse/copilot-collections | 284 | — | ~2k | Automated safety check: Pass | MIT | |
| Frontmcp Observabilityagentfront/frontmcp | 146 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Monitoring Observabilityahmedasmar/devops-claude-skills | 203 | — | ~3.9k | Automated safety check: Pass | None | |
| Prometheus GrafanaBagelHole/DevOps-Security-Agent-Skills | 1.2k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Grafana Dashboardpando85/kaniop | 132 | — | ~987 | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Frontmcp Observability
agentfront/frontmcp
A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.
Monitoring Observability
ahmedasmar/devops-claude-skills
Monitoring and observability strategy, implementation, and troubleshooting.
Prometheus Grafana
BagelHole/DevOps-Security-Agent-Skills
Set up metrics collection and visualization with Prometheus and Grafana.
Grafana Dashboard
pando85/kaniop
Improve and validate the Kaniop Grafana dashboard against repository metrics and the grigri live cluster.
- Official
Alloy
grafana/skills
Build a unified telemetry pipeline with Grafana Alloy — one OpenTelemetry-compatible binary that collects metrics, logs, traces, and profiles and ships to Grafana Cloud / Prometheus / Loki / Tempo /…
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Works with
Categories
Questions about Deploying Monitoring Stacks
What does Deploying Monitoring Stacks do?
Monitor use when deploying monitoring stacks including Prometheus, Grafana, and Datadog. Deploying Monitoring Stacks is an agent skill from jeremylongshore/tons-of-skills-marketplace. Monitor use when deploying monitoring stacks including Prometheus, Grafana, and Datadog.
When should I use Deploying Monitoring Stacks?
Deploying Monitoring Stacks fits situations like: deploying monitoring stacks including Prometheus; with phrases like deploy monitoring stack; setup prometheus; configure grafana.
How do I install Deploying Monitoring Stacks in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill deploying-monitoring-stacks -a claude-code`. Or copy the skill folder (skills/.curated/deploying-monitoring-stacks in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/deploying-monitoring-stacks in your project. Claude Code loads it when a task matches its description.
How do I install Deploying Monitoring Stacks in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill deploying-monitoring-stacks -a codex`. Or copy the skill folder (skills/.curated/deploying-monitoring-stacks in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/deploying-monitoring-stacks in your project. Codex loads it when a task matches its description.
Can I use Deploying Monitoring Stacks in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill deploying-monitoring-stacks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deploying-monitoring-stacks, .gemini/skills/deploying-monitoring-stacks, .github/skills/deploying-monitoring-stacks and .opencode/skills/deploying-monitoring-stacks in your project.
What does Deploying Monitoring Stacks need to run?
Going by SKILL.md and its folder, Deploying Monitoring Stacks needs Python for the scripts in its folder and the command-line tools its instructions call (helm). Our summary lists: Python 3; Docker. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(docker:*), Bash(kubectl:*). Compatibility (from SKILL.md): Designed for Claude Code.
Does Deploying Monitoring Stacks access the network?
SKILL.md names 4 domains. As links in the text: prometheus.io, grafana.com, github.com and docs.datadoghq.com. This is read from the text; nothing was executed.
Is Deploying Monitoring Stacks safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Deploying Monitoring Stacks use?
Deploying Monitoring Stacks is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Deploying Monitoring Stacks use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17 tokens, read only when the agent opens those files.
What are the alternatives to Deploying Monitoring Stacks?
Skills that share tags, products or a category with Deploying Monitoring Stacks: Tsh Implementing Observability (TheSoftwareHouse/copilot-collections, 284 stars), Frontmcp Observability (agentfront/frontmcp, 146 stars), Monitoring Observability (ahmedasmar/devops-claude-skills, 203 stars) and Prometheus Grafana (BagelHole/DevOps-Security-Agent-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deploying Monitoring Stacks?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.