agent-builder
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or autonomous AI (3) need help with capabilities, subagents, planning, or skill mechanisms (4) ask about Claude Code, Cursor, or similar agent internals (5) want to build agents for business, research, creative, or operational tasks Keywords: agent, assistant, autonomous, workflow, tool use, multi-step, orchestration
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- agent-builder
- description
- Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or autonomous AI (3) need help with capabilities, subagents, planning, or skill mechanisms (4) ask about Claude Code, Cursor, or similar agent internals (5) want to build agents for business, research, creative, or operational tasks Keywords: agent, assistant, autonomous, workflow, tool use, multi-step, orchestration
02 资源文件 5
- 参考文档references/agent-philosophy.md7.8 KB
- 脚本references/minimal-agent.py4.1 KB
- 脚本references/subagent-pattern.py7.6 KB
- 脚本references/tool-templates.py7.7 KB
- 脚本scripts/init_agent.py9.7 KB
03 SKILL.md 正文
Agent Builder
Build AI agents for any domain - customer service, research, operations, creative work, or specialized business processes.
The Core Philosophy
The model already knows how to be an agent. Your job is to get out of the way.
An agent is not complex engineering. It's a simple loop that invites the model to act:
LOOP:
Model sees: context + available capabilities
Model decides: act or respond
If act: execute capability, add result, continue
If respond: return to user
That's it. The magic isn't in the code - it's in the model. Your code just provides the opportunity.
The Three Elements
1. Capabilities (What can it DO?)
Atomic actions the agent can perform: search, read, create, send, query, modify.
Design principle: Start with 3-5 capabilities. Add more only when the agent consistently fails because a capability is missing.
2. Knowledge (What does it KNOW?)
Domain expertise injected on-demand: policies, workflows, best practices, schemas.
Design principle: Make knowledge available, not mandatory. Load it when relevant, not upfront.
3. Context (What has happened?)
The conversation history - the thread connecting actions into coherent behavior.
Design principle: Context is precious. Isolate noisy subtasks. Truncate verbose outputs. Protect clarity.
Agent Design Thinking
Before building, understand:
- Purpose: What should this agent accomplish?
- Domain: What world does it operate in? (customer service, research, operations, creative...)
- Capabilities: What 3-5 actions are essential?
- Knowledge: What expertise does it need access to?
- Trust: What decisions can you delegate to the model?
CRITICAL: Trust the model. Don't over-engineer. Don't pre-specify workflows. Give it capabilities and let it reason.
Progressive Complexity
Start simple. Add complexity only when real usage reveals the need:
| Level | What to add | When to add it |
|---|---|---|
| Basic | 3-5 capabilities | Always start here |
| Planning | Progress tracking | Multi-step tasks lose coherence |
| Subagents | Isolated child agents | Exploration pollutes context |
| Skills | On-demand knowledge | Domain expertise needed |
Most agents never need to go beyond Level 2.
Domain Examples
Business: CRM queries, email, calendar, approvals Research: Database search, document analysis, citations Operations: Monitoring, tickets, notifications, escalation Creative: Asset generation, editing, collaboration, review
The pattern is universal. Only the capabilities change.
Key Principles
- The model IS the agent - Code just runs the loop
- Capabilities enable - What it CAN do
- Knowledge informs - What it KNOWS how to do
- Constraints focus - Limits create clarity
- Trust liberates - Let the model reason
- Iteration reveals - Start minimal, evolve from usage
Anti-Patterns
| Pattern | Problem | Solution |
|---|---|---|
| Over-engineering | Complexity before need | Start simple |
| Too many capabilities | Model confusion | 3-5 to start |
| Rigid workflows | Can't adapt | Let model decide |
| Front-loaded knowledge | Context bloat | Load on-demand |
| Micromanagement | Undercuts intelligence | Trust the model |
Resources
Philosophy & Theory:
references/agent-philosophy.md- Deep dive into why agents work
Implementation:
references/minimal-agent.py- Complete working agent (~80 lines)references/tool-templates.py- Capability definitionsreferences/subagent-pattern.py- Context isolation
Scaffolding:
scripts/init_agent.py- Generate new agent projects
The Agent Mindset
From: "How do I make the system do X?" To: "How do I enable the model to do X?"
From: "What's the workflow for this task?" To: "What capabilities would help accomplish this?"
The best agent code is almost boring. Simple loops. Clear capabilities. Clean context. The magic isn't in the code.
Give the model capabilities and knowledge. Trust it to figure out the rest.
04 同仓库更多 Skills
seedance-prompt-en
Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.
onepage-pdf
Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file/report/proposal into a "single-page PDF", "long PDF", "不分页 PDF", "单页 PDF", "长图式 PDF", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.
native-feel-cross-platform-desktop
Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include "cross-platform desktop", "Electron alternative", "Tauri vs native", "WebView wrapper", "near-native performance", "Raycast architecture", "WebKit/WebView2 quirks", "WKWebView", "system tray app", "global hotkey app", "launcher app". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.
gstack
Router for the gstack skill suite. (gstack)
fireworks-tech-graph
Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent/memory, or concept map - and export as SVG+PNG. Trigger on: "画图" "帮我画" "生成图" "做个图" "架构图" "流程图" "可视化一下" "出图" "generate diagram" "draw diagram" "visualize" or any system/flow description the user wants illustrated.
dbs-video-extract
接收抖音、小红书、微信视频号等短视频链接或分享文案,查询作品/账号数据并提取语音文字稿,按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用;运行前检查 TikHub 与轻抖使用凭证,缺少时用新手能理解的方式引导购买和安全配置。