Frontmcp Observability
agentfront/frontmcp
A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.
Observability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots.
Install Vigil Recon
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill vigil-recon -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vigil-recon --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-recon .claude/skills/vigil-recon && 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-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-recon into .claude/skills/vigil-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-recon", 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-reconType 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-recon -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vigil-recon --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-recon .agents/skills/vigil-recon && 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-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-recon into .agents/skills/vigil-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-recon", 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-recon -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vigil-recon --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-recon .cursor/skills/vigil-recon && 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-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-recon into .cursor/skills/vigil-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-recon", 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-recon--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-recon -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace vigil-recon --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-recon .gemini/skills/vigil-recon && 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-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-recon into .gemini/skills/vigil-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-recon", 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-reconInstalls 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-recon -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-recon .github/skills/vigil-recon && 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-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-recon into .github/skills/vigil-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-recon", 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-recon -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-recon --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-recon .opencode/skills/vigil-recon && 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-recon" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/vigil-recon into .opencode/skills/vigil-recon/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vigil-recon", 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
vigil-recon- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 362 words
- Files
- 2
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Observability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots.
- Works in 4 steps: Detect Environment → Discover Monitoring Platforms → Inventory What's Instrumented → …
- Asked what monitoring exists
- SKILL.md covers Steps and Delivery
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vigil Recon is an agent skill from jeremylongshore/tons-of-skills-marketplace. Observability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots. Use when asked "what monitoring exists", "observability assessment", or "what can we see".
Its SKILL.md is about 1.1k 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 and Monitoring and alerting. It works with Docker, Grafana and Datadog. 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
- Asked what monitoring exists
- Observability assessment
- What can we see
Example prompts
- “what monitoring exists”
- “observability assessment”
- “what can we see”
- “/vigil-recon”
Requirements
- Docker
- Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
Workflow steps
4 steps, taken from the step headings in SKILL.md.
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:
ReadBashGlobGrepWebFetchWebSearchAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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.
Context cost
Vigil Recon loads about 1.1k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 362 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 362 words, ~1,138 tokens.
Download SKILL.mdSave it as
.claude/skills/vigil-recon/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- vigil-recon
- description
- Observability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots. Use when asked "what monitoring exists", "observability assessment", or "what can we see".
- allowed-tools
- Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
- version
- 0.6.4
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
Observability Reconnaissance
You are Vigil — the observability and reliability engineer from the Engineering Team.
Steps
Step 0: Detect Environment
Scan the project broadly to discover all observability infrastructure:
- Check for language/framework:
package.json,go.mod,requirements.txt,pyproject.toml,Cargo.toml - Check deployment platform:
Dockerfile,docker-compose.yml,fly.toml,app.yaml, Kubernetes manifests,render.yaml, serverless configs - Identify all services: scan for service definitions, separate build targets, microservice boundaries
This is read-only reconnaissance — do not modify anything.
Step 1: Discover Monitoring Platforms
Search for all monitoring and observability platforms in use:
Metrics platforms:
- Search for:
prometheus,grafana,datadog,newrelic,cloudwatch,cloud_monitoring,statsd,influxdb - Check: config files, environment variables, SDK initialization, Docker Compose services
Tracing platforms:
- Search for:
opentelemetry,otel,jaeger,zipkin,honeycomb,cloud_trace,xray,datadog-apm - Check: SDK initialization, collector configs, sampling configuration
Logging platforms:
- Search for:
elasticsearch,kibana,loki,cloud_logging,cloudwatch_logs,datadog_logs,axiom,betterstack - Check: log shipping configs, fluentd/fluentbit configs, logging library settings
Alerting platforms:
- Search for:
pagerduty,opsgenie,grafana_alerting,cloudwatch_alarms,betterstack - Check: alert rule definitions, notification channel configs, escalation policies
Error tracking:
- Search for:
sentry,bugsnag,rollbar,crashlytics - Check: DSN configs, SDK initialization, error boundary setup
Show full SKILL.md (184 more words)Show less
Step 2: Inventory What's Instrumented
For each service, catalog what exists:
- Metrics: what's being measured, what labels are used, where are they exported
- Dashboards: check for Grafana dashboard JSON files, dashboard-as-code configs, references to dashboard URLs
- Alerts: list all alert rules found — what they trigger on, severity, notification target
- Runbooks: check for runbook files, links in alert annotations, incident response documentation
- SLOs: check for SLO definitions, error budget configurations, SLO-based alerts
- Tracing: what's traced, sampling rate, trace context propagation
- Logging: structured or unstructured, what level, where shipped, retention policy
- Incident history: check for postmortem files, incident docs, CHANGELOG entries referencing incidents
Step 3: Present Coverage Map
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Present findings as a structured assessment:
## Observability Reconnaissance
### Monitoring Stack
- **Metrics:** [platform] — [status: active/configured/missing]
- **Tracing:** [platform] — [status]
- **Logging:** [platform] — [status]
- **Alerting:** [platform] — [status]
- **Error tracking:** [platform] — [status]
### Service Coverage
| Service | Metrics | Tracing | Logging | Alerts | Runbooks | SLOs |
|---------|---------|---------|---------|--------|----------|------|
| [name] | [detail]| [detail]| [detail]| [count]| [count] | [y/n]|
### What's Working Well
- [positive finding]
### Blind Spots
- [what's not monitored and why it's a risk]
### Incident Readiness
- Runbooks: [count found] / [count needed]
- SLOs defined: [yes/no — for which services]
- On-call setup: [detected/not detected]
- Postmortem history: [count found]
### Recommendations (prioritized)
1. [highest priority gap] — [why] — [effort estimate]
2. [next priority] — [why] — [effort estimate]
3. [next priority] — [why] — [effort estimate]This is a reconnaissance report — present facts, highlight risks, recommend actions. Do not make changes.
Delivery
If 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
Files
SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/vigil-recon of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- .claude-plugin/plugin.json
Open the folder on GitHubat commit cfae287
Compare with similar skills
Vigil Recon 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 Recon this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Notes | 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 | |
| Alloygrafana/skills | 282 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Cost Exportruvnet/ruflo | 74k | — | ~687 | Automated safety check: Notes | MIT | |
| Ag2 Telemetryag2ai/build-with-ag2 | 252 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Monitoring Observability
ahmedasmar/devops-claude-skills
Monitoring and observability strategy, implementation, and troubleshooting.
- 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 /…
Cost Export
ruvnet/ruflo
Export cost-tracking telemetry in Prometheus textfile or webhook JSON formats — for external observability (Grafana, Datadog, custom dashboards)
Ag2 Telemetry
ag2ai/build-with-ag2
Add OpenTelemetry traces to an AG2 beta Agent via TelemetryMiddleware (autogen.beta.middleware.builtin).
Observability
TheBeardedBearSAS/claude-craft
OpenTelemetry, distributed tracing, structured logging, metrics (Prometheus, Grafana, Datadog).
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
Categories
Questions about Vigil Recon
What does Vigil Recon do?
Observability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots. Vigil Recon is an agent skill from jeremylongshore/tons-of-skills-marketplace. Observability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots.
When should I use Vigil Recon?
Vigil Recon fits situations like: asked what monitoring exists; observability assessment; what can we see.
How do I install Vigil Recon in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vigil-recon -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/vigil-recon in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/vigil-recon in your project. Claude Code loads it when a task matches its description.
How do I install Vigil Recon in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill vigil-recon -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/vigil-recon in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/vigil-recon in your project. Codex loads it when a task matches its description.
Can I use Vigil Recon 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 vigil-recon -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-recon, .gemini/skills/vigil-recon, .github/skills/vigil-recon and .opencode/skills/vigil-recon in your project.
What does Vigil Recon need to run?
SKILL.md names no scripts, command-line tools or credentials: Vigil Recon is instructions for the agent only. Our summary lists: Docker. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion.
Does Vigil Recon access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vigil Recon safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Vigil Recon use?
Vigil Recon 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 Vigil Recon use?
About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vigil Recon?
Skills that share tags, products or a category with Vigil Recon: Frontmcp Observability (agentfront/frontmcp, 146 stars), Monitoring Observability (ahmedasmar/devops-claude-skills, 203 stars), Alloy (grafana/skills, 282 stars) and Cost Export (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vigil Recon?
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.