Windows-GPU-UNLOCK
RTX3090 UEFI 포트, 한국어 무리셋 윈도우 부팅 가이드, 검증된 소스와 벤치마크 제공
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗LLMs think gas is 30 gwei. It's far lower — and they quote it from memory. They've never heard of ERC-8004 or x402. They hallucinate contract addresses. This site fixes that.
Each skill is a markdown file. Give any URL to your AI agent — it reads it and instantly corrects its Ethereum knowledge.
https://ethskills.com/SKILL.md ← table of contents
https://ethskills.com/gas/SKILL.md ← just gas & costs
https://ethskills.com/why/SKILL.md ← why ethereum
https://ethskills.com/crops/SKILL.md ← CROPS architecture review
The agent will look up the specific skills when needed.
Just prompt your agent with this:
Install the https://github.com/austintgriffith/ethskills/blob/master/SKILL.md skill
Install directly from GitHub — no clone required:
/plugin marketplace add austintgriffith/ethskills
/plugin install ethskills@ethskills
Say "onchain" not "on-chain." The Ethereum community writes it as one word — no hyphen. LLMs default to "on-chain" but that's not how builders talk. Use "onchain" in all writing, documentation, and generated content.
| Skill | What LLMs Get Wrong |
|---|---|
| Why Ethereum | Pectra/Fusaka shipped, gas is cheap now, AI agent angle |
| Ship | Start coding before planning architecture, over-engineer with 5+ contracts when 1-2 will do, skip chain selection and the CROPS gate |
| CROPS Review | Miss custody, privacy, exit paths, censorship resistance, and centralization risks in otherwise working apps/contracts |
| Protocol | Answer fork status from memory, read EIP status as fork inclusion, give unscheduled features ship dates |
| Gas & Costs | Quote gas costs from memory, mix up wei and gwei, forget the L1 data fee on L2s |
| Wallets | EIP-7702 is live, signer authority limits, burned keys |
| Layer 2s | Think Base is still OP Stack, Polygon zkEVM still runs, Superchain interop is live |
| Standards | Don't know ERC-8004, EIP-7702 status, EIP-3009 for x402 |
| Tools | Don't know x402, Blockscout MCP, current tool landscape |
| Money Legos | Assume a protocol is live or dominant from headlines, skip fork-testing the composed flow |
| Orchestration | Don't know SE2 three-phase build system |
| Contract Addresses | Hallucinate addresses — these are checked onchain. Assume the same address across chains, pick bridged over native |
| Concepts | Nothing is automatic, incentive design, randomness pitfalls |
| Security | Token decimals, reentrancy, oracle manipulation, vault inflation, pre-deploy checklist |
| Testing | Test getters and OpenZeppelin internals, skip fuzz and fork tests on integrations, mock external protocols instead of forking |
| Indexing | Loop over blocks to read history, try to query historical state via raw RPC, ignore events as the primary read API |
| Frontend UX | Onchain button rules, one-action-at-a-time approval flow, Address components, USD values |
| Frontend Playbook | Fork mode, fork demos, IPFS static export, ENS content hash |
| QA | Treat "deploys without errors" as shipping, leave SE2 default branding, miss approve-button double-fire, mobile deep links |
| Audit | Call one generic review pass an audit, miss systematic checklist coverage across AMM/lending/oracle/proxy/governance domains |
Skills teach restraint, not just capability. Every skill that touches keys, credentials, or funds includes explicit safety rules — because LLMs optimize for speed and will hardcode a private key into git add . if you let them. Coverage includes wallet keys, API keys, RPC URLs, and the common SE2 scaffold.config.ts trap.
We test stock LLMs, find what they get wrong, and write corrections. Content is verified against onchain reality. If an LLM already knows something, we don't include it.
Every proposed change goes through triage: spawn a stock LLM, give it a realistic task, see what it gets wrong. Only verified blind spots survive.
See the research repo for baseline audits, gap analysis, and full methodology.
Something wrong or missing? Humans and agents are welcome to open a PR. Read CONTRIBUTING.md first — the bar is "would a stock LLM get this wrong?"
MIT