agent-experience

Agent Skills › See-Sol-Lab/DeepSeekGUI › agent-experience

agent-experience

GitHub

提供模型工具定义与技能设计的最佳实践，优化上下文加载、发现机制及约束可见性，提升信息检索效率并控制提示词开销。

.agents/skills/agent-experience/SKILL.md See-Sol-Lab/DeepSeekGUI

Trigger Scenarios

编写或修改面向模型的工具定义设计技能、上下文加载或多步工作流

Install

npx skills add See-Sol-Lab/DeepSeekGUI --skill agent-experience -g -y

More Options

Non-standard path

npx skills add https://github.com/See-Sol-Lab/DeepSeekGUI/tree/main/.agents/skills/agent-experience -g -y

Use without installing

npx skills use See-Sol-Lab/DeepSeekGUI@agent-experience

指定 Agent (Claude Code)

npx skills add See-Sol-Lab/DeepSeekGUI --skill agent-experience -a claude-code -g -y

安装 repo 全部 skill

npx skills add See-Sol-Lab/DeepSeekGUI --all -g -y

预览 repo 内 skill

npx skills add See-Sol-Lab/DeepSeekGUI --list

SKILL.md

Frontmatter

{
    "name": "agent-experience",
    "metadata": {
        "date": "2026-09-11"
    },
    "description": "Use when writing or changing a model-facing tool definition (name, description, parameter schema, or its system-prompt section), and when designing skills, context loading, or multi-step workflows, to make information discoverable and use context efficiently."
}

Start with minimal context: expose purpose, available actions, and constraints first; load detailed instructions when needed.
Make discovery explicit: every deferred resource needs a clear description and a reliable way to retrieve it.
Keep critical constraints visible: permissions, destructive effects, and required validation should appear before the relevant action.
Prefer bounded outputs: return concise results with identifiers or paths for retrieving details; avoid dumping entire logs or documents.
Use locality: include a bounded amount of likely needed adjacent context with an operation’s result. For example, deliver a thread reply with a few preceding messages. Mark omissions and truncation explicitly, and provide a way to retrieve more.
Evaluate total work: saving context is useful only if it does not cause more searches, repeated reads, or mistakes.

Tool definitions

Delete obvious constraints. Omit rules the model learns from the call result, such as a missing file failing to read or a failed send not being delivered.
Describe behavior, not implementation. State what the tool does and returns; omit internal mechanisms, output markers the model sees in results, and enforcement details.
Put parameter rules on the parameter. Defaults, ranges, pairing, and when-to-set rules belong in that parameter's description or schema; a description that varies with configuration usually means the varying part belongs to a parameter.
Say each fact once. Do not repeat the tool definition in its system-prompt section, a parameter description in the tool description, or one tool's rules in another tool.
Measure the change. Compare first-turn prompt tokens before and after a tool-definition change.