hallmark-setup SKILL.md skillA
hallmark-setup from tiagocolombo/hallmark is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tiagocolombo/hallmark/hallmark-setup@git:20261027.f4c613cPins git:20261027.f4c613c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tiagocolombo/hallmark
- Path
plugin/skills/hallmark-setup/SKILL.md- Versions recorded
- 9
- Latest version
- git:20261027.f4c613c, committed Oct 27, 2026
- First version recorded
- Oct 18, 2026
- Size
- 10,279 bytes
- Repository stars
- 9
- License
- MIT
Configure Hallmark for this person and repo with `hall config` - gates and the shell they run in, how worktrees are made and work is shipped, models, budgets, where claude and gh live, notifications. Use when they say "set up Hallmark", "configure hallmark", "change the gates", "use devbox/nix/mise for the checks", "change the ship command", "set a budget", "hall can't find gh", or ask what a Hallmark setting does.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Setting Hallmark up Every Hallmark setting can be read and changed with `hall config`. You never edit `.hallmark.toml` or the user config by hand. `hall config` keeps their comments and checks each value before it writes. Don't run `hall setup --interactive`: it asks its questions on a terminal, and you can't answer them. Ask the person yourself, then set what they choose. `hall init` and the first `hall setup` ask the same questions on a terminal; from a session they don't (there is no terminal), and `--defaults` says so explicitly. ## Look first ```sh hall config list --json # every key: value, source, kind, help, allowed values hall config list gates --json # one key, or every key under a prefix (budget, notify) ``` `source` says where a value comes from: - `default`: Hallmark's built-in value; - `repo`: this repo's `.hallmark.toml`; - `user`: the person's user config; - `env`: a `HALL_*` variable; - `path`: a tool found on PATH. Detect before you ask. Read `package.json`, `Cargo.toml`, `Makefile`, `justfile`, `flake.nix`, `devbox.json`, `mise.toml` and `.envrc`, then propose concrete values. ## Ask, in this order, one topic at a time …
Read the whole file at its exact version.
How to install
mdr add tiagocolombo/hallmark/hallmark-setup@sha256:6e8dca9c388f5485The line at the top of this page pins the label git:20261027.f4c613c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6x4kuzrv275hqj2x)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 9 versions of this file, between Oct 18, 2026 and Oct 27, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.f4c613c latest | 2026-10-27 | f4c613c | 10,279 B | A | view · diff |
| git:20261027.6e8ccb5 | 2026-10-27 | 6e8ccb5 | 10,056 B | A | view · diff |
| git:20261027.6fec9e1 | 2026-10-27 | 6fec9e1 | 10,032 B | A | view · diff |
| git:20261023.30bc989 | 2026-10-23 | 30bc989 | 9,868 B | A | view · diff |
| git:20261018.8697bef | 2026-10-18 | 8697bef | 8,845 B | A | view · diff |
| git:20261018.9e19afc | 2026-10-18 | 9e19afc | 8,288 B | A | view · diff |
| git:20261018.d713047 | 2026-10-18 | d713047 | 8,123 B | A | view · diff |
| git:20261018.c3a9825 | 2026-10-18 | c3a9825 | 7,845 B | A | view · diff |
| git:20261018.d964ccc | 2026-10-18 | d964ccc | 7,675 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10279 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tiagocolombo/hallmark · 9 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6x4kuzrv275hqj2x GET https://markdownregistry.com/api/v1/resolve?ref=tiagocolombo/hallmark/hallmark-setup GET https://markdownregistry.com/api/v1/blob/6e8dca9c388f5485f10c6aacf91ec167614bc430572f0e953b86f2c26ee2f09c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.