

























AI Agent 时代诞生的知识转化方法论与工具集,核心是将书籍、专业文章、文档等静态文本知识,通过结构化蒸馏与重构,转化为大语言模型(如 Claude Code)可直接调用、按需执行的标准化 Skill(技能包),最终实现「书本静态知识 → AI 可执行能力」的闭环。
它不是简单的书籍摘要或读书笔记,而是对知识进行「可执行化」改造 —— 把叙事性的内容,拆解为 AI 能理解、能套用、能引导用户落地的结构化单元。
Create LLM-powered autonomous agents and intelligent assistants tailored to your business and personal needs. From script-free customer service chatbots to fully independent agents operating seamlessly in the background, AI-powered assistants represent a breakthrough in machine intelligence. In AI Agents in Action, you'll master a proven framework for developing practical agent.
│ cheatsheet.md
│ glossary.md
│ patterns.md
│ SKILL.md
│ xx.txt
│
└─chapters
ch01-introduction-to-agents.md
ch02-harnessing-llms.md
ch03-engaging-gpt-assistants.md
ch04-multi-agent-systems.md
ch05-empowering-agents-actions.md
ch06-autonomous-assistants.md
ch07-agent-platform-nexus.md
ch08-agent-memory-knowledge.md
ch09-prompt-engineering-prompt-flow.md
ch10-reasoning-evaluation.md
ch11-planning-feedback.md
或
skillhub install lanham-ai-agents
Author: Micheal Lanham | Pages: ~346 | Chapters: 11 | Generated: 2026-06-16
Without arguments — load core frameworks for reference
With a topic — ask about behavior trees, RAG, multi-agent, prompt engineering, or another indexed topic; I find and read the relevant chapter
With chapter — ask for ch05; I load that specific chapter
Browse — ask "what chapters do you have?" to see the full index
When you ask about a topic not covered in Core Frameworks below, I will read the relevant chapter file before answering.
Use this spectrum to select the right autonomy level for any use case:
Direct → simple QA, no tools needed
Proxy → LLM reformulates prompts for another model (e.g., ChatGPT → DALL-E)
Agent + Confirmation → tool use with user approval step
Autonomous → independent planning, decision-making, execution
Think of agent autonomy as a spectrum, not a binary. Match the level to the risk/reward profile of the task.
Use AutoGen for conversational, exploratory multi-agent systems (group chat, proxy patterns). Use CrewAI when you need structured, role-based enterprise workflows (sequential/hierarchical task management). Think of multi-agent systems as teams of specialists — a coordinator delegates to experts.
OpenAI Function Calling is the standard pattern for LLM-tool integration. Define functions with name + description + parameters → LLM decides when to call → execute → return results. Semantic Kernel (SK) adds structure: semantic functions (prompt templates) for "what" and "why", native functions (code) for "how". Use the semantic service layer pattern to cleanly separate LLMs from external APIs.
Use behavior trees when you need structured, reusable control over agent decision-making. Five primary nodes cover most patterns: Selector (try until one succeeds), Sequence (run all, fail on any failure), Action (execute), Condition (check), Decorator (control/block). Agentic Behavior Trees (ABTs) use LLMs to dynamically construct and modify the tree. Always implement Control Barrier Functions as safety guardrails.
Use Retrieval Augmented Generation (RAG) whenever agents need external knowledge. Two phases: Index (load → chunk → embed → store) and Query (embed query → similarity search → augment prompt). Knowledge is document-based (external); memory is experience-based (from interactions). Both augment prompts through retrieval.
Six OpenAI strategies map to agent components: Write Clear Instructions → persona/behavior, Provide Reference Text → knowledge/RAG, Split Complex Tasks → subtask decomposition, Give Models Time to "Think" → reasoning/planning, Use External Tools → function calling, Test Changes Systematically → evaluation. Always iterate — prompt engineering is never one-shot.
Scale reasoning depth to problem complexity: Direct/Few-Shot for simple tasks, Chain of Thought (CoT) for multi-step reasoning, Self-Consistency for high-reliability needs (multiple paths, majority vote), Tree of Thought (ToT) for complex exploration. Multiple reasoning paths always beat a single path.
Planning separates agents from chatbots. Use sequential planning when tasks have dependencies (output feeds next step). Build custom JSON planners using prompt engineering to generate step-by-step plans from available functions. Implement feedback mechanisms (corrective, suggestive, epistemic) for continuous improvement. Always set safety guardrails — agents with autonomous actions can go rogue.
Book-to-Skill 对书本知识的重构并非简单提炼,而是围绕「可执行」进行多维度拆解,这也是其核心价值所在:
在传统教育与个人成长领域,「Book to Skill」也是一个通用学习理念:它指向「从信息到能力」的转化,强调打破「阅读 = 学习」的误区 —— 书本只是知识的载体,而非技能本身;只有通过实践、反馈、重复迭代,把书本上的理论转化为可落地的行动能力,才算完成了知识的真正吸收。AI 语境下的 Book-to-Skill,本质是用技术加速了这一过程:把原本需要人花大量时间消化、提炼、练习的知识,直接蒸馏为可随时调用的能力模块。
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。