BC Presentation
Makes talks, slide decks and sales pitches: a read-aloud lecture in Keynote or HTML, a cue-card HTML deck, or a pitch from product docs (value story, talking points, charcoal sketch). USE WHEN presentation, make me a deck, slides, slide deck, present on, give a talk on, keynote, speaker notes, present this, serve the deck, presenter mode, lecture, read-aloud talk, script for a talk, turn this essay or dictation into a talk, move this slide, reprocess the talk file, make that slide a diagram, find footage of the films I mention, make the animations autoplay, real book cover, real screenshot, too much white space, image too small, export to PPTX, sales pitch, sales narrative, sales deck, pitch deck, sales package, sales script, sales materials, product pitch, create a sales story, visual for this sales story, elevator pitch, value proposition, turn this into a pitch. NOT FOR images (Art), video (HyperFrames), web design (Webdesign), voice reading (ReadIt).
Makes talks, slide decks and sales pitches: a read-aloud lecture in Keynote or HTML, a cue-card HTML deck, or a pitch from product docs (value story, talking…
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 31. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "evals"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 12 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2370 tokens
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 968: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 6 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.