LL

lizhao888/llm-building-map

Productivity workflow

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

0 stars Качество 58 Тренд 14MIT

An agent skill: how LLMs are actually built — data pipeline, post-training, evaluation — with every claim mapped to a timestamp in the source lecture.

Обзор

An agent skill that gives you a — and, more usefully, a way to tell whether a claim about one is credible. Distilled from Yann Dubois' Stanford CS229 guest lecture Building Large Language Models (Summer 2024). Every claim in the skill is mapped to a timestamp in references/lecture-notes.md, so you can check it rather than trust it. 📖 Prefer to read it as an article? How LLMs are actually built — on dev.to Most "how LLMs work" explainers stop at "transformers + attention". The parts that decide whether a model is good — the data pipeline, the post-training recipe, the evaluation setup, the systems work — are usually glossed over. This skill covers those parts, in the form an agent can actually use: - : a structure for AI explainer content that isn't hand-waving. - : three questions that deflate most benchmark claims (which benchmark, against whom, judged by what). - : why "let's fine-tune it on our docs" rarely does what people expect.

README

Показан фрагмент оригинального README. Открыть оригинал.

llm-building-map

A skill file that tells an agent how an LLM is actually built — and gives you three questions that deflate most benchmark claims.

git clone https://github.com/lizhao888/llm-building-map.git
cp -r llm-building-map ~/.claude/skills/      # Claude Code
cp -r llm-building-map ~/.hermes/skills/research/   # Hermes Agent

Distilled from Yann Dubois’ Stanford CS229 guest lecture Building Large Language Models (Summer 2024). Every claim in the skill is mapped to a timestamp in references/lecture-notes.md, so you can check it rather than trust it.

📖 Prefer to read it as an article? How LLMs are actually built — on dev.to · 中文版(掘金)

Why this exists

Most “how LLMs work” explainers stop at “transformers + attention”. The parts that decide whether a model is good — the data pipeline, the post-training recipe, the evaluation setup, the systems work — are usually glossed over.

This skill covers those parts, in the form an agent can actually use:

  • Explain: a structure for AI explainer content that isn’t hand-waving.
  • Audit: three questions that deflate most benchmark claims (which benchmark, against whom, judged by what).
  • Scope: why “let’s fine-tune it on our docs” rarely does what people expect.

What’s inside

SKILL.md                          # the skill itself (five components, pipeline, post-training, eval)
references/lecture-notes.md       # evidence map: claim → timestamp in the source lecture (English)
references/lecture-notes.zh-CN.md # same content, in Chinese

Install

Claude Code / Claude Skills

git clone https://github.com/lizhao888/llm-building-map.git
mkdir -p ~/.claude/skills
cp -r llm-building-map ~/.claude/skills/llm-building-map

Hermes Agent

cp -r llm-building-map ~/.hermes/skills/research/llm-building-map
# Windows: %LOCALAPPDATA%\hermes\skills\research\llm-building-map

Any other agent that reads SKILL.md: drop the directory wherever that agent looks for skills. The frontmatter follows the common name + description convention.

The 60-second version

Component What it decides Who optimizes it
Architecture capacity and shape academia
Objective what “good” means during training academia
Data what the model has seen industry
Evaluation whether you can tell it improved industry
Открыть полный README на GitHub

Рекомендуемые инструменты

Попробуйте другой запрос или уберите фильтр.

Установка

npx skillfish add lizhao888/llm-building-map
Новичок в MCP? Начните с руководства на mcpskill.org →