North Star Metric
phuryn/pm-skills
Define a North Star Metric and 3-5 supporting input metrics that form a metrics constellation.
Compare design alternatives with a hat → metrics → tier-list loop, splitting composing layers and keeping a living note.
MITAuto-check passed
Install The Hat
$ npx skills add yamcodes/arkenv --skill the-hat -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yamcodes/arkenv the-hat --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/the-hat .claude/skills/the-hat && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "the-hat" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/the-hat into .claude/skills/the-hat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-hat", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yamcodes/arkenv/tree/v1/skills/the-hatType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yamcodes/arkenv --skill the-hat -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yamcodes/arkenv the-hat --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/the-hat .agents/skills/the-hat && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "the-hat" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/the-hat into .agents/skills/the-hat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-hat", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yamcodes/arkenv --skill the-hat -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yamcodes/arkenv the-hat --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/the-hat .cursor/skills/the-hat && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "the-hat" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/the-hat into .cursor/skills/the-hat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-hat", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yamcodes/arkenv.git --path skills/the-hat--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yamcodes/arkenv --skill the-hat -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yamcodes/arkenv the-hat --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/the-hat .gemini/skills/the-hat && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "the-hat" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/the-hat into .gemini/skills/the-hat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-hat", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yamcodes/arkenv the-hatInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yamcodes/arkenv --skill the-hat -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/the-hat .github/skills/the-hat && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "the-hat" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/the-hat into .github/skills/the-hat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-hat", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yamcodes/arkenv --skill the-hat -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yamcodes/arkenv the-hat --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/the-hat .opencode/skills/the-hat && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "the-hat" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/the-hat into .opencode/skills/the-hat/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-hat", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
the-hat- GitHub stars
- 145
- Token cost
- ~928 tokens
- SKILL.md length
- 508 words
- Files
- 2
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
Compare design alternatives with a hat → metrics → tier-list loop, splitting composing layers and keeping a living note.
- Works in 9 steps: Name the problem — what must be true… → Split composing layers if “solutions”… → Put every option in the hat, including… → …
- There are multiple ways to solve a design problem
- SKILL.md covers Loop, Living note, Layers vs a false choice and Rules
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The Hat is an agent skill from yamcodes/arkenv. Compare design alternatives with a hat → metrics → tier-list loop, splitting composing layers and keeping a living note. Use when there are multiple ways to solve a design problem, the user says "throw it in the hat" or "/the-hat", asks for a tier list, design eval, or composing layers/dimensions, or when options look like they compose rather than compete — even if they have not named this skill.
Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `NOTE-TEMPLATE.md`).
The repository describes itself as: ⛯ Typesafe environment variables with ArkType, Zod, or Valibot. The licence is MIT.
When your agent uses it
- There are multiple ways to solve a design problem
- The user says throw it in the hat
- Asks for a tier list
- Composing layers/dimensions
Example prompts
- “throw it in the hat”
- “/the-hat”
- “/the-hat”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Name the problem — what must be true when we are done, not the first idea that showed up.
- Split composing layers if “solutions” are not the same kind of thing. Layers are dimensions that compose, not rivals in one list (how you…
- Put every option in the hat, including already-rejected and out-of-scope ones, so they get scored instead of silently returning.
- Pick metrics that match the pain. Invent what fits (honesty, tax fairness, simplicity, DRY, composability, vendor neutrality, footguns…
- Evaluate each hat item against those metrics in prose. A table is welcome for a close call; a vibe ranking with no scores is not.
- Tier list (S / A / B / C / D, plus E if needed). S is the default story. A is optional tuck-away or distribution, not a blocker. A…
- Show usage for S and A across each real use case so the ranking is not abstract.
- Keep a living note. New ideas get slotted; do not restart the write-up.
- Do not ship A-tier extras that are not needed to close the current change.
What it can do on your machine
Read from SKILL.md and the folder at commit 74b3732. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
The Hat loads about 928 tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 508 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from yamcodes/arkenv at commit 74b3732, republished under its MIT licence (© yamcodes). 508 words, ~928 tokens.
Download SKILL.mdSave it as
.claude/skills/the-hat/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- the-hat
- description
- Compare design alternatives with a hat → metrics → tier-list loop, splitting composing layers and keeping a living note. Use when there are multiple ways to solve a design problem, the user says "throw it in the hat" or "/the-hat", asks for a tier list, design eval, or composing layers/dimensions, or when options look like they compose rather than compete — even if they have not named this skill.
- metadata.internal
- true
The hat
When several ways exist to solve a design problem, do not vibe-rank in chat. Run this loop and leave the artifacts in a living note (repo file, not a premature ADR).
Worked example of a hat loop later promoted to an ADR: #1564 / #1570 became ADR 0025. Copy headings from NOTE-TEMPLATE.md.
If the problem itself is still mushy, grill first (grill-me / grill-with-docs), then come back here to score options.
Loop
- Name the problem — what must be true when we are done, not the first idea that showed up.
- Split composing layers if “solutions” are not the same kind of thing. Layers are dimensions that compose, not rivals in one list (how you type a callback vs where the wrapper lives). Do not flatten them into one false choice.
- Put every option in the hat, including already-rejected and out-of-scope ones, so they get scored instead of silently returning.
- Pick metrics that match the pain. Invent what fits (honesty, tax fairness, simplicity, DRY, composability, vendor neutrality, footguns, elegance, teachability, maintenance hell).
- Evaluate each hat item against those metrics in prose. A table is welcome for a close call; a vibe ranking with no scores is not.
- Tier list (S / A / B / C / D, plus E if needed). S is the default story. A is optional tuck-away or distribution, not a blocker. A complete answer may be a stack (one pick per layer), not a single winner.
- Show usage for S and A across each real use case so the ranking is not abstract.
- Keep a living note. New ideas get slotted; do not restart the write-up.
- Do not ship A-tier extras that are not needed to close the current change.
Show full SKILL.md (219 more words)Show less
Living note
Write or update a repo file (typically docs/<topic>.md). Not chat-only. Not an ADR until the decision is hard to reverse, surprising without context, and the result of a real trade-off.
The note must contain:
- Problem statement
- Layer map — orthogonal dimensions; items on different layers compose
- The hat — numbered inventory of every option, grouped by layer (
A1,B1, …) - Metrics — named, with the question each one asks
- Evaluation — each hat item scored in prose against the metrics
- Tier list — S through D (or E), including stacks where layers combine
- S/A usage — concrete code (or equivalent) per real use case
Layers vs a false choice
If two options are not substitutes, they are layers, not rivals.
False choice: “inline helper vs typed callback vs CLI recipe.”
Layers:
- Typing — what is the callback parameter?
- Placement — where does the wrapper live?
S can be a stack (one pick per layer). Rank stacks as answers to the whole problem.
Rules
- Rejected and out-of-scope options stay in the hat and get scored. Silent return is how bad ideas come back next week.
- S is what you ship now. A is optional. Do not block the change on A.
- Slot new ideas into the existing note. Do not rewrite from scratch.
- Do not copy a prior eval’s decision into a new problem. Copy the shape.
© yamcodes, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/the-hat of yamcodes/arkenv.
- SKILL.md
- NOTE-TEMPLATE.md
Open the folder on GitHubat commit 74b3732
Compare with similar skills
The Hat next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| The Hat this skillyamcodes/arkenv | 145 | — | ~928 | Automated safety check: Pass | MIT | |
| North Star Metricphuryn/pm-skills | 27k | — | ~1k | Automated safety check: Pass | MIT | |
| Investigate MetricPostHog/posthog | 40k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Product Metrics Dashboard Designphuryn/pm-skills | 27k | — | ~1.3k | Automated safety check: Pass | MIT | |
| CI Metricspytorch/pytorch | 104k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Startup Metrics Frameworkwshobson/agents | 40k | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Product Metrics Dashboard Design
phuryn/pm-skills
Designs a product metrics dashboard: a North Star and input metrics, a definition table with data sources, chart types and alert thresholds, and a screen layout.
CI Metrics
pytorch/pytorch
Query PyTorch CI, GitHub Actions, HUD, Grafana, and infrastructure metrics.
Startup Metrics Framework
wshobson/agents
Track, calculate, and optimize key performance metrics for SaaS, marketplace, consumer, and B2B startups from seed through Series A, including unit economics, growth efficiency, and cash management.
- Official
Modeling Activation Metrics
PostHog/posthog
Build reusable activation models — an activation-rate metric and a per-user/per-account activated flag — on either PostHog data-warehouse views (HogQL) or an external dbt project.
More from yamcodes/arkenv
All 20 skills in this repoHallmark
yamcodes/arkenv
Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots.
Bulletproof React
yamcodes/arkenv
Bulletproof React architecture patterns for scalable, maintainable applications.
Arkenv
yamcodes/arkenv
Answer questions about ArkEnv and help implement environment variable validation.
Code Review
yamcodes/arkenv
Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace.
Forward Port
yamcodes/arkenv
Manually forward-ports merged dev (v0) changes to the v1 branch, adapting code to v1's package layout and changeset names.
Groom Issue
yamcodes/arkenv
Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent…
Questions about The Hat
What does The Hat do?
Compare design alternatives with a hat → metrics → tier-list loop, splitting composing layers and keeping a living note. The Hat is an agent skill from yamcodes/arkenv. Compare design alternatives with a hat → metrics → tier-list loop, splitting composing layers and keeping a living note.
When should I use The Hat?
The Hat fits situations like: there are multiple ways to solve a design problem; the user says throw it in the hat; asks for a tier list; composing layers/dimensions.
How do I install The Hat in Claude Code?
Run `npx skills add yamcodes/arkenv --skill the-hat -a claude-code`. Or copy the skill folder (skills/the-hat in yamcodes/arkenv) into .claude/skills/the-hat in your project. Claude Code loads it when a task matches its description.
How do I install The Hat in Codex?
Run `npx skills add yamcodes/arkenv --skill the-hat -a codex`. Or copy the skill folder (skills/the-hat in yamcodes/arkenv) into .agents/skills/the-hat in your project. Codex loads it when a task matches its description.
Can I use The Hat in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yamcodes/arkenv --skill the-hat -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/the-hat, .gemini/skills/the-hat, .github/skills/the-hat and .opencode/skills/the-hat in your project.
What does The Hat need to run?
SKILL.md names no scripts, command-line tools or credentials: The Hat is instructions for the agent only.
Does The Hat access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is The Hat safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does The Hat use?
The Hat is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does The Hat use?
About 928 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to The Hat?
Skills that share tags, products or a category with The Hat: North Star Metric (phuryn/pm-skills, 27k stars), Investigate Metric (PostHog/posthog, 40k stars), Product Metrics Dashboard Design (phuryn/pm-skills, 27k stars) and CI Metrics (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains The Hat?
yamcodes (a GitHub user) maintains it in yamcodes/arkenv, which has 145 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.
Source: yamcodes/arkenv on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.