term-entry

Estrellas1

Forks0

Actualizado14 de abril de 2026 a las 11:51

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

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

codekiln

codekiln/beans

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Secretarios y asistentes administrativos (excepto legal, médico y ejecutivo)Oficina y apoyo administrativo·SOC 43-6014

SKILL.md

readonly

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

Term entry

Use this skill when creating a new glossary term entry.

Command

$ bean term-entry "<TOPIC>" "<TERM>"

bean is display text for CLI-style formatting. Do not paste this command into the markdown body.

Required behavior

Treat the request as two inputs: TOPIC and TERM.
Create the filename by slugifying the term into lowercase kebab-case.
Write the file directly under src/content/terms/.
Include frontmatter matching the terms collection schema:

---
name: "<display term>"
summary: "<very short one-line summary>"
aliases:
  - "<optional alias>"
---

Keep the primary descriptive content in the markdown body, not frontmatter arrays.
Use exactly one markdown heading, and it must be the term itself.
Write only 1 or 2 short paragraphs in the body.
Attach 2 to 4 trustworthy hyperlinks directly to the relevant claim or example.
Create the file instead of stopping at a draft or diff-only response.

Notes

Use markdown inline links for citations.
Keep the summary short enough to read cleanly on /beans/terms/.
If the requested term text is awkward as a display label, you may normalize the display name slightly while preserving the user's intent.

Más de este repositorio

mismo repositorio

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

bean-entry

codekiln/beans

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

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

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

Term entry

Use this skill when creating a new glossary term entry.

Command

$ bean term-entry "<TOPIC>" "<TERM>"

bean is display text for CLI-style formatting. Do not paste this command into the markdown body.

Required behavior

Treat the request as two inputs: TOPIC and TERM.
Create the filename by slugifying the term into lowercase kebab-case.
Write the file directly under src/content/terms/.
Include frontmatter matching the terms collection schema:

---
name: "<display term>"
summary: "<very short one-line summary>"
aliases:
  - "<optional alias>"
---

Keep the primary descriptive content in the markdown body, not frontmatter arrays.
Use exactly one markdown heading, and it must be the term itself.
Write only 1 or 2 short paragraphs in the body.
Attach 2 to 4 trustworthy hyperlinks directly to the relevant claim or example.
Create the file instead of stopping at a draft or diff-only response.

Notes

Use markdown inline links for citations.
Keep the summary short enough to read cleanly on /beans/terms/.
If the requested term text is awkward as a display label, you may normalize the display name slightly while preserving the user's intent.