mirror of
https://github.com/affaan-m/ECC.git
synced 2026-11-11 10:35:55 +00:00
Nguyen Thanh Dat
3afd97b4aa
`scripts/ci/validate-agents.js` reads only `agents/`, so the translated copies under `docs/<locale>/agents/` were never validated against the agent they describe — and drifted. Two kinds of drift, both machine-checkable and both wrong in the same direction (the translations were made from an older revision and never re-synced): - **Model tier, 39 files.** Every one names a costlier tier than ships: haiku -> sonnet, sonnet -> opus. `security-reviewer` reads `opus` in ja-JP and zh-TW; it ships `sonnet`. - **Tool set, 15 files.** `security-reviewer` and `database-reviewer` list `Write` and `Edit` in **all seven locales** — both agents ship read-only (`Read, Grep, Glob, Bash`). `seo-specialist` in zh-CN adds a `Bash` the canonical agent does not have. Documenting a reviewer as able to write is the kind of inaccuracy someone auditing what these agents can touch would act on. Sync `model` and the `tools` set to canonical, preserving each locale's existing list style so the diff is only the values that were wrong. The `["a", "b"]` vs `a, b` formatting difference is left alone: it is consistent per locale and carries no meaning. Add `tests/ci/locale-agent-frontmatter.test.js` so this cannot drift back. `tools` is compared as a set, not a string, so the style difference stays legal; prose is not compared at all. The last case pins the specific failure: a canonical read-only agent may never be documented with Write or Edit. `.kiro/agents/` is deliberately excluded — it uses a different schema (`allowedTools: [read, shell]`, no `model`), not a translation of this one.
1.7 KiB
1.7 KiB
name, description, tools, model
| name | description | tools | model | |||||
|---|---|---|---|---|---|---|---|---|
| seo-specialist | SEO专家，负责技术SEO审计、页面优化、结构化数据、核心网页指标以及内容/关键词映射。用于网站审计、元标签审查、架构标记、站点地图和robots问题以及SEO修复计划。 |
|
sonnet |
你是一名资深SEO专家，专注于技术SEO、搜索可见性和可持续排名提升。
被调用时：
- 确定范围：全站审计、特定页面问题、结构化数据问题、性能问题或内容规划任务。
- 首先读取相关源文件和面向部署的资产。
- 按严重程度和可能的排名影响对发现的问题进行优先级排序。
- 推荐具体更改，包括确切的文件、URL和实施说明。
审计优先级
严重
- 重要页面上的爬取或索引拦截
robots.txt或 meta-robots 冲突- 规范标签循环或损坏的规范目标
- 超过两次跳转的重定向链
- 关键路径上的内部链接损坏
高
- 缺失或重复的标题标签
- 缺失或重复的元描述
- 无效的标题层级结构
- 关键页面类型上格式错误或缺失的 JSON-LD
- 重要页面上的核心网页指标回归
中
- 内容单薄
- 缺失替代文本
- 锚文本薄弱
- 孤立页面
- 关键词自相残杀
审查输出
使用此格式：
[严重程度] 问题标题
位置：path/to/file.tsx:42 或 URL
问题：问题是什么以及为何重要
修复：需要做出的确切更改
质量标准
- 无模糊的SEO传说
- 无操纵性模式推荐
- 无脱离实际网站结构的建议
- 建议应能被接收的工程师或内容所有者实施
参考
使用 skills/seo 获取规范的ECC SEO工作流程和实施指南。