원클릭으로 Manus에서 모든 스킬 실행

stack-year-review

스타0

포크0

업데이트2026년 4월 9일 02:15

Structures longform year or phase reviews: stack at t0 vs t1, personally notable bullets, benchmark fatigue honesty, paradox TL;DR, and deep links. Use when synchronizing audience mental models after a fast-moving year in tech.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

ERerGB

ERerGB/AK.skill

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Stack Year Review

Distilled pattern: once a year (or after a phase change), publish a before/after picture of the production stack plus a personal highlight reel—notable papers, releases, and intuitions—closed with tensions instead of a single hype arc.

When to use

The field moved fast and your audience only saw fragments; you want to synchronize mental models.
You need a longform piece that still rewards skimming.

Steps

Draw the stack at t₀ and t₁ — What did “default serious stack” look like at year start vs end? Boxes and arrows beat prose.
List what actually moved capability — RL, reasoning traces, tool use, evals, product layer—whatever you believe mattered; keep each bullet falsifiable.
Name one ontology shift — How should readers feel the new object? (e.g., from “training animals” to “summoning ghosts”—use your own metaphor; do not copy others’ wording.)
Admit benchmark fatigue — If leaderboards diverged from felt reality, say so and point to what you trust instead (tasks, demos, production metrics).
Product / ecosystem paragraph — How did the “app layer” thicken? (IDEs, agents, vertical bundles.) Ask the open economic question: who captures value?
TL;DR with paradox — One paragraph that holds both “smarter than expected” and “dumber than expected” (or your field’s equivalent)—signals intellectual honesty.
Deep links — Point to your longer essays or talks for readers who want rabbit holes.

Anti-patterns

A list of headlines anyone could copy from TechCrunch.
One-note optimism or one-note doom.
No personal timestamp (“as practitioner/builder/researcher, I noticed…”).

Output shape

Diagram or bullet stack: then vs now.
5–15 “notable” bullets (mixed scope: infra + product + science).
TL;DR: tension + forward-looking open field.

이 저장소의 다른 Skills

같은 저장소

ERerGB/AK.skill

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.

2026-04-090

hype-discipline-pairing

ERerGB/AK.skill

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.

2026-04-090

idea-file-handoff

ERerGB/AK.skill

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.

2026-04-090

irreducible-core

ERerGB/AK.skill

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.

2026-04-090

paradigm-surface

ERerGB/AK.skill

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.

2026-04-090

proof-in-miniature

ERerGB/AK.skill

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.

2026-04-090

name	stack-year-review
description	Structures longform year or phase reviews: stack at t0 vs t1, personally notable bullets, benchmark fatigue honesty, paradox TL;DR, and deep links. Use when synchronizing audience mental models after a fast-moving year in tech.

Stack Year Review

When to use

The field moved fast and your audience only saw fragments; you want to synchronize mental models.
You need a longform piece that still rewards skimming.

Steps

Draw the stack at t₀ and t₁ — What did “default serious stack” look like at year start vs end? Boxes and arrows beat prose.
List what actually moved capability — RL, reasoning traces, tool use, evals, product layer—whatever you believe mattered; keep each bullet falsifiable.
Name one ontology shift — How should readers feel the new object? (e.g., from “training animals” to “summoning ghosts”—use your own metaphor; do not copy others’ wording.)
Admit benchmark fatigue — If leaderboards diverged from felt reality, say so and point to what you trust instead (tasks, demos, production metrics).
Product / ecosystem paragraph — How did the “app layer” thicken? (IDEs, agents, vertical bundles.) Ask the open economic question: who captures value?
TL;DR with paradox — One paragraph that holds both “smarter than expected” and “dumber than expected” (or your field’s equivalent)—signals intellectual honesty.
Deep links — Point to your longer essays or talks for readers who want rabbit holes.

Anti-patterns

A list of headlines anyone could copy from TechCrunch.
One-note optimism or one-note doom.
No personal timestamp (“as practitioner/builder/researcher, I noticed…”).

Output shape

Diagram or bullet stack: then vs now.
5–15 “notable” bullets (mixed scope: infra + product + science).
TL;DR: tension + forward-looking open field.