Taifeng is a pre-alpha agent microkernel (v2026.9.17.23) with 10 tools spanning financial data, user input collection, skill orchestration, and script execution. Critical gaps: 7 of 10 tools lack visible input schemas in the provided source; descriptions are present but often terse (Chinese, 10-30 chars); no documented output schemas; no error handling guidance; no parameter type constraints or validation rules visible. The codebase shows sophisticated audit/journal infrastructure (audit_tool.py) but tool definitions themselves are underspecified for LLM consumption. Tools like `run_script` (IRREVERSIBLE risk) and `kill_skill` (DESTRUCTIVE) lack confirmation patterns or permission gates. Composition is reasonable (spawn_skill + await_skills + join_skill form a coherent async pattern), but parameter documentation is minimal.
等待已发起的子 skill 完成。
派发调用子 skill,支持权限审批 + hook 拦截。
按固定汇率把金额从一种货币换算到另一种。
汇聚子 skill 结果。
终止子 skill。
查询某股票代码的最新价格(美元)。
采集工具:弹出结构化表单(问答题 + 单选 enum + 多选 array),用户填写后续跑。
执行 Python / Shell 脚本,支持多语言 executor。
搜索可用的 skill 候选,返回 JSON 列表(skill_id + confidence)。
7 of 10 tools have no visible input schema in source code. request_user_input, spawn_skill, await_skills, join_skill, kill_skill, search_skills, call_skill, run_script lack explicit JSON Schema definitions with type and property constraints.
Descriptions are terse (10-30 chars in Chinese) and lack LLM-actionable context. E.g., '并发分离发起子 skill' (spawn_skill) does not explain when to use it, what it returns, or how it chains with await_skills. Descriptions should be 50-200 chars with WHAT/WHEN/RETURN guidance.
Destructive/irreversible tools (kill_skill, run_script) lack confirmation patterns, dry-run support, or permission gates. kill_skill terminates child skills with no undo; run_script executes arbitrary code. No recovery guidance or audit trail visible in tool definitions.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 35 | 2026-07-28+ | v2 |
并发分离发起子 skill。
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., skill_id from search_skills, result structure from run_script). Output documentation is missing entirely.
No error handling guidance visible. Tools do not document retryable vs. fatal errors, invalid input constraints, or recovery steps. E.g., run_script (IRREVERSIBLE) provides no guidance on timeout, permission denial, or script failure modes.