“BeeRad”
07754f5030
- remove legacy contexts surfaces from the app, MCP bridge, standalone server, and docs - keep getContext and retrieveQueryContext while aligning the simplified graph-only contract - harden dev startup migration behavior and disable the accidental chat surface in open source Generated with Codex
1.0 KiB
1.0 KiB
name, description
| name | description |
|---|---|
| Audit | Use for structured review, QA, cleanup, or governance checks across graph quality, skill quality, and operational consistency. |
Audit
Scope
- Node quality: duplicates, vague descriptions, missing dates, weak titles.
- Edge quality: missing links, weak explanations, wrong directionality.
- Graph structure quality: weak clustering, redundant organizational nodes, or cases where stronger titles, descriptions, metadata, and edges should carry the meaning.
- Skill quality: trigger clarity, overlap, dead/unused skills.
Output Format
- Critical issues
- High-impact improvements
- Cleanup actions
- Optional refinements
Rules
- Prefer specific evidence over generic commentary.
- Propose the smallest high-leverage fixes first.
- Separate defects from optional polish.
- Node descriptions must read like natural prose while still making what / why / status clear.
- Flag any node description missing a clear why or status component as a high-priority quality issue.