Review Best Practice Profile

Validate a .grimoire/profiles/<name>.toml file — check format, verify skills exist, surface conflicts.

Why This Is Best Practice

Adopted by: Every package registry runs validation before publish — npm, PyPI, and Cargo all reject malformed manifests at submission time. ESLint's --print-config resolves and validates the final config before running. Grimoire profile review applies the same gate: catch issues before a profile is shared and depended on. Impact: A profile with a broken skill name silently activates nothing for that entry — no error, no warning at runtime. Review at authoring time surfaces these before they reach team members who depend on the profile. Why best: Review at publish time costs 30 seconds. Debugging why a profile silently skipped three skills in production costs 30 minutes. The gate is the right place.

Sources: XDG Base Directory Specification (freedesktop.org); npm publish validation; Grimoire docs/profiles.md

Steps

1. Locate the profile file

User provides name or path. Search order if only a name is given: