bean-entry

星标1

分支0

更新时间2026年4月14日 11:51

Create a new bean entry with the correct file shape, public identifier, frontmatter, imported images, and Beans-specific markdown conventions.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

codekiln

codekiln/beans

打开 GitHub 仓库查看创作者相关仓库

下载

Bean entry

Use this skill when creating a new bean entry.

Command

$ bean log <YYYY-MM-DD> [HHMM]

bean is display text for CLI-style formatting and naming conventions in this project. Do not paste this command into the markdown body.

Target file

Create:

src/content/beans/<YYYY-MM-DD>-<beanKey>.md

Public identifier rules

Keep the filename, frontmatter id, and frontmatter beanKey in the internal <YYYY-MM-DD>-<beanKey> format.
Use the date by itself for the public command prompt and route when that date has only one bean entry.
If the date has multiple bean entries, use top-level time converted to 24-hour HHMM as the public identifier.
If time is missing on a multi-entry date, use a simple ordinal fallback such as 1 or 2.

Template

---
id: "<YYYY-MM-DD>-<beanKey>"
beanKey: "<beanKey>"
date: "<YYYY-MM-DD>"
time: "<HH:MM>"
title: "<short title>"
tags:
  - "<tag>"
coffee:
  roaster:
    name: "<roaster name>"
    slug: "<roaster-slug>"
  roast:
    name: "<roast name>"
    slug: "<roaster-slug>/<roast-slug>"
brew:
  brewer:
    name: "<brewer name>"
    slug: "<brewer-slug>"
  recipe:
    name: "<recipe name>"
    slug: "<recipe-slug>"
brewDetails:
  dose: "<dose>"
  water: "<water>"
  ratio: "<ratio>"
  grinder:
    name: "<grinder name>"
    slug: "<grinder-slug>"
  grind: "<grind description>"
  setting: "<setting>"
  temp: "<temperature>"
  release: "<release time>"
  total: "<total time>"
  time: "<brew time>"
gear:
  - label: "<label>"
    value: "<value>"
    slug: "<slug>"
---

<note>

Notes

Omit optional fields or entire objects when unknown.
Keep the primary descriptive content in the markdown body.
Save new assets under public/images/.
In the bean markdown body, link images with /beans/images/<filename>.
If the user supplied images or scans, import them and display them in the entry by default.
For multi-page scans, place each image near the corresponding section and use the clearest page as the frontmatter image when appropriate.
For handwritten or scan-based entries, also apply the bean-entry-handwritten skill.
Do not include an inline body preamble like $ bean log YYYY-MM-DD; the entry header already renders the command prompt.

同仓库更多 Skills

同仓库

bean-entry-handwritten

codekiln/beans

Create or update a bean entry from handwritten scans while preserving line breaks, handling CompanionComment formatting correctly, maintaining spans, and avoiding low-value boilerplate transcription.

2026-04-141

land-the-plane

codekiln/beans

Close out a Beans work session cleanly by validating work, finishing Beads-managed tasks correctly, landing on main, and pruning closed worktrees.

2026-04-141

playwright-preview

codekiln/beans

Capture local dev-server screenshots with Playwright for Beans preview workflows, especially for `/beans/` routes and visual verification of new pages or content edits.

2026-04-141

rulesync-preferences

codekiln/beans

Use when adding, changing, or reorganizing AI guidance in this repository. Prefer Rulesync skills over commands, subagents, or hooks for reusable workflows, and always edit Rulesync sources before generating tool-specific AI config files.

2026-04-141

rulesync

codekiln/beans

Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.

2026-04-141

term-entry

codekiln/beans

Create a new glossary term entry with the correct schema, compact body, and lightly sourced Beans field-guide tone.

2026-04-141

Bean entry

Use this skill when creating a new bean entry.

Command

$ bean log <YYYY-MM-DD> [HHMM]

bean is display text for CLI-style formatting and naming conventions in this project. Do not paste this command into the markdown body.

Target file

Create:

src/content/beans/<YYYY-MM-DD>-<beanKey>.md

Public identifier rules

Keep the filename, frontmatter id, and frontmatter beanKey in the internal <YYYY-MM-DD>-<beanKey> format.

Use the date by itself for the public command prompt and route when that date has only one bean entry.

If the date has multiple bean entries, use top-level time converted to 24-hour HHMM as the public identifier.

If time is missing on a multi-entry date, use a simple ordinal fallback such as 1 or 2.

Template

--- id: "<YYYY-MM-DD>-<beanKey>" beanKey: "<beanKey>" date: "<YYYY-MM-DD>" time: "<HH:MM>" title: "<short title>" tags: - "<tag>" coffee: roaster: name: "<roaster name>" slug: "<roaster-slug>" roast: name: "<roast name>" slug: "<roaster-slug>/<roast-slug>" brew: brewer: name: "<brewer name>" slug: "<brewer-slug>" recipe: name: "<recipe name>" slug: "<recipe-slug>" brewDetails: dose: "<dose>" water: "<water>" ratio: "<ratio>" grinder: name: "<grinder name>" slug: "<grinder-slug>" grind: "<grind description>" setting: "<setting>" temp: "<temperature>" release: "<release time>" total: "<total time>" time: "<brew time>" gear: - label: "<label>" value: "<value>" slug: "<slug>" --- <note>

Notes

Omit optional fields or entire objects when unknown.

Keep the primary descriptive content in the markdown body.

Save new assets under public/images/.

In the bean markdown body, link images with /beans/images/<filename>.

If the user supplied images or scans, import them and display them in the entry by default.

For multi-page scans, place each image near the corresponding section and use the clearest page as the frontmatter image when appropriate.

For handwritten or scan-based entries, also apply the bean-entry-handwritten skill.

Do not include an inline body preamble like $ bean log YYYY-MM-DD; the entry header already renders the command prompt.

name	bean-entry
description	Create a new bean entry with the correct file shape, public identifier, frontmatter, imported images, and Beans-specific markdown conventions.