support-desk
Route a question to the team that owns an artifact. Use when a published skill misbehaves and you need the maintainer, the issue tracker, or the security contact rather than a code change.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 15
- Forks
- 1
01 前言 Front Matter
- name
- support-desk
- license
- MIT
- metadata
- { "vendor": "Grimoire Manual Rig", "authors": "Grimoire Platform Team", "summary": "Maintainer-routing skill (annotation demo)", "homepage": "https://grimoire.rs", "keywords": "support,contact,maintainer,demo", "repository": "https://github.com/grimoire-rs/grimoire", "documentation": "https://grimoire.rs/publishing.html#metadata-descriptive" }
- description
- Route a question to the team that owns an artifact. Use when a published skill misbehaves and you need the maintainer, the issue tracker, or the security contact rather than a code change.
- compatibility
- claude>=2
02 资源文件 2
- 参考文档CHANGELOG.md1.1 KB
- 参考文档README.md630 B
03 SKILL.md 正文
Support Desk
The rig's annotation showcase. Every optional metadata field grim knows
how to publish is authored here or in catalog/publish.toml, so one artifact
exercises the whole read path at once:
- Frontmatter
license,compatibility, and the descriptivemetadatakeys (authors,vendor,homepage,documentation) becomeorg.opencontainers.image.*/com.grimoire.*annotations on the manifest. revisionandcreatedare derived from the publishing commit — no flag needed, and no wall clock is read, so re-publishing the same commit yields the same digest.- The repository's support channels ride the description companion, not
this manifest, so moving a chat link is a
grim publishre-run rather than a re-release of every version.
See scenario 9 in the rig README for what each surface shows.
04 同仓库更多 Skills
rca
Use when a bug ticket, GitHub issue or error report needs a root cause analysis before code is touched — "is this a bug", "why does this fail". Read-only. Gives a verdict (bug or not-a-bug kind), file:line evidence, ruled-out hypotheses, other affected sites, fix direction and size. A ticket, not a diff (hex-review).
fix
Use when a bug ticket or GitHub issue should go from report to an approved fix plan — "plan a fix", "fix this issue". Root-causes it via rca, then plans in plan mode with the failing regression test first. Routes to hex-plan instead when the fix is large or moves an interface contract.
p9-skill
Principle 9 differential fixture skill (v2).
p9-member
Bundle member skill for the Principle 9 fixture (v2).
p9-hookish
Hook-free skill carrying an ignored hook.toml (v2).
p9-skill
Principle 9 differential fixture skill (v1).