investor-lenses SKILL.md skillA
investor-lenses from hkuds/vibe-trading is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hkuds/vibe-trading/investor-lenses@git:20260829.1af4019Pins git:20260829.1af4019 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hkuds/vibe-trading
- Path
agent/src/skills/investor-lenses/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260829.1af4019, committed Aug 29, 2026
- First version recorded
- Aug 4, 2026
- Size
- 9,786 bytes
- Repository stars
- 38,485
- License
- MIT
Named investor reasoning frameworks packaged as reusable analytical lenses — 12 lenses (deep value, quality franchise, inversion, scuttlebutt growth, GARP, cycle positioning, debt cycle, forensic short, cost drag, right-business, weak-system contrarian, three questions) that stack on top of evidence already gathered, each with ordered priority signals, hard disqualifiers, and documented failure modes.
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
# Investor Lenses ## What a lens is A lens is a **reasoning procedure**: a fixed, ordered set of questions plus explicit veto rules, distilled from one investor's publicly published methodology. It is applied *after* the evidence exists — it does not gather data and does not care where the data came from. The value of a lens is that it is **opinionated and therefore falsifiable**. A lens tells you, before you look at the answer, which signals it ranks first and which facts make it walk away. Two lenses disagreeing on the same evidence is the product, not a bug: the disagreement localizes exactly which assumption the decision rests on. ## What a lens is NOT - **Not investment advice.** Every lens output is an analytical exercise. - **Not the named person's opinion.** Each lens is a reconstruction, in our own words, of a methodology that investor has described publicly. It is not written by them, not endorsed by them, and may diverge from what they would say today. - **Not a universal truth test.** A lens verdict is conditional on the lens. "Fails the Graham lens" and "bad investment" are different statements. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_35u4f5uaatdgdzvj/1ed207815a993d142d98db22348f0a2c64b55e38be49e89489bcadb4edc5a214.json
Then /plugin install investor-lenses@markdownregistry-35u4f5uaatdgdzvj in Claude Code. It installs git:20260829.1af4019, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add hkuds/vibe-trading/investor-lenses@sha256:1ed207815a993d14The line at the top of this page pins the label git:20260829.1af4019, 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_35u4f5uaatdgdzvj)
3 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 hkuds/vibe-trading/investor-lenses 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 investor-lenses from somewhere else? Ask it: where did my investor-lenses 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 2 versions of this file, between Aug 4, 2026 and Aug 29, 2026, about one every 25 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260829.1af4019 latest | 2026-08-29 | 1af4019 | 9,786 B | A | view · diff |
| git:20260804.7018083 | 2026-08-04 | 7018083 | 9,786 B | A | view |
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/investor-lenses/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 (9786 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
hkuds/vibe-trading · 38,485 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_35u4f5uaatdgdzvj GET https://markdownregistry.com/api/v1/resolve?ref=hkuds/vibe-trading/investor-lenses GET https://markdownregistry.com/api/v1/blob/1ed207815a993d142d98db22348f0a2c64b55e38be49e89489bcadb4edc5a214
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.