HyperFrames by HeyGen
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
This repo is a collection of 28 skills
The skillbook for recursive self-improvement (RSI). NVIDIA's latest proof, unpacked with timeless engineering. Distilled from the OpenAI harness engineering hackathon winner's zero-touch method.If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/lilmgenius-paperthin)MCP servers that connect the AI to services for the same work
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Same kind of work, ordered like the Skills list
| This one paperthin | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| Maker | LilMGenius | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skills | 28 | 1 | 1 | 1 | 1 |
| GitHub stars | 1,452 | 111,852 | 67,796 | 32,458 | 29,958 |
| Last code change | Nov 15, 2026 | Nov 17, 2026 | Nov 13, 2026 | Jun 24, 2026 | Oct 30, 2026 |
| License | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
28 skills (instruction sets) by LilMGenius that an AI reads and follows · not an MCP server
Install only the ones you use. Open a skill to see how to install it
If you want every one, let the AI install them in one go. Know 2 things first
Uploading to Claude on the web and apps: you need 28 uploads, one ZIP per skill. Open each skill in the list below to download it
Checked against official docs Nov 12, 2026 · Source: support.claude.com, code.claude.com, learn.chatgpt.com, cursor.com
When data lands with a thin ask (files, a repo, a paste, a chat scrollback), read it and propose what the user is trying to do with it for them to confirm. Use the moment material arrives without a fully-formed ask, or when the ask reads thinner than the data suggests.
Carve guardrail-adjacent items out of scope with safe alternatives before risk-adjacent work starts, then run the safe remainder at full strength in a fresh subagent that only ever sees the carved prompt, never the risky input. Use when a task includes stealth, scraping, privacy, IP, policy, licens…
Rebuild the human's lost context on a project from live state, in plain language: what needs them, what changed, what new words mean. Use when the human returns after a gap, says they can't follow the project anymore, asks what happened or what a term means, or before deciding what to do next when…
Cut an artifact that has accreted into bloat, prose or code, to its load-bearing density, meaning and behavior preserved. In prose: padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement. In code, behind green tests: comments that restate the code, commented-out co…
Remove the em and en dashes an agent drops into running prose where a comma, colon, parentheses or a sentence break belongs, from a user-owned scope, keeping hyphens, ranges and dashes that separate a label from its text.
Make durable artifacts portable by replacing incidental stack, vendor, model, CLI, path, quota, or harness nouns with the mechanism they mean, while keeping provenance, runbooks, and tool-subject claims concrete.
Verify reality-grounded claims against external sources in both directions before they ship: could the 'absurd' be real, could the 'obvious' be false or long-established? Use whenever an artifact, or the sentence you are about to write, asserts something as plausible, realistic, absurd, novel, or i…
No description from the maker
Attack a plan, design, or argument like you want it to fail before you commit real effort; return the single load-bearing objection and the cheapest experiment that would prove it matters, not a checklist. User-invoked on purpose: a hate-it reflex always in the agent's reach would bias it toward de…
User-invoked read-only pass for checking whether the current direction is tunnel-visioned: strip the session's bait, fan out 2 to 5 same-model fresh reads, and report divergence first without treating convergence as proof; or, when asked, re-read one decision at a larger scale and return linked exp…
Audit any eval, metric, experiment, or benchmark for leakage: does external ground-truth enter independently, or are the model, scorer, and designer just confirming a result no outside truth ever produced? Use before trusting any 'how we'll know it worked', including an A/B, a holdout, a score, a v…
Size a task's run before spending it: the cheapest sufficient capability tier (fast, standard, frontier) and the reasoning effort within it, on a neutral scale that binds to whatever levels the model exposes. Use when work seems over- or under-powered, costly, ambiguous, or high-risk, or asks which…
Read the live cycle state and return the single highest-leverage next best action, not a menu. Use when a project is between phases, the author asks what to do next, too many valid threads are open, or the work needs re-entry into frame, build, drive, re0-memo, hate, re0-work, or ship.
No description from the maker
Refresh an existing artifact into the current best v0. Use when the user asks to clean up, sync up, dedupe, de-noise, smooth, rewrite, or update an artifact after iteration; when nearby artifacts may have drifted; or when changes in one place should be reflected across related artifacts while keepi…
Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, place a late commit in time order on a linear history, and take a rejected or duplicate commit out of a range, so `git log` alone tells the story. User-invoked: run it once you've decided to commit.
Run repeated cycles of build, QA, re0-memo and re0-work while preserving learning and letting code die. Use for long agentic projects where progress must be measured by quality-cleared templates, reusable modules, and eliminated anti-patterns rather than hours spent or features accumulated.
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary, and measure how far the work stands from its objective. Use after a build, QA pass, demo, user complaint or correction, a request the user had to repeat, a user askin…
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing.
Open a paperthin iteration's casebook before re0-loop's first turn, seeded with real content the moment the folder exists, never an empty directory. User-invoked, paperthin-only: assumes the full skill package installed. Run when opening a new build cycle in this repo.
Walk a pending change in the repository it runs in through that repository's release procedure end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.
Keep one paperthin install current and loaded once: move an old skills.sh install onto the Claude Code or Codex plugin, clear the session-start notice older releases wired, set up the daily update job where skills.sh stays, and bring that install to the full current catalog, all shown and confirmed…
Restart a project or artifact from v0 while preserving only proven lessons, contracts, gates, vocabulary, real-surface tests, and negative corpus. Use when the foundation is wrong, accumulated code is misleading progress, or a new pass should learn from the old one without inheriting its accidental…
No description from the maker
No description from the maker
Cold-read the artifact you're focused on from a fresh, zero-context sub-session to confirm it stands on its own: a shower-thought reset for accumulated session bias. Use when a long session has worn away your fresh eyes and you can no longer tell whether the artifact in focus is clear to someone wi…
After you create or change an artifact or skill, taste-test it with our own skills instead of trusting your in-session judgment. Use right after writing or editing anything, before calling it done, committing, or handing it off.
Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or plat…
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Claude CodeCodexCursorOpenCode
From the maker’s README and the folders in the repo
This repo has 28 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.