AF long-running-agent
长时间运行智能体编排框架。让AI智能体能够跨会话持续工作并完成复杂任务。 使用场景： - 用户说 "创建一个新项目"、"开始一个项目"、"新建任务"、"启动项目" - 用户说 "继续项目"、"继续工作"、"接着做"、"继续开发" - 用户说 "更新进度"、"记录进度"、"保存进度" - 用户说 "项目状态"、"查看进度"、"做到哪了" - 用户说 "列出项目"、"所有项目"、"我有哪些项目" - 用户说 "暂停项目"、"存档项目" - 用户需要执行多步骤、长时间、跨会话的任务 - 用户需要AI持续追踪工作进度和上下文 - 用户需要AI记住之前尝试过但失败的方法 核心功能： - 创建新项目（自动生成 PROJECT.md, CHANGELOG.md） - 继续项目（自动读取进度，从断点继续） - 更新进度（自动更新 CHANGELOG.md） - Ralph Loop 自动推进（解决智能体惰性） - 多项目管理 - 项目状态概览 - 失败方法记录（防止重复尝试）
As a process F 35/100 · Will not run — References files that are not bundled: examples/task-planner-demo/
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: examples/task-planner-demo/
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: examples/task-planner-demo/
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1263 tokens
- 100Running it twice. No mutating operations
- low 13 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -214 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 438: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (18 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.