Recording
codewhale-hq/Codewhale
Capture screenshots on registered computers, record on macOS or HarmonyOS, and manage saved captures.
Catalogs or repairs Peated Bottle records directly for a named Bottle, brand, Series, distillery, bottler, or release set.
Apache-2.0Auto-check passed
Install Peated Catalog
$ npx skills add dcramer/peated --skill peated-catalog -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dcramer/peated peated-catalog --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/dcramer/peated.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/peated-catalog .claude/skills/peated-catalog && 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 "peated-catalog" agent skill from https://github.com/dcramer/peated/tree/main/skills/peated-catalog into .claude/skills/peated-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peated-catalog", 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/dcramer/peated/tree/main/skills/peated-catalogType 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 dcramer/peated --skill peated-catalog -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dcramer/peated peated-catalog --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dcramer/peated.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/peated-catalog .agents/skills/peated-catalog && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "peated-catalog" agent skill from https://github.com/dcramer/peated/tree/main/skills/peated-catalog into .agents/skills/peated-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peated-catalog", 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 dcramer/peated --skill peated-catalog -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dcramer/peated peated-catalog --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dcramer/peated.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/peated-catalog .cursor/skills/peated-catalog && 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 "peated-catalog" agent skill from https://github.com/dcramer/peated/tree/main/skills/peated-catalog into .cursor/skills/peated-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peated-catalog", 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/dcramer/peated.git --path skills/peated-catalog--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 dcramer/peated --skill peated-catalog -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dcramer/peated peated-catalog --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dcramer/peated.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/peated-catalog .gemini/skills/peated-catalog && 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 "peated-catalog" agent skill from https://github.com/dcramer/peated/tree/main/skills/peated-catalog into .gemini/skills/peated-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peated-catalog", 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 dcramer/peated peated-catalogInstalls 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 dcramer/peated --skill peated-catalog -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dcramer/peated.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/peated-catalog .github/skills/peated-catalog && 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 "peated-catalog" agent skill from https://github.com/dcramer/peated/tree/main/skills/peated-catalog into .github/skills/peated-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peated-catalog", 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 dcramer/peated --skill peated-catalog -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dcramer/peated peated-catalog --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dcramer/peated.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/peated-catalog .opencode/skills/peated-catalog && 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 "peated-catalog" agent skill from https://github.com/dcramer/peated/tree/main/skills/peated-catalog into .opencode/skills/peated-catalog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "peated-catalog", 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
peated-catalog- GitHub stars
- 102
- Token cost
- ~1.7k tokens
- SKILL.md length
- 806 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Catalogs or repairs Peated Bottle records directly for a named Bottle, brand, Series, distillery, bottler, or release set.
- Works in 9 steps: Name the target and environment. Resolve… → Build the outside inventory before… → Fetch every page of Peated results by… → …
- Missing Bottles
- SKILL.md covers Read what applies, Work, Research record and Rules
- Calls pnpm
What it does
Peated Catalog is an agent skill from dcramer/peated. Catalogs or repairs Peated Bottle records directly for a named Bottle, brand, Series, distillery, bottler, or release set. Use for missing Bottles, wrong facts, Brand or Series decisions, images, aliases, references, duplicate review, or a dry-run inventory of such a set. Do not use for code changes or store-price queue moderation.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
The licence is Apache-2.0.
When your agent uses it
- Missing Bottles
- Series decisions
- Duplicate review
- A dry-run inventory of such a set
Example prompts
- “Use the peated-catalog skill to catalog or repairs Peated Bottle records directly for a named Bottle, brand, Series, distillery, bottler, or release…”
- “/peated-catalog”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Name the target and environment. Resolve stored IDs with read-only API
- Build the outside inventory before deciding anything: current and past
- Fetch every page of Peated results by Brand, distiller, bottler, Series,
- Give each row one status: create, update, merge, no change,
- Review every field, Series, the target Entity, images, aliases, and import
- Before writing, state the target and the counts by status. A direct
- Check the live OpenAPI schema. Re-fetch each record before changing it. Use
- Re-fetch every changed record and check shared edits, images, aliases,
- Before reporting, write the research record under
What it can do on your machine
Read from SKILL.md and the folder at commit aee6890. 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
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
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
Peated Catalog loads about 1.7k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 806 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 dcramer/peated at commit aee6890, republished under its Apache-2.0 licence (© dcramer). 806 words, ~1,652 tokens.
Download SKILL.mdSave it as
.claude/skills/peated-catalog/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- peated-catalog
- description
- Catalogs or repairs Peated Bottle records directly for a named Bottle, brand, Series, distillery, bottler, or release set. Use for missing Bottles, wrong facts, Brand or Series decisions, images, aliases, references, duplicate review, or a dry-run inventory of such a set. Do not use for code changes or store-price queue moderation.
Peated Catalog
Finish the named catalog target in production unless the user names another environment or asks only for a dry run, research, or review. Follow any narrower target the user gives.
Read what applies
| Read | For |
|---|---|
docs/operations/catalog-maintenance.md | The full workflow, every field to review, and the create, patch, merge, and image procedures |
docs/architecture/whisky-identity-model.md | What counts as a release, the six Brand, Series, and bottler rules, and when Bottles are one |
docs/operations/catalog-research.md | Where releases hide and the traps earlier work hit; read before building the outside inventory |
pnpm cli auth, pnpm cli api | Production data. Do not use legacy database commands. |
Work
- Name the target and environment. Resolve stored IDs with read-only API calls.
- Build the outside inventory before deciding anything: current and past releases from producer archives, dated announcements, specialist catalogs, collector lists, old sites, and auction records. The producer's current range is not the catalog. Search every period and product family, including discontinued, one-off, and country-specific releases. For a distillery scope, also search former owner and house brands. If a search fails, try other names, languages, archives, and kinds of sources.
- Fetch every page of Peated results by Brand, distiller, bottler, Series, and name search. Compare both directions: every outside release needs a Peated status and every Peated record needs an inventory status.
- Give each row one status:
create,update,merge,no change,unresolved, orout of scope. Save the source for each changed fact. Do not mark old recordsunresolvedas a group because there are many or no producer page survives; for each one, record the open question and the searches tried. - Review every field, Series, the target Entity, images, aliases, and import references that Catalog Maintenance lists.
- Before writing, state the target and the counts by status. A direct catalog request allows evidence-backed creates and updates inside that target. Ask before Bottle or Entity merges, deletes, Brand changes, or work outside the target.
- Check the live OpenAPI schema. Re-fetch each record before changing it. Use exact IDs and send only supported fields. Stop if the record changed or the API returns a conflict or validation error.
- Re-fetch every changed record and check shared edits, images, aliases, references, and redirects where they apply.
- Before reporting, write the research record under
docs/research/catalog/YYYY-MM-DD-short-name.md: a guide to where the information for this scope lives, for the next person who researches it. Do not append to a shared or monthly report. Updatedocs/operations/catalog-research.mdonly for a reusable method, access limit, or recurring trap.
Research record
| Keep | Leave out |
|---|---|
| Each source with its link, the families and years it covers, and its limit | Production IDs, counts, and per-Bottle field lists |
| Sites that block tools or need a browser, and pacing limits | Raw API replies, request files, tokens, downloaded images |
| Conflicts between sources and which value was used | Working notes with no later use |
| Searches and sites that found nothing | Claims that a source is complete when it does not prove it |
| Image reuse terms per site | |
| Releases and facts still unknown, with the open question |
Peated's change history records the writes; the report to the user carries the counts and IDs.
Show full SKILL.md (277 more words)Show less
Rules
- One marketed release is one Bottle. The same liquid in another size, box, label, or market name is the same Bottle; add the name as a reference.
- Set Brand, Series, and bottler with the six rules in the identity model.
In short: a distillery's own line and an owner's multi-distillery
collection are Brands; an independent bottler's label is Brand and bottler;
a retailer's, importer's, or festival's selection of an official bottling
keeps the producer Brand, has no bottler, and carries the program name in
edition. Do not clear an existing bottler only because a source omits it. nameis the producer's title without the Brand, keeping printed age, vintage, or cask wording. Store age, years, ABV, edition, cask facts, and outturn in their fields as well; never build a name from them, and do not fall back to a genericSingle Malt.- Read the edit context before a shared rename; it changes every Bottle in the group.
- Use
nullfor an unknown or disputed fact. Keep an existing value unless a stronger source for the same Bottle proves it wrong. - Add an alias only for a proven public name. Assign an import reference only when its full text identifies one Bottle.
- Use only an image of the exact Bottle. Record its source page and reuse terms, then inspect the stored image; a direct image URL is not provenance.
- Merge only proven copies of the same marketed release.
One family or the current range does not complete the catalog; continue until every item has a final status. Report the environment, sources and years covered, counts by status, changed IDs, checks performed, research records changed, and unresolved questions.
© dcramer, Apache-2.0. 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/peated-catalog of dcramer/peated.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit aee6890
Compare with similar skills
Peated Catalog 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 |
|---|---|---|---|---|---|---|
| Peated Catalog this skilldcramer/peated | 102 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Recordingcodewhale-hq/Codewhale | 41k | — | ~540 | Automated safety check: Pass | MIT | |
| Browser Recordruvnet/ruflo | 74k | — | ~735 | Automated safety check: Notes | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 275k | 4 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 275k | 1 repos | ~863 | Automated safety check: Pass | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 275k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Browser Record
ruvnet/ruflo
Open a named, traced browser session into an RVF cognitive container with a ruvector trajectory recording every action
Architecture Decision Records
affaan-m/ECC
Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README.
Architecture Decision Records
affaan-m/ECC
在Claude Code会话期间，将做出的架构决策捕获为结构化的架构决策记录（ADR）。自动检测决策时刻，记录上下文、考虑的替代方案和理由。维护一个ADR日志，以便未来的开发人员理解代码库为何以当前方式构建。
Architecture Decision Records
affaan-m/ECC
コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。
Openclaw Repair Sweep
openclaw/openclaw
Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.
More from dcramer/peated
Peated QA
dcramer/peated
A skill your agent uses when manually QAing Peated changes across the API, CLI, or web UI; selecting smoke checks after code changes; using agent-browser for Peated flows; verifying local behavior…
Agent Design Review
dcramer/peated
Designs, reviews, and debugs Peated's model-driven code, such as the Bottle and Entity classifiers, extractors, price matching, and generated details.
Deslop
dcramer/peated
Simplifies existing Peated code, docs, prompts, plans, or explanations without changing required behavior.
Peated Scraper Queue
dcramer/peated
Moderates Peated retailer listings in the store-price match queue.
Peated Writing
dcramer/peated
Writes and reviews user-facing Peated copy in the product's voice.
Peated CLI
dcramer/peated
Use Peated's authenticated API client for OAuth-backed production API reads and writes through pnpm cli auth and pnpm cli api.
Questions about Peated Catalog
What does Peated Catalog do?
Catalogs or repairs Peated Bottle records directly for a named Bottle, brand, Series, distillery, bottler, or release set. Peated Catalog is an agent skill from dcramer/peated. Catalogs or repairs Peated Bottle records directly for a named Bottle, brand, Series, distillery, bottler, or release set.
When should I use Peated Catalog?
Peated Catalog fits situations like: missing Bottles; series decisions; duplicate review; A dry-run inventory of such a set.
How do I install Peated Catalog in Claude Code?
Run `npx skills add dcramer/peated --skill peated-catalog -a claude-code`. Or copy the skill folder (skills/peated-catalog in dcramer/peated) into .claude/skills/peated-catalog in your project. Claude Code loads it when a task matches its description.
How do I install Peated Catalog in Codex?
Run `npx skills add dcramer/peated --skill peated-catalog -a codex`. Or copy the skill folder (skills/peated-catalog in dcramer/peated) into .agents/skills/peated-catalog in your project. Codex loads it when a task matches its description.
Can I use Peated Catalog 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 dcramer/peated --skill peated-catalog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/peated-catalog, .gemini/skills/peated-catalog, .github/skills/peated-catalog and .opencode/skills/peated-catalog in your project.
What does Peated Catalog need to run?
Going by SKILL.md and its folder, Peated Catalog needs the command-line tools its instructions call (pnpm).
Does Peated Catalog 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 Peated Catalog 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 Peated Catalog use?
Peated Catalog is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Peated Catalog use?
About 1.7k tokens (SKILL.md is roughly 6.6k 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 Peated Catalog?
Skills that share tags, products or a category with Peated Catalog: Recording (codewhale-hq/Codewhale, 41k stars), Browser Record (ruvnet/ruflo, 74k stars), Architecture Decision Records (affaan-m/ECC, 275k stars) and Architecture Decision Records (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Peated Catalog?
dcramer (a GitHub user) maintains it in dcramer/peated, which has 102 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 2, 2026.
Source: dcramer/peated on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.