peer-readacross SKILL.md skillA
peer-readacross from ccplugins/awesome-claude-code-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ccplugins/awesome-claude-code-plugins/peer-readacross@git:20260812.efb14f8Pins git:20260812.efb14f8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ccplugins/awesome-claude-code-plugins
- Path
plugins/alphai/skills/peer-readacross/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260812.efb14f8, committed Aug 12, 2026
- Size
- 1,966 bytes
- Repository stars
- 1,012
- License
- Apache-2.0
Compare two tickers and surface the cross-read between them using the AlphaAI MCP. Use when the user asks to "compare X and Y", "NVDA vs AMD", "what does <peer>'s news mean for <ticker>", or wants the read-across between two related names (competitors, supplier/customer, same theme).
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
# Peer read-across
When two names are linked — competitors, a supplier and its customer, two plays
on one theme — the interesting signal is the **read-across**: a peer's print that
resets the other's setup. `alphai_pair_analysis` is built for exactly this.
## Steps
1. **Resolve both tickers.** If given company names, map them with
`alphai_tickers(q=...)`. Any symbol that isn't a recognized active ticker
comes back in `unknown_tickers` and contributes no rows — surface that.
2. **Run the comparison.** Call `alphai_pair_analysis(ticker_a, ticker_b)`. It
returns three things: news naming **both** companies (the shared read-across),
plus each ticker's **own** recent news for context.
3. **Tighten on request.** Raise `min_relevance` (default 4) for only the
strongest items, or `limit` for more rows per list.
## Output
- **Shared story** — the news naming both names: what links them right now and
which way the read-across cuts (does A's news help or hurt B?).
- **{Ticker A}** — 2–3 of its own top stories, one-liners.
- **{Ticker B}** — same.
- **Net read** — one or two sentences: are they moving together or diverging, and
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hqd4erp74zvwaw2f/e204cea15c614ab57f9ce4554467ade0933a9860bb58c0f0f547621b3aa2db19.json
Then /plugin install peer-readacross@markdownregistry-hqd4erp74zvwaw2f in Claude Code. It installs git:20260812.efb14f8, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add ccplugins/awesome-claude-code-plugins/peer-readacross@sha256:e204cea15c614ab5The line at the top of this page pins the label git:20260812.efb14f8, 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.
[](https://markdownregistry.com/a/art_hqd4erp74zvwaw2f)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in ccplugins/awesome-claude-code-plugins/peer-readacross 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 peer-readacross from somewhere else? Ask it: where did my peer-readacross 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 1 version of this file, committed on Aug 12, 2026.
Watch this file (sign in, one email per new version)
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.
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.
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.
Installed this file, say at .claude/skills/peer-readacross/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1966 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
ccplugins/awesome-claude-code-plugins · 1,012 stars · license Apache-2.0 · pushed 2026-08-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hqd4erp74zvwaw2f GET https://markdownregistry.com/api/v1/resolve?ref=ccplugins/awesome-claude-code-plugins/peer-readacross GET https://markdownregistry.com/api/v1/blob/e204cea15c614ab57f9ce4554467ade0933a9860bb58c0f0f547621b3aa2db19
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.