slide-library

Match investor questions to existing slides in the catalog.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill slide-library
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slide-library
Source: https://github.com/Scripsteam/scrips-stack/tree/main/slide-library
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill slide-library

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This gate enforces a catalog-driven approach to slide development, ensuring that new visuals are only created when no existing slides match investor questions.

Core Features & Use Cases

  • Read the catalog at ~/scrips-repos/scrips-slide-library/CATALOG.md
  • Match investor questions to existing slides and cite checks
  • Build new visuals only when no match exists, then update the catalog

Quick Start

Check CATALOG.md, attempt to match the investor question to existing slides, and only build a new visual if no match is found, then update the catalog.

Frequently Asked Questions about slide-library

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent duplicate slides when building investor presentations?

Catalog-driven matching prevents duplicate investor presentation slides by checking each investor question against existing entries in a slide library before authorizing any new visual creation.

What is catalog-driven slide matching and how does it work?

Catalog-driven slide matching is a gating process that reads a central CATALOG.md file, matches investor questions to existing slides, and blocks unnecessary slide creation when a visual match already exists.

How do I match investor questions to existing slides in a library?

You match investor questions to existing slides by reading the CATALOG.md file, comparing questions against catalog entries to cite matching checks, and building a new visual only if no match is found.

Do I need a specific catalog file format to gate slide creation?

Yes, the slide creation gating process requires a markdown catalog file located specifically at ~/scrips-repos/scrips-slide-library/CATALOG.md to read and match existing slides successfully.

What happens to the slide catalog when a new visual is created?

When a new visual is created because no existing slide matched an investor question, the gating process enforces a catalog update so the new slide is recorded for future matching.

When should I not create a new slide for an investor deck?

You should not create a new slide for an investor deck when the gating process finds an existing slide in the catalog that already matches the investor question, preventing unnecessary visual creation.