菜单
Use when the user wants to validate a practice profile before using or sharing it — e.g., "review my profile", "validate my-team.toml", "check this profile before sharing".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jeffreytse/grimoire-core --skill review-best-practice-profile命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when comparing very differently-titled roles for compensation banding, leveling, or organizational design — score each role's inherent Know-How (knowledge, skills, experience required), Problem Solving (complexity and freedom of thinking, scored as a percentage of Know-How), and Accountability (freedom to act and magnitude of impact), because job titles and informal seniority perceptions vary inconsistently across departments and don't provide a comparable basis on their own.
Use when many people request your scarce time, mentorship, or expertise and you cannot evaluate their genuine commitment level from a conversation alone — require a specific, costly, objectively verifiable unit of self-directed output (a set number of completed attempts) before engaging, because genuine commitment is what a conversation cannot reliably reveal but a completed, verifiable body of work can.
Use when deciding how to allocate a manager's or leader's limited time across competing activities — before defaulting to whatever is most urgent, estimate each candidate activity's leverage (how many people's output it affects, for how long, and whether it requires your specific position), because a manager's actual output is the output of the organization under their influence, not their own individual task completion.
基于 SOC 职业分类
正在显示 SKILL.md
| name | review-best-practice-profile |
| description | Use when the user wants to validate a practice profile before using or sharing it — e.g., "review my profile", "validate my-team.toml", "check this profile before sharing". |
| source | Grimoire project conventions; XDG Base Directory Specification (freedesktop.org) |
| tags | ["profile","review","validation","quality","contributor"] |
| related | ["write-best-practice-profile","apply-best-practice-profile","share-best-practice-profile"] |
Validate a .grimoire/profiles/<name>.toml file — check format, verify skills exist, surface conflicts.
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
User provides name or path. Search order if only a name is given:
.grimoire/profiles/<name>.toml — project-level~/.grimoire/profiles/<name>.toml — user-level<name>.toml — current directoryIf not found, report checked locations and stop.
Multi-location conflict: If the profile name matches files at more than one location (e.g., both project-level and user-level), note it before proceeding: 'Found [name].toml at [path1] (project) and [path2] (user). Reviewing [path1] — project takes precedence. To review the other, provide the full path.' Do not silently pick one without telling the user.
If the file is malformed TOML, report the parse error with line number and stop:
✗ Parse error at line 7: expected '=' after key
| Field | Required | Check |
|---|---|---|
name | yes | non-empty string |
[[skills]] | yes | at least one entry |
skills[].name | yes | non-empty string for each entry |
description | no | warn if absent (helpful for sharing) |
For each skills[].name, check it exists in installed grimoire skills:
Read the related: frontmatter of each found skill. If two skills in the profile list each other as conflicting (or share a known-conflicting tag pairing), flag as warning. This is a soft check — conflicts are context-dependent.
Conflict detection mechanism: Two skills conflict if:
For each detected conflict, show: '[skill-A] ↔ [skill-B]: [reason they conflict] — cannot apply both simultaneously.'
Example conflicts (anchors for judgment):
apply-functional-programming ↔ apply-oop-principles — mutually exclusive paradigms when applied globally to the same codebaseprefer-immutability ↔ a performance practice requiring mutation — philosophy conflict on data handlingenforce-strict-types ↔ prefer-duck-typing — type system philosophy conflictUse these as calibration anchors when evaluating novel skill pairs.
Profile: my-team (4 skills)
✓ Format valid
✓ description present
✓ apply-solid-principles — found
✓ apply-domain-driven-design — found
⚠ apply-twelve-factor-app — not installed
Install: grimoire --skill engineering/architecture/apply-twelve-factor-app
✓ apply-kiss-principle — found
Result: PASS with 1 warning
Next: /share-best-practice-profile my-team
If errors exist (missing required fields, zero valid skills), result is FAIL.
FAIL is advisory, not a blocker: A FAIL result means the profile has issues worth fixing before sharing, but the user can still apply it. After showing the FAIL findings, offer: 'Fix issues before applying? [y] or apply anyway? [n]'. Never silently block application.
Skipping review before sharing. A profile that works locally (all skills installed) may fail for others if skill names are not canonical. Review against the published skill list, not just what is locally installed.