菜单
Seek out and update agent discovery files as conventions evolve. Use when agent ecosystems add new ways to state behavior, skills, or rules; when discovery files need revision; or when maintaining FOR_AGENTS.md, .cursorrules, docs/for-agents.md, docs/agent-discovery.md.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | agent-convention-sync |
| description | Seek out and update agent discovery files as conventions evolve. Use when agent ecosystems add new ways to state behavior, skills, or rules; when discovery files need revision; or when maintaining FOR_AGENTS.md, .cursorrules, docs/for-agents.md, docs/agent-discovery.md. |
Keep HALOS agent discovery files current as coding tools and agent frameworks evolve.
.agentrules, AI_CONTEXT.md)| File | Purpose |
|---|---|
FOR_AGENTS.md | Root-level agent entry point |
.cursorrules | Legacy Cursor config |
AGENTS.md | Contract and agent definitions |
docs/for-agents.md | Full agent guidelines, discovery table |
docs/agent-discovery.md | Why/how documentation |
spec/manifest.json | Machine-readable discovery |
.cursor/rules/halos-alignment.mdc | Cursor rule (always apply) |
Research — Search for new conventions: agent instruction formats, discovery mechanisms, tool-specific config files (e.g., .aider.conf, .continuerc, AI_CONTEXT.md, .well-known/agents/).
Propose — For structural changes (new files, new sections), use the proposal process (proposals/). For minor updates (fixing links, wording), edit directly.
Update files:
docs/for-agents.md discovery table when adding/changing filesdocs/agent-discovery.md "Files Added" and "Maintenance" sectionsFOR_AGENTS.md as a brief pointer; avoid duplicating full contract.cursorrules minimal (one-line pointer)Canonical sources — The HALOS contract lives in spec/core.json and .cursor/rules/halos-alignment.mdc. Discovery files should point to these, not duplicate them.
README — Update the "For AI Agents" section and "Agents" links if new files are added.
.ossa.yaml.well-known/agents/.cursorrules, .cursor/rules/, AGENTS.md.aider.conf, .aiderignore.continuercFOR_AI.md, AI_CONTEXT.md, .agentrules, AGENT_INSTRUCTIONS.mdWhen a convention becomes widely used, consider adding a HALOS pointer in that format. When obsolete, mark deprecated in docs but avoid breaking existing users.
Answer help questions and route users. Use when the user says help, how do I, what is HALOS, or asks about contributing, validating, proposing, or understanding the spec.
Troubleshoot validation, build, and Docker. Use when the user has validation errors, build failures, Docker issues, or questions about running validate, build, or serve.
Help draft and structure proposals. Use when the user wants to write a proposal, submit a framework change, extend the spec, or needs guidance on the proposal process.
Explain HALOS in plain language. Use when the user asks about a core requirement, principle, how to adopt HALOS, or interpretation of the spec.