跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 skill-upper

Skill Upper

Capture and review Agent Skill observations, and create, run, diagnose, or iteratively improve Skill evaluations (evals) with the skill-up CLI / 采集和审核 Agent Skill 观察,并使用 skill-up CLI 创建、运行、诊断或持续改进 Skill 评测. Use when the user asks to record explicitly attributed Skill usage or feedback; review observations; turn an approved observation into a regression case; evaluate, test, regress, verify, fix, improve, iterate, or evolve a Skill; add or strengthen eval cases; write eval.yaml/case.yaml; run skill-up run/validate/list-cases/report/import/init; or migrate from Anthropic evals.json. Observation capture and review require either the Codex skill-up plugin or an observer-enabled DSH skill-up plugin; evaluation remains multi-engine.

947 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

官方 description 用英文写明「Skill Upper」做什么。中文介绍不改写这段原文,能力边界以文件结构与下方原文为准。

何时用

用户要求记录明确归属的技能使用或反馈; 审查观测结果; 将核准的观测结果变成回归案例; 评估、测试、倒退、核实、修正、改进、去除或演化技能; 增加或加强eval案例; 写入 eval.yaml/ case.yaml; 运行

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:use-skill-up-cli、Language Policy、Language Rules for Generated Artifacts、What is skill-up、When to trigger、Main flow (follow this order strictly)。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/install.md、references/observations.md、references/migrate-anthropic.md、assets/eval.yaml.tmpl、assets/case.yaml.tmpl、references/judge-types.md,属于带资源的技能包,这些文件按需再读。

use-skill-up-cliLanguage PolicyLanguage Rules for Generated ArtifactsWhat is skill-upWhen to triggerMain flow (follow this order strictly)Observation capture mode (optional)Observation input mode (optional)Step 0: Make sure skill-up is installedStep 0.5 (optional): User config and telemetryStep 1: Locate the target SkillStep 2: Scaffold the evals (only when none exist)

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
skill-upper
description
Capture and review Agent Skill observations, and create, run, diagnose, or iteratively improve Skill evaluations (evals) with the skill-up CLI / 采集和审核 Agent Skill 观察,并使用 skill-up CLI 创建、运行、诊断或持续改进 Skill 评测. Use when the user asks to record explicitly attributed Skill usage or feedback; review observations; turn an approved observation into a regression case; evaluate, test, regress, verify, fix, improve, iterate, or evolve a Skill; add or strengthen eval cases; write eval.yaml/case.yaml; run skill-up run/validate/list-cases/report/import/init; or migrate from Anthropic evals.json. Observation capture and review require either the Codex skill-up plugin or an observer-enabled DSH skill-up plugin; evaluation remains multi-engine.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 9
  • references/install.md
  • references/observations.md
  • references/migrate-anthropic.md
  • assets/eval.yaml.tmpl
  • assets/case.yaml.tmpl
  • references/judge-types.md
  • references/eval-yaml.md
  • references/case-yaml.md
  • references/cli.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「skill-upper」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-c7980a23159ce298-%E9%AB%98%E7%BA%A7%E6%8A%80%E8%83%BD.html
请存为 .cursor/skills/skill-upper/SKILL.md 或 .claude/skills/skill-upper/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/alibaba/skill-up 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/alibaba/skill-up' --list

npx skills add 'https://github.com/alibaba/skill-up' --skill 'skill-upper'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: skill-upper description: "Capture and review Agent Skill observations, and create, run, diagnose, or iteratively improve Skill evaluations (evals) with the skill-up CLI / 采集和审核 Agent Skill 观察,并使用 skill-up CLI 创建、运行、诊断或持续改进 Skill 评测. Use when the user asks to record explicitly attributed Skill usage or feedback; review observations; turn an approved observation into a regression case; evaluate, test, regress, verify, fix, improve, iterate, or evolve a Skill; add or strengthen eval cases; write eval.yaml/case.yaml; run skill-up run/validate/list-cases/report/import/init; or migrate from Anthropic evals.json. Observation capture and review require either the Codex skill-up plugin or an observer-enabled DSH skill-up plugin; evaluation remains multi-engine." --- # use-skill-up-cli Help the user evaluate and evolve Agent Skills through the `skill-up` CLI. Manual: ## Language Policy **Default to English when responding to the user. If the user writes in Chinese (or any other language), switch to that language and stay consistent with the user's input throughout the session.** Detection rules (highest priority first): 1. The user explicitly specifies a language in the current message (e.g. "answer in English" / "用中文回答") → follow the user's instruction. 2. The natural language used in the user's current message → match it. 3. None of the above → use English (default). Regardless of the response language, technical identifiers in this SKILL — CLI commands, `eval.yaml` / `case.yaml` field names, report field names, etc. — MUST stay in their original English form. Do not translate them. ### Language Rules for Generated Artifacts When creating or editing `eval.yaml`, `case.yaml`, grading scripts, README snippets, final replies, or any other user-visible artifact, treat the language of the user's current message as the output language for this turn: - If the user asks in Chinese, write the final response and all generated natural-language content in Chinese, including YAML comments, `title`, `description`, `input.prompt`, `expect` keywords, and `judge.criteria`. - If the user asks in English, write the final response and all generated natural-language content in English, including YAML comments, `title`, `description`, `input.prompt`, `expect` keywords, and `judge.criteria`; do not leave Chinese or CJK characters in generated case files. - If the target Skill itself is written in Chinese but the user asks in English, translate the Skill's functional intent into English test prompts and assertions instead of copying Chinese prose from the target Skill or templates. - In an English context, deterministic keywords in `rule_based` cases, including `expect.must_contain` and `judge.success.output_contains`, must also be English keywords. Translate terms such as `资源泄漏`, `关闭`, and `异常处理` into `resource leak`, `close`, and `exception handling`; do not write bilingual parentheticals like `"资源" (resources)`. - Keep technical identifiers unchanged, such as `schema_version`, `environment.type`, `engine.name`, `rule_based`, `agent_judge`, `script_path`, file paths, and commands. - Generated YAML comments must use field-leading comments. Keep each comment short: one line for field meaning, plus one line for options only when useful. - When listing options in comments, keep enum values unchanged, such as `none | opensandbox | docker` and `rule_based | agent_judge | script`. - Treat `assets/*.tmpl` as structural references only. Rewrite placeholder prose and comments into the current output language; in an English context, translate or remove every Chinese comment and Chinese placeholder before writing generated files. - `skill-up import` uses the CLI conversion path and does not preserve template comments; do not promise commented YAML for import-generated files. - In an English context, after generating all files but BEFORE submitting the final reply, you **MUST perform a CJK self-check**: open every `evals/cases/*.yaml` and `evals/eval.yaml` and scan for CJK characters (Unicode ranges `\u4e00-\u9fff\u3400-\u4dbf\uf900-\ufaff\u3000-\u303f\uff00-\uffef`), including but not limited to `title`, `description`, `input.prompt`, `expect` keywords, `judge.criteria`, and YAML comments. If any CJK character is found, **replace it with an equivalent English expression before finishing the task**. This step is mandatory and must not be skipped. ## What is skill-up `skill-up` is an evaluation CLI for Agent Skill authors. It installs the Skill into a real Agent Engine (Claude Code, Codex, qodercli, etc.), spins up an execution environment for each case, runs the prompt, then grades the result via declared rules / LLM judges / custom scripts, and finally produces a report. Typical layout: ``` my-skill/ SKILL.md evals/ eval.yaml cases/ .yaml fixtures/ ``` ## When to trigger Use this skill in any of the following situations: - The user asks to "run / evaluate / verify / test this skill". - The user asks to "fix / improve / iterate / evolve this skill" from eval failures. - The user wants to "add evals, test cases, or regression cases to a skill". - The user asks to record explicitly attributed Skill usage, evidence, or feedback. - The user wants to review captured Skill observations or turn approved feedback into a regression case. - The user wants to edit `eval.yaml` / `case.yaml`, or asks you to choose an appropriate `judge` type. - The user mentions `skill-up run/validate/list-cases/report/import/init`. - The user wants to migrate from Anthropic `evals.json` to skill-up. - The current working directory contains `evals/eval.yaml` or `evals/evals.json` and the user wants to run it. ## Main flow (follow this order strictly) ### Observation capture mode (optional) Use this mode when the user asks to record the current Skill interaction or feedback and observation tools are available. It requires either a current Codex release with the `codex-skill-up` plugin and lifecycle-hook support, or DSH with the skill-up plugin's observer explicitly enabled. Do not retrofit observation capture onto the pinned Codex 0.80.0 evaluation adapter. If the user asks how to install either host plugin, or the required observation tools are missing and the user asks to enable them, read `references/install.md` under "安装 observation host plugin(可选)". Do not install or enable a plugin unless the user asks. Claude Code, qodercli, Qwen Code, and other Agent Engines are not supported for this observation workflow. This restriction does not apply to normal `skill-up` evaluation runs, which remain multi-engine. 1. Attribute the interaction only when the user explicitly references a Skill (for example, `$my-skill`) or the responsible Skill is otherwise known with certainty. 2. In Codex, if explicit attribution is absent but certain, call `mark_skill_invocation` once with the Skill name and optional version. DSH derives exact attribution from its durable `/skill` injection or successful `skill` tool result; do not add inferred attribution. 3. In Codex, use `attach_skill_evidence` only for references that help reproduce or evaluate the behavior. Prefer paths and short summaries over copied file contents. 4. In Codex, use `record_skill_feedback` during the observed turn. In DSH, wait until the completed turn has produced an observation, then use `record_observation_feedback` with its ID. Never invent sentiment or comments. Both adapters redact common credential shapes before local persistence, but still avoid sending secrets to marker tools. If the request is capture-only, stop after recording it; do not edit, evaluate, commit, or publish a Skill unless the user also asks for that work. ### Observation input mode (optional) When the request starts from a captured Skill observation, read `references/observations.md` first. Use the available observation tools to inspect and preview the observation, require explicit approval for the exact candidate, write it only after approval, and then continue at Step 4. If the request does not start from an observation, use the normal flow below. ### Step 0: Make sure skill-up is installed Before doing anything, verify `skill-up` is available: ```bash command -v skill-up && skill-up --version ``` If a version is printed, continue. If you see `command not found`, on **macOS / Linux**: ```bash curl -fsSL https://raw.githubusercontent.com/alibaba/skill-up/main/install.sh | bash export SKILL_UP_VERSION=v0.1.0 curl -fsSL https://raw.githubusercontent.com/alibaba/skill-up/main/install.sh | bash export INSTALL_DIR="$HOME/bin" curl -fsSL https://raw.githubusercontent.com/alibaba/skill-up/main/install.sh | bash ``` > **Platform:** `skill-up` currently supports **macOS / Linux** only; Windows is not supported. After installing, run `skill-up --version` again. If the command is still missing, add `~/.local/bin` to `PATH`. More details, including optional Codex and DSH observation host plugins: `references/install.md`. ### Step 0.5 (optional): User config and telemetry For OTLP defaults, `runtime_kwargs` (e.g. OpenSandbox `base_url`), etc.: ```bash skill-up init skill-up init --local skill-up init --print skill-up init --force ``` Precedence (low → high): embedded empty defaults < user config < project `.skill-up.yaml` < `--config`. `SKILL_UP_CONFIG` can point at the user config file (env var name is historical). See the upstream README "User config". ### Step 1: Locate the target Skill 1. Identify the root directory of the target Skill (the directory containing `SKILL.md`). Search in this priority: user path → nearest `SKILL.md` upward from CWD → recently viewed files. 2. Read the target `SKILL.md` for scope, triggers, and dependencies. If the Skill is Chinese but the user writes in English, translate capabilities into English for prompts and assertions. 3. Check `evals/`: - `evals/eval.yaml` exists → Step 4 (optionally Step 3). - Only `evals/evals.json` → `references/migrate-anthropic.md` (`skill-up run --auto` or `skill-up import`). - Nothing → Step 2. ### Step 2: Scaffold the evals (only when none exist) - Copy `assets/eval.yaml.tmpl` to `/evals/eval.yaml`. - Copy `assets/case.yaml.tmpl` to `/evals/cases/.yaml`. Adapt language per "Language Rules for Generated Artifacts". In an English context, it is **prohibited** to copy Chinese placeholder text from the templates into generated files — all prose must be rewritten in English. The Chinese in the templates is for structural reference only, not to be carried over. Preserve short field-leading comments in generated YAML. In Chinese context, rewrite those comments into Chinese while keeping field names and enum values in English. Selection guidelines: - `environment.type`: use `none` for pure-text Skills; use `opensandbox` when you need a remote sandbox (set `OPENSANDBOX_API_KEY`, put non-secrets in `environment.kwargs`). - `engine.name` + `engine.model`: default `claude_code`; `model` is optional. For `qodercli`, often omit `model`. - `judge.type`: `rule_based` (preferred), `script`, `agent_judge` (expensive) — see `references/judge-types.md`. - Case ID = filename without `.yaml`; prompts should exercise real Skill value. See `references/eval-yaml.md` and `references/case-yaml.md`. ### Step 3: Fill the gaps (when evals already exist) - `skill-up list-cases ` - Review `eval.yaml` and representative cases; avoid `agent_judge` abuse. - Add or edit YAML under `cases/` as needed. ### Step 4: Validate the configuration ```bash skill-up validate /evals/eval.yaml ``` Expect: `✓ eval.yaml is valid (loaded N case(s))`. ### Step 5: Prepare credentials Priority: `--api-key` > env (`ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, `QODER_PERSONAL_ACCESS_TOKEN`) > `~/.skill-up/credentials.yaml`. ```bash printenv | grep -E 'ANTHROPIC_API_KEY|OPENAI_API_KEY|QODER_PERSONAL_ACCESS_TOKEN' ``` If missing, **stop and ask**; do not write secrets into YAML without consent. For `opensandbox`, also ensure `OPENSANDBOX_API_KEY` (and related env) as needed. ### Step 6: Run the evaluation ```bash skill-up run /evals/eval.yaml ``` | Scenario | Command | | -------------------------------- | ------------------------------------- | | Subset | `--include-case-name "basic-*"` | | Exclude | `--exclude-case-name "*-flaky"` | | HTML report | `--format html` | | Engine override | `--engine codex --model openai/gpt-4` | | Parallelism | `--parallelism 4` (1–256) | | Anthropic JSON | `--auto` | | Stability/flakiness sampling | `--iteration 3` | | Auto-append after last iteration | `--iteration 0` (default behavior) | | Verbose | `-v`, `-vv` | Exit `0` = all passed; `1` = failure or error — suitable for CI. When an explicit positive `--iteration N` runs more than one sample, inspect the terminal's simple current-command summary for lines like `case_a: 3 trials, 2 PASS, 1 FAIL -> flaky`. ### Step 7: Interpret the report Artifacts under `/-workspace/iteration-N/`: - `result.json`, `benchmark.json`, optional `report.html` - `/with_skill/grading.json`, `outputs/` Summarize: pass rate and timing; for failures, case id, assertion `text`, and `evidence`; benchmark deltas if enabled; offer HTML path or `skill-up report result.json --format html`. ### Step 8: Evolve the Skill when requested Only enter this loop when the user asks to fix, improve, iterate, or evolve the target Skill. If the user only asks to evaluate or report results, stop after Step 7 without modifying it. 1. Diagnose failures from `result.json`, `grading.json`, and output evidence. 2. Fix `SKILL.md` or supporting files when the Skill behavior is incorrect. 3. Add or refine eval cases when coverage is missing. 4. Do not weaken valid assertions merely to make a failure pass. 5. Rerun failed cases first, then run the full eval suite. 6. Continue until the evals pass or clearly report what remains blocked. ## Command quick reference | Command | Purpose | | --------------------------------------------- | --------------------------------- | | `skill-up validate ` | Validate before `run`. | | `skill-up list-cases ` | List cases. | | `skill-up run [eval.yaml]` | Run evals. | | `skill-up run --auto` | Run from `evals/evals.json`. | | `skill-up report --format html` | Re-render reports. | | `skill-up import ` | Convert Anthropic format to YAML. | | `skill-up init` | Write user-config template. | | `skill-up debug judge ` | Debug judge. | | `skill-up debug report ` | Debug report. | Full flags: `references/cli.md`. ## Common pitfalls - Model IDs vs proxy aliases — preserve what works for the user's `base_url`. - `opensandbox` without `OPENSANDBOX_API_KEY` — auth failures. - Chinese `expect.must_contain` vs English model output — align language in prompts/assertions. - Abusing `agent_judge`. - Anthropic `evals.json` expectations → default `agent_judge`; use `import` + hand edits for deterministic checks. - Paths relative to Skill root (`SKILL.md` directory). - `--iteration 0` appends one run after the latest existing iteration without summarizing history; positive `--iteration N` runs N samples of the selected cases and, when N > 1, prints a simple stability/flakiness summary covering only samples from the current command. ## References - `references/install.md` - `references/eval-yaml.md` - `references/case-yaml.md` - `references/judge-types.md` - `references/cli.md` - `references/migrate-anthropic.md` - `references/observations.md` - `assets/eval.yaml.tmpl`, `assets/case.yaml.tmpl`

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…