AGENT SKILL

beat-sheet

Formats a reply as single-line beats in plain everyday words. Triggers: '/beat-sheet', 'beat sheet this', 'give me the beats', 'write this as beats', 'too long', 'shorter', 'what?', 'english', 'no sense', 'jargon', 'huh?'.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 7
Forks
1

01 前言 Front Matter

name
beat-sheet
description
Formats a reply as single-line beats in plain everyday words. Triggers: '/beat-sheet', 'beat sheet this', 'give me the beats', 'write this as beats', 'too long', 'shorter', 'what?', 'english', 'no sense', 'jargon', 'huh?'.

02 资源文件 1

03 SKILL.md 正文

beat-sheet

Write in single-line beats. Make each line one complete thought, under 12 words, with a blank line between lines. Keep it to ten lines, each one covering a new point. Order: situation, problem, fix, how it works. Put any command in its own code fence. Start with one short bold title line. Use plain everyday words a tired reader can skim.

Plain words

Name the real thing first — a file, an image, a control, a screen, a size, an id, a proof. Prefer a word the reader can point at over an abstract one. When a word only makes sense on this project, say what it is in the app or on disk (a Theme Studio control, a package file name).

What the reader gets

Lead with the answer. Put most of the reply on what they asked; keep warnings short. For "what's wrong" or "what's missing", answer in this order: what's wrong, what's missing, what follows. For an explain request, give a short summary unless they ask for more.

Around the work

Before the first tool call, say in one sentence what you'll do. While working, speak up only on an important find or a change of course. When you finish, open with the result — what happened or what you found — then add detail only if it helps.

Job size

Do the job asked, at the size asked. Decide small things yourself; ask only when two readings would change the work. When the ask looks off or a better path is clear, say so in one sentence, then do what was asked. Finish the whole job.

Before sending

Read the reply as someone new to the project. Replace any word that needs a glossary with the thing itself.

Visual beats

Add a visual only when it earns its space beyond what the beats already show on their own. See reference/visual-beats.md for the shape picker, the rich setup, and a working example.

04 同仓库更多 Skills

jl-cmd-projects
jl-cmd-projects/claude-dev-env

update

Fast-forwards a local repository's main branch to a remote's main after confirming the repo path and source remote through AskUserQuestion. Use when the user says '/update', 'update main', 'fast-forward main', 'sync main from origin', 'pull latest main into <path>', or 'bring main up to date'.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

source-command-sr-loop

Converging cleanup loop: repeat /simplify until clean, then repeat /code-review --fix until clean

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

skill-builder

Skill lifecycle: classify, scaffold, write via the skill-writer-agent, self-audit, compose sub-skills, polish description triggers, enforce deterministic scripts. Triggers: build a skill, new skill workflow, improve this skill, optimize skill description, skill development lifecycle, skill modularity, skill composition, description trigger catalog, deterministic skill scripts.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

session-tidy

Audit, clean, and consolidate session logs in the Obsidian vault. Fixes format drift, resolves orphaned next-steps, updates stale statuses, and generates project rollup summaries. Use when session logs feel cluttered or before starting a new project milestone. Triggers on '/session-tidy', 'tidy sessions', 'clean up session logs', 'session audit'.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

session-log

Logs a session report as an HTML page, tracks vault context, extracts decisions, and outputs a /rename command. Use for /session-log, 'journal this session', 'log this work', 'session report', 'summarize/log/record this session', 'save session', 'capture session', or 'document what we did'.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

run-claude-dev-env

Build, install, run, and test the claude-dev-env installer. Use when asked to run claude-dev-env, install the Claude Code config into ~/.claude, drive the installer, smoke-test it against a sandbox, or run its test suite.

★ 7