ckm:slides

Overview of ckm:slides skill

What ckm:slides skill is for

ckm:slides is a presentation-building skill for creating strategic HTML slide decks, not just slide copy. It combines deck structure guidance, copywriting formulas, layout patterns, and an HTML template that supports responsive slides and optional Chart.js visuals. If you want an AI assistant to turn a rough deck idea into a more presentation-ready output with structure and implementation hints, this skill is a stronger fit than a generic “make me slides” prompt.

Best-fit users and jobs-to-be-done

The best fit for ckm:slides is someone who needs to produce persuasive slide decks such as pitch decks, sales presentations, product demos, QBRs, board updates, or conference-style decks. It is especially useful when the real task is one of these:

• choose the right deck structure for the audience
• turn messy notes into slide-by-slide messaging
• generate HTML slides instead of PowerPoint-native files
• include KPI or chart sections with a web-friendly approach

What makes ckm:slides different

The main differentiator is that ckm:slides ships with reusable references instead of only a short prompt. The skill points the model to:

• references/slide-strategies.md for deck archetypes and emotion arcs
• references/copywriting-formulas.md for persuasive slide copy patterns
• references/layout-patterns.md for slide layout choices
• references/html-template.md for a concrete HTML deck scaffold
• references/create.md for the creation entrypoint

That makes it more guided than ordinary prompting, especially for users who want a deck strategy plus HTML output.

When not to choose this skill

Skip ckm:slides if you need:

• native .pptx, Keynote, or Google Slides export
• heavy visual design automation with assets and brand systems already wired in
• complex data storytelling logic beyond simple Chart.js-ready patterns
• a one-click slide generator with no prompt shaping

This skill is best treated as a structured drafting aid for slide decks, not a full presentation production pipeline.

How to Use ckm:slides skill

How to install ckm:slides

A practical ckm:slides install command is:

npx skills add https://github.com/nextlevelbuilder/ui-ux-pro-max-skill --skill slides

After installation, make sure your assistant can access the skill files under .claude/skills/slides or the equivalent local skill directory in your setup.

How the skill is invoked in practice

The skill frontmatter exposes an argument hint of:

[topic] [slide-count]

The repo also defines one routed subcommand:

• create

In practice, that means your call should include both the intent and the task details, for example:

• slides create investor pitch 10
• slides create QBR 12
• slides create product demo 6

Because references/create.md is minimal, output quality depends heavily on the task details you provide after the subcommand.

What input ckm:slides needs to work well

Give ckm:slides enough context to choose the right strategy and write slide-level content. The most useful inputs are:

• audience: investors, prospects, executives, internal team
• deck goal: raise funding, close a deal, teach, align, report
• slide count or time limit
• product/company description
• must-include metrics, proof points, objections, or CTA
• preferred tone: formal, bold, technical, executive
• output format: outline only, copy + structure, or full HTML slides

Without this context, the skill can still draft a deck, but the result will be generic.

Turn a rough request into a strong ckm:slides usage prompt

Weak:
Use ckm:slides for Slide Decks about our product.

Stronger:
Use ckm:slides create to build a 9-slide sales deck for IT buyers at mid-market SaaS companies. Goal: book a technical demo. Include problem, cost of inaction, solution overview, proof, differentiators, ROI, objection handling, and CTA. Tone should be confident and concise. Output slide-by-slide copy first, then HTML structure suggestions.

Why this works better:

• it gives the skill a known audience
• it maps to deck patterns in references/slide-strategies.md
• it provides persuasion requirements that fit the copy formulas reference
• it tells the model what deliverable to produce

Best workflow for first-time users

A reliable ckm:slides guide workflow is:

1. Pick the deck type from references/slide-strategies.md.
2. Fix the slide count and audience before generating.
3. Ask for a slide outline first.
4. Review whether the flow matches your persuasion goal.
5. Then ask for full slide copy.
6. If you need implementation output, ask for HTML using references/html-template.md.
7. Add charts only after the narrative is stable.

This two-pass approach usually beats generating full HTML on the first attempt.

Files to read first before relying on output

If you want to understand the skill quickly, read these files in order:

1. SKILL.md
2. references/slide-strategies.md
3. references/create.md
4. references/copywriting-formulas.md
5. references/layout-patterns.md
6. references/html-template.md

This path tells you what the skill is trying to optimize: strategy first, copy second, layout third, implementation last.

How to choose the right deck strategy

The highest-value reference is references/slide-strategies.md. It includes deck types such as:

• YC Seed Deck
• Sales Pitch
• Product Demo
• QBR
• Board Meeting
• Webinar
• Case Study

Do not ask for “a presentation” if you already know the scenario. Ask for the nearest strategy explicitly. That reduces structural drift and makes the slide sequence more persuasive.

How to get better slide copy from the skill

references/copywriting-formulas.md is useful when a deck needs persuasion, not just information. You will usually get stronger output if you specify the copy pattern per slide type, for example:

• use PAS for the problem slide
• use Cost of Inaction for urgency
• use FAB for product capability slides
• use AIDA for the closing CTA

This is one of the clearest ways to improve ckm:slides usage without changing tools.

How to use ckm:slides for Slide Decks in HTML

If your target is a browser-based presentation, tell the skill to produce HTML slides that follow the provided template. The repository’s template includes:

• viewport-aware deck container
• CSS-token-style theming
• responsive layout patterns
• Chart.js CDN integration

Ask for:

• one section per slide
• semantic slide titles
• placeholder chart containers only where data exists
• minimal inline JS unless interaction is required

This keeps the output easier to review and adapt.

Common constraints and tradeoffs

Before adopting ckm:slides, know these limits:

• the skill provides references, not an end-to-end app
• the create instruction file is sparse, so prompting quality matters
• HTML output may still need manual cleanup for production use
• charts are template-friendly, but the repo does not give deep data-modeling rules
• there is no evidence here of built-in export to PowerPoint or Slides tools

If your workflow depends on exact downstream file formats, treat this skill as a drafting layer, not the final renderer.

ckm:slides skill FAQ

Is ckm:slides skill better than a normal prompt?

Usually yes, if your task includes both messaging and deck structure. A generic prompt can produce slides, but ckm:slides skill gives the assistant reusable decision support: strategy options, copy formulas, layout patterns, and HTML scaffolding. That reduces guesswork when the deck has a real persuasion job.

Is ckm:slides good for beginners?

Yes, with one condition: beginners should start by naming the audience and deck type clearly. The skill helps with structure, but it does not replace knowing what outcome the deck needs. If you can answer “who is this for?” and “what decision should they make?”, you can use it effectively.

What kinds of decks fit best?

Best-fit decks are:

• investor pitches
• sales decks
• product demos
• QBRs
• board or leadership updates
• case studies
• workshops and talks

It is less compelling for purely decorative slide design or highly custom motion-heavy presentations.

Does ckm:slides generate finished presentations?

Not by itself. ckm:slides can help generate deck structure, slide copy, and HTML-based presentation code, but you should expect to review, edit, and adapt the result. Think “accelerated first draft plus implementation scaffold,” not “final presentation with zero editing.”

Can I use ckm:slides without HTML output?

Yes. A good pattern is to use the skill for:

• deck strategy selection
• slide-by-slide outline
• headline and body copy
• chart suggestions
• CTA refinement

Then move the content into your own presentation tool.

When should I not use ckm:slides?

Avoid it when your main need is:

• native slide software output
• highly branded design production
• exact visual fidelity from a design system not represented in the prompt
• dense analytical storytelling that needs domain-specific chart reasoning

In those cases, a custom workflow may fit better than ckm:slides install and prompting alone.

How to Improve ckm:slides skill

Give ckm:slides stronger business context

The fastest way to improve ckm:slides skill output is to provide commercial context, not just topics. Include:

• target audience
• presentation goal
• key objections
• proof points
• desired next step

For example, “AI security platform, selling to CISOs, objection is compliance risk, proof is 3 enterprise logos and 42% reduction in triage time, CTA is book pilot” will outperform “make a security deck.”

Ask for structure before full copy

A common failure mode is accepting the first full deck draft. Instead, ask ckm:slides to produce:

1. recommended deck strategy
2. slide list with purpose
3. copy formulas per slide
4. only then the actual slide copy

This catches weak sequencing early and avoids rewriting every slide later.

Match the layout pattern to the slide job

Use references/layout-patterns.md intentionally. Better prompts say things like:

• “Use a big number hero for KPI impact”
• “Use a comparison table for competitor positioning”
• “Use a two-column split for problem vs solution”
• “Use pricing cards only if we have clear tiers”

When the layout matches the message, the deck feels more deliberate and less template-driven.

Be selective with charts

Because the skill references Chart.js, users often over-request charts. Improve output by limiting charts to data that actually benefits from visualization:

• trends over time
• before/after metrics
• category comparisons
• share breakdowns

Do not add charts to weak or low-confidence data. A strong big-number slide is often better than a decorative graph.

Provide slide-level source material

If you already have raw notes, feed them slide by slide or section by section. Useful inputs include:

• founder notes
• sales call takeaways
• KPI tables
• case study bullets
• customer quotes
• pricing logic

This lets ckm:slides transform material instead of inventing too much, which reduces fluff.

Improve prompts with formula and tone constraints

If output feels generic, add constraints such as:

• “Use PAS on the problem slide”
• “Keep each slide to one headline and three bullets max”
• “Avoid hype words”
• “Write in an executive tone”
• “End with one clear CTA”

These constraints align well with the repository’s copywriting reference and usually sharpen the result fast.

Iterate after the first draft with targeted revisions

Do not ask for “make it better.” Ask for specific upgrades:

• tighten investor credibility
• reduce jargon for non-technical buyers
• add stronger cost-of-inaction framing
• cut slide count from 12 to 8
• make the CTA more concrete
• replace weak proof with metrics-first messaging

This kind of revision prompt helps ckm:slides refine the deck in a controlled way.

Improve ckm:slides skill by extending local references

If you plan to use ckm:slides often, the biggest improvement may be local customization. Add your own:

• brand tokens for the HTML template
• approved messaging frameworks
• common deck structures by audience
• proof and objection libraries
• chart snippets your team reuses

The repository already organizes knowledge in references/, so extending that pattern is a practical way to make the skill more valuable over time.