What problem does it solve?
GROWI's suggest-path feature proposes parent paths for saving a document, but there is no systematic way to judge whether those proposals are actually usable. This Skill reviews each proposed path against the wiki's real content and organization, marking it usable, improvable, or not usable, so you can measure and tune suggest-path quality instead of eyeballing results.
Core Features & Use Cases
- Per-candidate verdicts: Judges every suggest-path proposal as o (usable), triangle (usable but a better home exists), or x (not usable), using wiki-agnostic principles rather than a fixed answer key.
- Drilldown to the ideal home: Descends the wiki tree (beam search, up to 3 children per level, depth cap 5) to build the document's recommended save location, which backs x verdicts and supplies the better place for triangle verdicts.
- Batch aggregation and consistency gating: Ships scripts that reconcile per-document digests against bodies to catch body swaps, and aggregate verdicts into per-domain usable-rate, per-candidate rates, recall-miss rate, and x-by-reason breakdowns.
- Use Case: While dogfooding suggest-path on a devcontainer GROWI wiki, run the evaluator on a batch of documents to find which wiki areas produce the most unusable path suggestions and why.
Quick Start
Ask the AI to evaluate suggest-path's proposals for a document body against the local devcontainer GROWI wiki and report the per-candidate verdicts plus the recommended home.