monitor SKILL.md skillA

monitor from parcha-ai/agentrun is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add parcha-ai/agentrun/monitor@git:20261114.34f0a79

Pins git:20261114.34f0a79 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
parcha-ai/agentrun
Path
packages/serve/templates/market-monitor/skills/monitor/SKILL.md
Versions recorded
8
Latest version
git:20261114.34f0a79, committed Nov 14, 2026
First version recorded
Nov 9, 2026
Size
15,049 bytes
Repository stars
1,181
License
Apache-2.0

Write the weekly competitor and market digest. Check each watched company's changelog, pricing and news for events that happened inside the lookback window, on a fixed small fetch plan, drop repeats, date and link every item with a one-line "so what", then post it through the saved Slack or email MCP server, or return it. Use for the scheduled weekly run and for "what changed at our competitors", "run the market digest".

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Monitor

You write one digest of what changed at the companies the owner watches. You read the web; you never read the channel the
digest goes to, nor any mailbox. Your one write is posting the digest, once, to the one destination your instructions
name. Your answer is the JSON in step 8.

`MONITOR.md`, beside this file, says what counts as a change and what never does, and the digest's limits. Read it as
a file before step 2. Your `# Learned` notes, when you have them, are the owner's standing preferences ("skip junior
job posts", "their status page is not a launch"): they win over `MONITOR.md` where the two differ.

## Inputs

- The companies, topics, channel and lookback from your instructions. A company is a name and a domain; one written
  without a domain, find its official site with its one search.
- Run history: a scheduled run is handed its trigger's last completed digest after its message, as a fenced json block
  under "The result of this trigger's last completed run" (the digest's own fields: window, items, digest). A manual run
  has one only when a person pastes it into the message.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qblvfu33sfe5ptos/6dc6debc3bcaa52e171a4479f4aa74c42c3204d33a7e024b3e931ba9c41ed9e2.json

Then /plugin install monitor@markdownregistry-qblvfu33sfe5ptos in Claude Code. It installs git:20261114.34f0a79, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add parcha-ai/agentrun/monitor@sha256:6dc6debc3bcaa52e

The line at the top of this page pins the label git:20261114.34f0a79, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_qblvfu33sfe5ptos.svg)](https://markdownregistry.com/a/art_qblvfu33sfe5ptos)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in parcha-ai/agentrun/monitor since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of monitor from somewhere else? Ask it: where did my monitor come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 8 versions of this file, between Nov 9, 2026 and Nov 14, 2026, more than one a day.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261114.34f0a79 latest2026-11-14 34f0a79 15,049 BA view · diff
git:20261114.c8abb972026-11-14 c8abb97 14,824 BA view · diff
git:20261114.701212c2026-11-14 701212c 14,750 BA view · diff
git:20261111.ac919552026-11-11 ac91955 14,782 BA view · diff
git:20261110.fe825862026-11-10 fe82586 14,597 BA view · diff
git:20261109.75349aa2026-11-09 75349aa 13,899 BA view · diff
git:20261109.08fb7572026-11-09 08fb757 12,820 BA view · diff
git:20261109.1829f3d2026-11-09 1829f3d 12,295 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (15049 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

parcha-ai/agentrun · 1,181 stars · license Apache-2.0 · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_qblvfu33sfe5ptos
GET https://markdownregistry.com/api/v1/resolve?ref=parcha-ai/agentrun/monitor
GET https://markdownregistry.com/api/v1/blob/6dc6debc3bcaa52e171a4479f4aa74c42c3204d33a7e024b3e931ba9c41ed9e2

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from parcha-ai/agentrun

code-review-knowledge SKILL.md skill
parcha-ai/agentrun · .agents/skills/code-review-knowledge/SKILL.md · Invariants and past defect patterns of Parcha-ai/agentrun, keyed by path glob. The code reviewer reads it from the base…
git:20261112.d69251a · audit A · 1,181 stars
gh-stack SKILL.md skill
parcha-ai/agentrun · .agents/skills/gh-stack/SKILL.md · Manage AgentRun's native GitHub PR stacks with gh-stack: inspect, restack, publish and coordinate gated queue…
git:20261114.994ab02 · audit A · 1,181 stars
ship-pr SKILL.md skill
parcha-ai/agentrun · .agents/skills/ship-pr/SKILL.md · The one gate every pull request to Parcha-ai/agentrun passes before it goes to the maintainer: fresh base, local…
git:20261114.994ab02 · audit A · 1,181 stars
ship SKILL.md skill
parcha-ai/agentrun · .agents/skills/ship/SKILL.md · Ship AgentRun work through implementation, proof, review and its merge queue. Use for a named PR, an existing branch or…
git:20261114.994ab02 · audit A · 1,181 stars
AGENTS.md AGENTS.md file
parcha-ai/agentrun · AGENTS.md
git:20261114.994ab02 · audit B · 1,181 stars
CLAUDE.md CLAUDE.md file
parcha-ai/agentrun · CLAUDE.md
git:20261004.5bdb930 · audit B · 1,181 stars
agentrun-setup SKILL.md skill
parcha-ai/agentrun · docs/SKILL.md · Onboard to AgentRun Cloud, local setup or self-hosting by creating a new agent or connecting an existing Claude Code or…
git:20261117.15f5a02 · audit A · 1,181 stars
agentrun-cli SKILL.md skill
parcha-ai/agentrun · packages/agentrun/skills/agentrun-cli/SKILL.md · Onboard and manage AgentRun agents from a shell. Connect existing Claude Code or Codex setups locally or remotely…
git:20261115.039beb7 · audit B · 1,181 stars
agentrun-author SKILL.md skill
parcha-ai/agentrun · packages/dsl/skills/author/SKILL.md · Build, inspect, and run a small AgentRun workflow when the user says /agentrun <task>, asks to use AgentRun, or asks to…
v1.3.0 · audit A · 1,181 stars
agentrun-serve SKILL.md skill
parcha-ai/agentrun · packages/serve/skills/agentrun-serve/SKILL.md · Onboard to AgentRun by starting a new agent, observing agents already running in a backend or terminal, or connecting…
git:20261116.7011bb4 · audit B · 1,181 stars
llms.txt@packages/serve/src llms.txt file
parcha-ai/agentrun · packages/serve/src/llms.txt
git:20261106.9961274 · audit A · 1,181 stars
desktop-computer SKILL.md skill
parcha-ai/agentrun · packages/serve/src/workspace/kind-skills/desktop/SKILL.md · Use a desktop computer (a Mac, or a Linux desktop) through computer_observe, computer_act, computer_screenshot and a…
git:20261115.25c2fb6 · audit A · 1,181 stars

Every file in parcha-ai/agentrun

Other files named monitor

monitor Claude Code subagent
agentworkforce/relay · .claude/agents/monitor.md · Use for monitoring setup, alerting configuration, observability, and performance analysis.
git:20260814.67b52ca · audit A · 1,134 stars
monitor SKILL.md skill
microsoft/amplifier-bundle-skills · skills/monitor/SKILL.md · Run a bounded, self-checking polling loop (sleep -> check -> decide, repeat) WITHOUT ENDING THE TURN. The turn ends…
v1.0.0 · audit A · 12 stars
monitor SKILL.md skill
compforge/devloop · devloop/skills/monitor/SKILL.md · Inspect PR/MR state or reclaim repository caches and worktrees with repocli. Use for requested cleanup or…
git:20261111.30e4de9 · audit A · 4 stars

Browse by kind, by grade A, or by owner.