Frontend Session Rca
grafana/skills
Diagnoses a Grafana Frontend Observability (RUM) session: whether it is healthy, what went wrong, ranked problems with timestamps and evidence, likely cause, how to fix it.
Agent skill
Setting Up Synthetic Monitoring
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Setup synthetic monitoring for proactive performance tracking including uptime checks, transaction monitoring, and API health.
Install Setting Up Synthetic Monitoring
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill setting-up-synthetic-monitoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace setting-up-synthetic-monitoring --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/setting-up-synthetic-monitoring .claude/skills/setting-up-synthetic-monitoring && 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 "setting-up-synthetic-monitoring" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/setting-up-synthetic-monitoring into .claude/skills/setting-up-synthetic-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-synthetic-monitoring", 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/setting-up-synthetic-monitoringType 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 setting-up-synthetic-monitoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace setting-up-synthetic-monitoring --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/setting-up-synthetic-monitoring .agents/skills/setting-up-synthetic-monitoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "setting-up-synthetic-monitoring" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/setting-up-synthetic-monitoring into .agents/skills/setting-up-synthetic-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-synthetic-monitoring", 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 setting-up-synthetic-monitoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace setting-up-synthetic-monitoring --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/setting-up-synthetic-monitoring .cursor/skills/setting-up-synthetic-monitoring && 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 "setting-up-synthetic-monitoring" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/setting-up-synthetic-monitoring into .cursor/skills/setting-up-synthetic-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-synthetic-monitoring", 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/setting-up-synthetic-monitoring--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 setting-up-synthetic-monitoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace setting-up-synthetic-monitoring --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/setting-up-synthetic-monitoring .gemini/skills/setting-up-synthetic-monitoring && 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 "setting-up-synthetic-monitoring" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/setting-up-synthetic-monitoring into .gemini/skills/setting-up-synthetic-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-synthetic-monitoring", 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 setting-up-synthetic-monitoringInstalls 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 setting-up-synthetic-monitoring -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/setting-up-synthetic-monitoring .github/skills/setting-up-synthetic-monitoring && 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 "setting-up-synthetic-monitoring" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/setting-up-synthetic-monitoring into .github/skills/setting-up-synthetic-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-synthetic-monitoring", 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 setting-up-synthetic-monitoring -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 setting-up-synthetic-monitoring --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/setting-up-synthetic-monitoring .opencode/skills/setting-up-synthetic-monitoring && 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 "setting-up-synthetic-monitoring" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/setting-up-synthetic-monitoring into .opencode/skills/setting-up-synthetic-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setting-up-synthetic-monitoring", 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
setting-up-synthetic-monitoring- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 480 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Setup synthetic monitoring for proactive performance tracking including uptime checks, transaction monitoring, and API health.
- Works in 3 steps: Identify Monitoring Needs: Determine the… → Design Monitoring Scenarios: Create… → Configure Monitoring: Set up the…
- Implementing availability monitoring
- SKILL.md covers Overview, How It Works, When to Use This Skill and Examples, plus 7 more sections
- Runs Python scripts from its folder
What it does
Setting Up Synthetic Monitoring is an agent skill from jeremylongshore/tons-of-skills-marketplace. Setup synthetic monitoring for proactive performance tracking including uptime checks, transaction monitoring, and API health. Use when implementing availability monitoring or tracking critical user journeys. Trigger with phrases like "setup synthetic monitoring", "monitor uptime", or "configure health checks".
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/README.md`, `references/README.md` and `scripts/README.md`). Compatibility notes: Designed for Claude Code
It sits in DevOps & Cloud, covering Monitoring and alerting and Customer journey mapping. 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
- Implementing availability monitoring
- Tracking critical user journeys
- With phrases like setup synthetic monitoring
- Configure health checks
Example prompts
- “setup synthetic monitoring”
- “monitor uptime”
- “configure health checks”
- “/setting-up-synthetic-monitoring”
Requirements
- Python 3
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(curl:*), Bash(monitoring:*)
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Identify Monitoring Needs: Determine the critical endpoints, user journeys, and APIs to monitor based on the user's application…
- Design Monitoring Scenarios: Create specific monitoring scenarios for uptime, transactions, and API performance, including frequency and…
- Configure Monitoring: Set up the synthetic monitoring tool with the designed scenarios, including alerts and dashboards for performance…
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(curl:*)Bash(monitoring:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Python), which the agent can run.
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.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Setting Up Synthetic Monitoring loads about 1.1k tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 480 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). 480 words, ~1,109 tokens.
Download SKILL.mdSave it as
.claude/skills/setting-up-synthetic-monitoring/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- setting-up-synthetic-monitoring
- description
- Setup synthetic monitoring for proactive performance tracking including uptime checks, transaction monitoring, and API health. Use when implementing availability monitoring or tracking critical user journeys. Trigger with phrases like "setup synthetic monitoring", "monitor uptime", or "configure health checks".
- allowed-tools
- Read, Write, Edit, Grep, Glob, Bash(curl:*), Bash(monitoring:*)
- compatibility
- Designed for Claude Code
- version
- 1.22.0
- license
- MIT
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- tags
- performance, api, monitoring
Synthetic Monitoring Setup
Configure synthetic monitoring for uptime checks, transaction flows, and API health using Pingdom, Datadog, or New Relic with multi-location probes and alerting.
Overview
This skill streamlines the process of setting up synthetic monitoring, enabling proactive performance tracking for applications. It guides the user through defining key monitoring scenarios and configuring alerts to ensure optimal application performance and availability.
How It Works
- Identify Monitoring Needs: Determine the critical endpoints, user journeys, and APIs to monitor based on the user's application requirements.
- Design Monitoring Scenarios: Create specific monitoring scenarios for uptime, transactions, and API performance, including frequency and location.
- Configure Monitoring: Set up the synthetic monitoring tool with the designed scenarios, including alerts and dashboards for performance visualization.
When to Use This Skill
This skill activates when you need to:
- Implement uptime monitoring for a web application.
- Track the performance of critical user journeys through transaction monitoring.
- Monitor the response time and availability of API endpoints.
Examples
Example 1: Setting up Uptime Monitoring
User request: "Set up uptime monitoring for my website example.com."
The skill will:
- Identify example.com as the target endpoint.
- Configure uptime monitoring to check the availability of example.com every 5 minutes from multiple locations.
Example 2: Monitoring API Performance
User request: "Configure API monitoring for the /users endpoint of my application."
The skill will:
- Identify the /users endpoint as the target for API monitoring.
- Set up monitoring to track the response time and status code of the /users endpoint every minute.
Best Practices
- Prioritize Critical Endpoints: Focus on monitoring the most critical endpoints and user journeys that directly impact user experience.
- Set Realistic Thresholds: Configure alerts with realistic thresholds to avoid false positives and ensure timely notifications.
- Regularly Review and Adjust: Periodically review the monitoring configuration and adjust scenarios and thresholds based on application changes and performance trends.
Show full SKILL.md (171 more words)Show less
Integration
This skill can be integrated with other plugins for incident management and alerting, such as those that handle notifications via Slack or PagerDuty, allowing for automated incident response workflows based on synthetic monitoring results.
Prerequisites
- Access to synthetic monitoring platform (Pingdom, Datadog, New Relic)
- List of critical endpoints and user journeys in ${CLAUDE_SKILL_DIR}/monitoring/endpoints.yaml
- Alerting infrastructure configuration
- Geographic monitoring location requirements
Instructions
- Identify critical endpoints and user journeys to monitor
- Design monitoring scenarios (uptime, transactions, API checks)
- Configure monitoring frequency and locations
- Set up performance and availability thresholds
- Configure alerting for failures and degradation
- Create dashboards for monitoring visualization
Output
- Synthetic monitoring configuration files
- Uptime check definitions for endpoints
- Transaction monitoring scripts
- Alert rule configurations
- Dashboard definitions for monitoring status
Error Handling
If synthetic monitoring setup fails:
- Verify monitoring platform credentials
- Check endpoint accessibility from monitoring locations
- Validate transaction script syntax
- Ensure alert channel configuration
- Review threshold definitions
Resources
- Synthetic monitoring best practices
- Uptime monitoring service documentation
- Transaction monitoring script examples
- Alert threshold tuning guides
© 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 4 other files (scripts, references, assets) in skills/.curated/setting-up-synthetic-monitoring of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- assets/README.md
- references/README.md
- scripts/README.md
- scripts/setup_monitor.py
Open the folder on GitHubat commit cfae287
Compare with similar skills
Setting Up Synthetic Monitoring 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 |
|---|---|---|---|---|---|---|
| Setting Up Synthetic Monitoring this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Frontend Session Rcagrafana/skills | 282 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Synthetic Monitoringpetrkindlmann/qa-skills | 170 | — | ~5.8k | Automated safety check: Pass | MIT | |
| Mz Release SignoffMaterializeInc/materialize | 6.4k | — | ~7.2k | Automated safety check: Pass | Custom licence | |
| Axiom Alerting Managementopenclaw/clawhub | 9.5k | — | ~2.1k | Automated safety check: Pass | MIT | |
| UI Architectopenobserve/openobserve | 22k | — | ~16k | Automated safety check: Notes | AGPL-3.0 |
Similar skills
- Official
Synthetic Monitoring
petrkindlmann/qa-skills
Scheduled probes that run CONTINUOUSLY after release. An agent skill from petrkindlmann/qa-skills.
Mz Release Signoff
MaterializeInc/materialize
Verify a release candidate on the Grafana dashboards and sign off in release.
Axiom Alerting Management
openclaw/clawhub
Creates and manages Axiom monitors and notifiers end to end through the v2 API, with scripts for each CRUD operation and a recommended create-validate-tune workflow.
UI Architect
openobserve/openobserve
ALWAYS use this skill for ANY change to the OpenObserve web UI (web/) — even a single-line UI modification.
KubeEye Cluster Inspection
kubesphere/kubesphere
Deploys KubeEye on KubeSphere and writes InspectRule and InspectPlan resources to inspect cluster health, then retrieves the inspection reports.
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 Setting Up Synthetic Monitoring
What does Setting Up Synthetic Monitoring do?
Setup synthetic monitoring for proactive performance tracking including uptime checks, transaction monitoring, and API health. Setting Up Synthetic Monitoring is an agent skill from jeremylongshore/tons-of-skills-marketplace. Setup synthetic monitoring for proactive performance tracking including uptime checks, transaction monitoring, and API health.
When should I use Setting Up Synthetic Monitoring?
Setting Up Synthetic Monitoring fits situations like: implementing availability monitoring; tracking critical user journeys; with phrases like setup synthetic monitoring; configure health checks.
How do I install Setting Up Synthetic Monitoring in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill setting-up-synthetic-monitoring -a claude-code`. Or copy the skill folder (skills/.curated/setting-up-synthetic-monitoring in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/setting-up-synthetic-monitoring in your project. Claude Code loads it when a task matches its description.
How do I install Setting Up Synthetic Monitoring in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill setting-up-synthetic-monitoring -a codex`. Or copy the skill folder (skills/.curated/setting-up-synthetic-monitoring in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/setting-up-synthetic-monitoring in your project. Codex loads it when a task matches its description.
Can I use Setting Up Synthetic Monitoring 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 setting-up-synthetic-monitoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setting-up-synthetic-monitoring, .gemini/skills/setting-up-synthetic-monitoring, .github/skills/setting-up-synthetic-monitoring and .opencode/skills/setting-up-synthetic-monitoring in your project.
What does Setting Up Synthetic Monitoring need to run?
Going by SKILL.md and its folder, Setting Up Synthetic Monitoring needs Python for the scripts in its folder. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(curl:*), Bash(monitoring:*). Compatibility (from SKILL.md): Designed for Claude Code.
Does Setting Up Synthetic Monitoring 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 Setting Up Synthetic Monitoring 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 Setting Up Synthetic Monitoring use?
Setting Up Synthetic Monitoring 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 Setting Up Synthetic Monitoring use?
About 1.1k tokens (SKILL.md is roughly 4.4k 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 18 tokens, read only when the agent opens those files.
What are the alternatives to Setting Up Synthetic Monitoring?
Skills that share tags, products or a category with Setting Up Synthetic Monitoring: Frontend Session Rca (grafana/skills, 282 stars), Synthetic Monitoring (petrkindlmann/qa-skills, 170 stars), Mz Release Signoff (MaterializeInc/materialize, 6.4k stars) and Axiom Alerting Management (openclaw/clawhub, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Setting Up Synthetic Monitoring?
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.