Individual skill
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.
test/manual/catalog/skills/support-desk/SKILL.md
Source commit 03393c51ffa36f488ed4c86839a853b38ffdf41d
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 15
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
CHANGELOG.mddoc · 1,111 bytesREADME.mddoc · 630 bytesSKILL.mdcore · 1,451 bytes
Read excerpt
# 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 descriptive `metadata` keys
(`authors`, `vendor`, `homepage`, `documentation`) become
`org.opencontainers.image.*` / `com.grimoire.*` annotations on the manifest.
- `revision` and `created` are 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 publish` re-run rather than