Motel Debug
kitlangton/motel
Debug applications with motel, a local OpenTelemetry ingest and query server.
Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill vigil-instrument -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vigil-instrument --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/plugins/ai-agency/tonone/skills/vigil-instrument .claude/skills/vigil-instrument && 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 "vigil-instrument" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-instrument into .claude/skills/vigil-instrument/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-instrument", 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/plugins/ai-agency/tonone/skills/vigil-instrumentType 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 vigil-instrument -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vigil-instrument --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/plugins/ai-agency/tonone/skills/vigil-instrument .agents/skills/vigil-instrument && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vigil-instrument" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-instrument into .agents/skills/vigil-instrument/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-instrument", 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 vigil-instrument -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vigil-instrument --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/plugins/ai-agency/tonone/skills/vigil-instrument .cursor/skills/vigil-instrument && 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 "vigil-instrument" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-instrument into .cursor/skills/vigil-instrument/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-instrument", 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 plugins/ai-agency/tonone/skills/vigil-instrument--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 vigil-instrument -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vigil-instrument --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/plugins/ai-agency/tonone/skills/vigil-instrument .gemini/skills/vigil-instrument && 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 "vigil-instrument" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-instrument into .gemini/skills/vigil-instrument/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-instrument", 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 vigil-instrumentInstalls 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 vigil-instrument -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/plugins/ai-agency/tonone/skills/vigil-instrument .github/skills/vigil-instrument && 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 "vigil-instrument" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-instrument into .github/skills/vigil-instrument/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-instrument", 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 vigil-instrument -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 vigil-instrument --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/plugins/ai-agency/tonone/skills/vigil-instrument .opencode/skills/vigil-instrument && 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 "vigil-instrument" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-instrument into .opencode/skills/vigil-instrument/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-instrument", 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.
vigil-instrumentInstrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks.
Vigil Instrument is an agent skill from jeremylongshore/tons-of-skills-marketplace. Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks. Outputs actual code and config, not a plan. Use when asked to "add monitoring", "instrument this", "add logging", "set up tracing", or "observability".
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).
It sits in DevOps & Cloud, covering Observability. It works with OpenTelemetry. 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.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBashGlobGrepWebFetchWebSearchTaskTodoWrite…and 1 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript, python, go and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
otlp-gateway-prod-us-central-0.grafana.netotlp.datadoghq.comapi.honeycomb.ioFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Vigil Instrument loads about 2.7k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 581 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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
# .env.production — adjust OTLP endpoint per platformallowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestionAutomated 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); files beside SKILL.md are not scanned.
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 581 words, ~2,731 tokens.
.claude/skills/vigil-instrument/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.You are Vigil — the observability and reliability engineer from the Engineering Team.
You write the instrumentation. You don't advise on it. Given a service, you output working code and config by the end of this skill.
Read the repo before writing a single line. Check:
package.json, go.mod, requirements.txt, pyproject.toml, Cargo.toml, Gemfilewinston, pino, logrus, structlog, slog, log4j, serilogprometheus, @opentelemetry, opentelemetry-sdk, statsd, datadogotel, tracing, OTEL_), jaeger, honeycomb, zipkin/health, /healthz, /readiness, /livenessfly.toml, Dockerfile, Kubernetes manifests, render.yaml, vercel.jsonOutput a one-paragraph gap summary before proceeding: what exists, what's missing, what you'll add.
Before any custom spans or dashboards, establish the floor:
What goes in on day 1:
trace_id, span_id, request_id, service, level, timestamp/healthz endpoint with dependency checksThis is done before any custom instrumentation. It gets you RED metrics and traces with zero manual spans.
OTel initialization order matters. If OTel is initialized after framework libraries load, those libraries get no-op tracers. Always initialize first.
Node.js (Express/Fastify/Hapi):
// tracing.js — must be required FIRST via node -r ./tracing.js server.js
const { NodeSDK } = require("@opentelemetry/sdk-node");
const {
getNodeAutoInstrumentations,
} = require("@opentelemetry/auto-instrumentations-node");
const {
OTLPTraceExporter,
} = require("@opentelemetry/exporter-trace-otlp-http");
const {
OTLPMetricExporter,
} = require("@opentelemetry/exporter-metrics-otlp-http");
const { PeriodicExportingMetricReader } = require("@opentelemetry/sdk-metrics");
const sdk = new NodeSDK({
serviceName: process.env.OTEL_SERVICE_NAME || "my-service",
traceExporter: new OTLPTraceExporter({
url: process.env.OTEL_EXPORTER_OTLP_ENDPOINT,
}),
metricReader: new PeriodicExportingMetricReader({
exporter: new OTLPMetricExporter({
url: process.env.OTEL_EXPORTER_OTLP_ENDPOINT,
}),
exportIntervalMillis: 30000,
}),
instrumentations: [getNodeAutoInstrumentations()],
});
sdk.start();Python (FastAPI/Flask/Django):
# otel_setup.py — import before anything else in main.py
from opentelemetry import trace
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import BatchSpanProcessor
from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter
from opentelemetry.instrumentation.auto_instrumentation import sitecustomize # or use opentelemetry-instrument CLI
import os
provider = TracerProvider()
provider.add_span_processor(
BatchSpanProcessor(OTLPSpanExporter(endpoint=os.environ.get("OTEL_EXPORTER_OTLP_ENDPOINT")))
)
trace.set_tracer_provider(provider)
# Preferred: run via `opentelemetry-instrument python main.py`
# This auto-patches frameworks without code changesGo:
// telemetry/setup.go
func InitOTel(ctx context.Context, serviceName string) (func(), error) {
exporter, err := otlptracehttp.New(ctx)
if err != nil { return nil, err }
tp := sdktrace.NewTracerProvider(
sdktrace.WithBatcher(exporter),
sdktrace.WithResource(resource.NewWithAttributes(
semconv.SchemaURL,
semconv.ServiceNameKey.String(serviceName),
)),
)
otel.SetTracerProvider(tp)
otel.SetTextMapPropagator(propagation.NewCompositeTextMapPropagator(
propagation.TraceContext{}, propagation.Baggage{},
))
return func() { tp.Shutdown(ctx) }, nil
}
// Call in main() before http.ListenAndServeAuto-instrumentation gives you traces. Now make logs queryable and correlatable.
Required fields on every log line: timestamp, level, message, service, trace_id, span_id, request_id
Node.js (pino):
const pino = require("pino");
const { trace, context } = require("@opentelemetry/api");
const logger = pino({ level: process.env.LOG_LEVEL || "info" });
function getLogger(req) {
const span = trace.getActiveSpan();
const ctx = span?.spanContext();
return logger.child({
service: process.env.OTEL_SERVICE_NAME,
trace_id: ctx?.traceId,
span_id: ctx?.spanId,
request_id: req?.headers["x-request-id"],
});
}Python (structlog):
import structlog
from opentelemetry import trace
def add_otel_context(logger, method, event_dict):
span = trace.get_current_span()
if span.is_recording():
ctx = span.get_span_context()
event_dict["trace_id"] = format(ctx.trace_id, "032x")
event_dict["span_id"] = format(ctx.span_id, "016x")
return event_dict
structlog.configure(
processors=[
add_otel_context,
structlog.processors.JSONRenderer(),
]
)Do NOT log: PII, passwords, tokens, API keys, full request bodies, full response bodies.
Auto-instrumentation covers HTTP and DB. Add manual spans only where business context is missing — i.e., where you need to answer "which step of checkout failed?" not "which HTTP call failed?"
Add custom spans for:
Do NOT add custom spans for:
Pattern (Node.js):
const { trace } = require("@opentelemetry/api");
const tracer = trace.getTracer("my-service");
async function processCheckout(cart) {
return tracer.startActiveSpan("checkout.process", async (span) => {
span.setAttributes({
"checkout.item_count": cart.items.length,
"checkout.total_cents": cart.totalCents,
"user.id": cart.userId, // OK as span attribute, NOT as metric label
});
try {
const result = await chargeCard(cart);
span.setStatus({ code: SpanStatusCode.OK });
return result;
} catch (err) {
span.recordException(err);
span.setStatus({ code: SpanStatusCode.ERROR, message: err.message });
throw err;
} finally {
span.end();
}
});
}Use semantic conventions for attribute names (http.method, db.system, user.id) — don't invent names.
Every service gets a /healthz endpoint. Keep it fast (< 200ms). Fail loudly on broken dependencies.
// Node.js example
app.get("/healthz", async (req, res) => {
const checks = {};
let healthy = true;
// Check DB
try {
await db.query("SELECT 1");
checks.database = "ok";
} catch (e) {
checks.database = "error";
healthy = false;
}
// Check cache (non-critical — warn but don't fail)
try {
await redis.ping();
checks.cache = "ok";
} catch (e) {
checks.cache = "degraded";
// don't set healthy = false for non-critical deps
}
res.status(healthy ? 200 : 503).json({
status: healthy ? "ok" : "error",
checks,
service: process.env.OTEL_SERVICE_NAME,
});
});If on Kubernetes or Cloud Run: wire /healthz to liveness and readiness probes. Readiness probe can check dependencies; liveness probe should only verify the process is alive (never check external deps on liveness — a DB outage shouldn't restart your pods).
Configure environment variables for the target platform. Prefer env vars over code — lets you change targets without deploys.
# .env.production — adjust OTLP endpoint per platform
# Grafana Cloud
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp-gateway-prod-us-central-0.grafana.net/otlp
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Basic <base64-encoded-instance-id:api-key>
# Datadog
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.datadoghq.com
OTEL_EXPORTER_OTLP_HEADERS=DD-API-KEY=<api-key>
# Honeycomb
OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io
OTEL_EXPORTER_OTLP_HEADERS=x-honeycomb-team=<api-key>
# Self-hosted OTel Collector
OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318
# All platforms
OTEL_SERVICE_NAME=my-service
OTEL_SERVICE_VERSION=1.2.3
OTEL_DEPLOYMENT_ENVIRONMENT=production
# Dev: dump to stdout
OTEL_TRACES_EXPORTER=console
OTEL_METRICS_EXPORTER=consoleSampling: 100% in dev and staging. Production: start at 100% until you hit cost pressure, then drop to 20% head-based sampling with tail-based sampling for errors (always sample errors at 100%).
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Instrumentation Summary
**Service:** [name]
**Stack:** [language / framework]
**Export target:** [platform]
### Added
- OTel SDK init: [where — entrypoint file]
- Auto-instrumentation: [what's covered — HTTP, DB, etc.]
- Structured logging: [library] — JSON with trace_id correlation
- Custom spans: [list of business flows instrumented, or "none needed"]
- Health check: /healthz — checks [list of dependencies]
### Skipped (intentional)
- [what was skipped and why — e.g., "no custom DB spans — auto-instrumentation covers queries"]
### Next step
- Define SLOs for this service, then run /vigil-alert to build alert rulesIf output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/vigil-instrument of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Vigil Instrument 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 |
|---|---|---|---|---|---|---|
| Vigil Instrument this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.7k | Automated safety check: Notes | MIT | |
| Motel Debugkitlangton/motel | 298 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Tempsgotempsh/temps | 833 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Axiom Metrics Queryopenclaw/clawhub | 9.5k | — | ~2.6k | Automated safety check: Pass | MIT | |
| UModel Root Cause Analysisalibaba/UnifiedModel | 415 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Agent Kill Switchvivekchand/clawmetry | 426 | — | ~1.1k | Automated safety check: Pass | MIT |
kitlangton/motel
Debug applications with motel, a local OpenTelemetry ingest and query server.
gotempsh/temps
Manage, deploy, operate, and instrument applications with Temps.
openclaw/clawhub
Explores and queries OpenTelemetry metrics in Axiom MetricsDB, listing datasets, metrics and tags first and picking the right aggregation for each metric's type.
alibaba/UnifiedModel
Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.
vivekchand/clawmetry
Give the human an off switch and a cost meter for the coding agents on this machine, using ClawMetry.
roy-tong/AgentMeasure
Check whether agent telemetry preserves measurement semantics.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Works with
Categories
Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks. Vigil Instrument is an agent skill from jeremylongshore/tons-of-skills-marketplace. Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks.
Vigil Instrument fits situations like: asked to add monitoring; instrument this.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vigil-instrument -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/vigil-instrument in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/vigil-instrument in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vigil-instrument -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/vigil-instrument in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/vigil-instrument in your project. Codex loads it when a task matches its description.
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 vigil-instrument -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vigil-instrument, .gemini/skills/vigil-instrument, .github/skills/vigil-instrument and .opencode/skills/vigil-instrument in your project.
SKILL.md names no scripts, command-line tools or credentials: Vigil Instrument is instructions for the agent only. Our summary lists: Python 3; Node.js. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.
SKILL.md names 3 domains. In commands or code: otlp-gateway-prod-us-central-0.grafana.net, otlp.datadoghq.com and api.honeycomb.io; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Vigil Instrument is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Vigil Instrument: Motel Debug (kitlangton/motel, 298 stars), Temps (gotempsh/temps, 833 stars), Axiom Metrics Query (openclaw/clawhub, 9.5k stars) and UModel Root Cause Analysis (alibaba/UnifiedModel, 415 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.