메뉴
Ships a terminal simplification claim with a single-file or gist core, section-by-section teaching, efficiency vs essence split, and optional commit-granular video or repo twin. Use when demystifying a stack or teaching from minimal runnable code.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Top-level entry for the AK.skill pack: routes agent-era public-idea work to the right sub-skill (paradigm surface, proof, idea file, hype+discipline, irreducible core, scoreboard loop, year review). Use when the user invokes /ak, says AK.skill, or needs a single checklist for shipping a thread, README, talk, teaching repo, or annual stack essay without picking modules manually.
Welds bold forecasts to plain limits, one real verification habit, paradox framing (capable yet brittle), and honest benchmark skepticism. Use when writing about agents, autonomy, or LLMs and preserving trust in the same breath as excitement.
Turns attention spikes into durable agent-readable idea files: invariants, policy vs mechanism, paste blocks for tools, and discussion-friendly hosting. Use when a post goes viral but the value is the pattern, not a frozen app or private dotfiles dump.
Surfaces paradigm shifts in public technical writing: open with lived workflow change, name one abstraction (optional metaphor or era label), and list the real stack honestly. Use when posting threads, READMEs, or memos about how tools or the profession are changing.
Pairs strong claims with the smallest falsifiable proof (script, gist, notebook, or runbook) and labels bare-bones baselines clearly. Use when arguing that a capability crossed a threshold or when credibility must fit in one link.
Defines a cheap-to-evaluate score and one mutable workspace so agents iterate from numbers; separates immutable prep from editable experiment files. Use when designing overnight experiment loops, autoresearch-style harnesses, or metric-gated agent iteration.
| name | irreducible-core |
| description | Ships a terminal simplification claim with a single-file or gist core, section-by-section teaching, efficiency vs essence split, and optional commit-granular video or repo twin. Use when demystifying a stack or teaching from minimal runnable code. |
Distilled pattern: ship a terminal simplification claim—this is the smallest honest container for the idea—then teach through the file section by section.
When the full stack is too large for one file, pair the minimal core with a repo whose git history is the syllabus (one conceptual step per commit), plus a long-form video or post that walks commits in order. Centralize errata and FAQ next to the repo so the teaching artifact stays maintainable.
