winlab-slides-guidelines_skill
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill nycu-winlab/winlab-skills --skill winlab-slides-guidelines- SKILL.md3.4 KB
Overview
This skill reviews and guides creation of WinLab presentation slides to ensure compliance with WinLab formatting and content standards. It enforces RFC 2119-style requirements and helps authors produce clear, consistent, and presentation-ready slides. Use it when creating, editing, or validating PowerPoint or slide decks for WinLab events or reports.
How this skill works
The skill inspects slide titles, structure, lists, abbreviations, diagrams, and multi-slide content against MUST/SHOULD requirements. It flags violations of absolute rules first (MUST/MUST NOT), then evaluates recommended items (SHOULD) and optional choices (MAY). It returns actionable feedback and a checklist of items to fix, using RFC 2119 keywords to explain severity.
When to use it
- Before finalizing a WinLab presentation to ensure compliance with required rules
- When drafting slides to get guidance on title clarity and slide organization
- During peer review to detect duplicate titles, unclear bullets, or missing abbreviation definitions
- When converting article-style content into presentation format
- When adding diagrams or flowcharts to verify step descriptions are present
Best practices
- Ensure every slide has a clear, unique title that states the slide’s main point
- Structure the deck from high-level concepts to detailed evidence, grouping related content
- Keep bullet items concise and on a single line; make hierarchical relationships explicit
- Spell out full names for English abbreviations early in the deck and at first use
- Label multi-slide sequences with suffixes like “(1/2)” when content spans slides
- Include step descriptions for every flowchart, pipeline, or process diagram
Example use cases
- Convert a research report into a presentation while preserving logical flow and compliance
- Review a draft slide deck to remove duplicate titles and tighten bullet points
- Validate that all diagrams include step descriptions and timing details
- Provide revision notes highlighting REQUIRED fixes and RECOMMENDED improvements
- Train new presenters on WinLab slide conventions using a scored checklist
FAQ
It checks all MUST/REQUIRED/SHALL rules first and reports any non-compliance before reviewing recommendations.
How are multi-slide topics handled?
Use suffix notation like “(1/2)” on titles when content spans slides; the skill will flag missing suffixes as SHOULD items.
