BB beamer
House rules and craft for LaTeX Beamer slide decks (lectures, seminars, talks), built from the author's own Overleaf edits and published slide-design guidance. Covers storyboarding before LaTeX, frame titles, slide prose, word and frame budgets, layout that avoids overfull boxes, XeLaTeX fonts and Korean (xeCJK), color, figures and screenshots, Overleaf source hygiene, speaker notes, and the build and QA loop with a contact sheet. Use whenever a .tex deck, a beamer theme (.sty), a storyboard, slides, frames, overfull boxes in a deck, or an Overleaf slide repo is being written, edited, reviewed, or built, even without the word Beamer. A course skill (for example ba3-skills) supplies that course's facts, schedule and frame skeleton, and this skill supplies the craft alongside it. Not for HTML or PowerPoint decks, posters, or papers.
House rules and craft for LaTeX Beamer slide decks (lectures, seminars, talks), built from the author's own Overleaf edits and published slide-design guidance.
As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 65/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 12 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 117 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3710 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Description length 842: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 15 headings
- +3Step-by-step instructions: 117 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.