Skip to content
Back to skills

Demo

ASecurity

Print the prismantis demo reply to eyeball every rendering feature after a change. Use after any visual change, when asked for "the demo", "show all features", "visual test", or before a release screenshot.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 21, 2026
ai-agentstypescriptshell

Works with

  • claude code
  • terminal

Security analysis

A100/100

Scanned October 21, 2026

npx -y skills add Hanafubuki/ops-control --skill demo --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Demo?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Demo
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hanafubuki-demo/badge)](https://www.skillsdirectory.com/skills/hanafubuki-demo)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: demo
description: Print the prismantis demo reply to eyeball every rendering feature after a change. Use after any visual change, when asked for "the demo", "show all features", "visual test", or before a release screenshot.
---

# Demo

The visual test. Unit tests prove the tree; this proves the look.

1. **Load the working copy** in this session (see `live-check` step 1). The new version shows only after the turn that made the edit ends.
2. **Print `docs/demo.md` verbatim as the whole final message of a turn**, with nothing before it and no tool call after it. Claude Code condenses text written right before a tool call, so the demo must close the turn.
3. **The person looks at it**, or screenshots it on the next turn (`live-check` step 3). Check:
   - `prismantis` in a heavy box on the first line, and `Roster` with a heavy rule under it
   - the table: yellow header, rules between rows, the right-aligned `Size` column, colored numbers
   - the four diagrams and the table on one row on a wide terminal, wrapping on a narrow one
   - every flowchart box and sequence participant in its own color, with matching colors at both ends of the sequence
   - a value above each bar, the tallest bar highlighted and the rest muted, labels without quotes, dim gridlines, colored axis numbers
   - shell colors: command, flags, the quoted string, `&&`
   - code blocks with a language header and no frame, and Prism colors in the TypeScript block
   - path, link and inline-code colors, the quote bar running down its paragraph and both list rows, and the green `Tip` alert box
   - accent `⧉ md`, `⧉ art` and `⧉ html` buttons on the table (`⧉ html` in a local macOS or Linux terminal only), and an accent `[ ⧉ copy ]` button on every diagram, the list, the shell block, the alert and the quote
   - the timeline figure: drawn line by line with no `── figure` header, the caption in the comment color, the `▏───▏` axis and the Provider bar in the diagram color, `✗` and `2 twice` in the theme's reddest accent color, the Handler bar and `1` in its greenest, the time labels in its most amber, those three different from each other and from the diagram color, the bars ending on the axis ticks, `⧉ source` and `⧉ art` above it
   - the Hebrew section: lines read right to left (the first bullet shows `eu-west` and `us-east` after the Hebrew, mirrored parentheses), bullets and `1.` on the right, the quote bar on the right, the table cells right aligned, and the shell comment reversed while `ls -la` stays
4. **Fix what looks wrong**, then run the demo again.
5. **Keep it current.** A new feature adds a line to `docs/demo.md` and to the checklist above. All data stays invented and neutral.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.