AgentStack
SKILL verified MIT Self-run

Karpathy Gist Check

skill-mujtaba3b-mutwo-skills-karpathy-gist-check · by mujtaba3B

Check Andrej Karpathy's public gists for new or updated entries since the last seen baseline. Trigger automatically on session start when `~/.claude/karpathy-last-check` is missing or older than 30 days. Also invoke manually when the user says "check karpathy gists", "/karpathy-gist-check", or "any new karpathy posts". Defers if the user is mid-task; runs at most once per session.

No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-mujtaba3b-mutwo-skills-karpathy-gist-check

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Karpathy Gist Check? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Karpathy gist check

Karpathy publishes design patterns and mental models for working with LLMs in his public gists. They sometimes change how core working patterns (like the LLM Wiki) should be set up. This check runs on a ~30 day cadence to surface new or updated gists.

When to run

  • Auto-trigger: On session start, if ~/.claude/karpathy-last-check is missing or its date is more than 30 days before today.
  • Manual trigger: User asks to check Karpathy's gists.
  • Defer if the user is mid-task. Wait for a natural break. Better to skip a check than derail active work.
  • At most once per session, even if the staleness file still looks stale after the first run.

Procedure

  1. Use /browse (from gstack) to fetch https://gist.github.com/karpathy and extract the gist list: id, title, last-active date.
  2. Compare against ~/.claude/karpathy-seen.json (the seen baseline).
  3. If anything is new or has been updated since the seen baseline:
  • List new/changed gists, one line each (id title last_active).
  • Ask the user whether to read any of them now or defer.
  1. Overwrite ~/.claude/karpathy-last-check with today's date (YYYY-MM-DD).
  2. Overwrite ~/.claude/karpathy-seen.json with the fresh snapshot.

First-time setup

If ~/.claude/karpathy-seen.json doesn't exist:

  • Fetch the gist list fresh.
  • Treat all current gists as the baseline (do NOT surface them as "new"; the protocol is for changes going forward).
  • Write the baseline and today's date as above.

Notes

  • Use /browse, not WebFetch, per the gstack rule in ~/.claude/CLAUDE.md.
  • Date format for karpathy-last-check: YYYY-MM-DD on a single line, no trailing newline issues.
  • karpathy-seen.json shape: { "snapshot_date": "YYYY-MM-DD", "gists": [{"id": "...", "title": "...", "last_active": "..."}] }. Future runs diff against gists[] and report last_active as the date column.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.