How do I install the Uv Slider Plan skill?

Run npx skillmds@latest add tomevault-io/uv-slider-plan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Uv Slider Plan safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Uv Slider Plan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Uv Slider Plan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Uv Slider Plan?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Uv Slider Plan by tomevault-io — Agent Skill

Name: Uv Slider Plan
Author: tomevault-io

Uv Slider Plan

Plan the slider workflow end-to-end by selecting which repo skills to run (content-prompts, styled-prompts, styled-artifacts) based on the user’s starting input (materials or existing prompts) and requested output (content prompt, styled prompt, images, PDF, PPTX). Uses $HUMAN_MATERIAL_PATH/slides/<deck>/ as the working root. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Slider Plan (Orchestrator)

Goal

Produce a plan only (no file edits, no rendering) that routes the user request to the right v2 skill(s):

content-prompts → material → $HUMAN_MATERIAL_PATH/slides/<deck>/prompts/content/<deck>.md
styled-prompts → content prompt + style brief → $HUMAN_MATERIAL_PATH/slides/<deck>/prompts/styled/<deck>.md
styled-artifacts → styled prompt → images + $HUMAN_MATERIAL_PATH/slides/<deck>/artifacts/<deck>/<deck>.pdf / image-PPTX $HUMAN_MATERIAL_PATH/slides/<deck>/artifacts/<deck>/<deck>.pptx

The plan must be written in the same format as the create-plan skill template.

Routing

Decide the starting point from the user’s input:

Raw notes / folder / “material” → run content-prompts
Already has $HUMAN_MATERIAL_PATH/slides/<deck>/prompts/content/<deck>.md → start at styled-prompts
Already has $HUMAN_MATERIAL_PATH/slides/<deck>/prompts/styled/<deck>.md → start at styled-artifacts

Decide the stopping point from the requested output:

Wants Content PROMPT → stop after content-prompts
Wants Styled PROMPT → stop after styled-prompts
Wants PDF / images / image-PPTX → include styled-artifacts
Wants editable PPTX → out of scope for this repo (the upstream pptx skill was proprietary)

Style selection (v2)

If the user names a style, use $HUMAN_MATERIAL_PATH/slides/styles/<style>.md.
Otherwise, use $HUMAN_MATERIAL_PATH/slides/<deck>/configs/deck.yaml (style:) if present.
If neither is available, default to $HUMAN_MATERIAL_PATH/slides/styles/blueprint.md (or ask 1 question if the choice matters).

Review policy (required)

Keep generation cheap:

Review happens on prompts (prompts/content/* and/or prompts/styled/*).
Do not plan “regenerate + review” loops for final artifacts.

Output format

Output only a plan, using the exact template structure:

# Plan
## Scope
## Action items (include the exact skill invocations and file paths)
## Open questions (max 3; ask only if blocking)

References

Routing cheatsheet: references/routing.md
Example plans: references/examples.md

Completion behavior (required)

When this skill is triggered:

Do only this step: output a plan (no file edits, no rendering).
The plan must include the exact next skill invocations and any CLI commands needed.
Do not execute the plan steps automatically.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: uv-slider-plandescription: Plan the slider workflow end-to-end by selecting which repo skills to run (content-prompts, styled-prompts, styled-artifacts) based on the user’s starting input (materials or existing prompts) and requested output (content prompt, styled prompt, images, PDF, PPTX). Uses $HUMAN_MATERIAL_PATH/slides/<deck>/ as the working root. Use when this capability is needed.---# Slider Plan (Orchestrator)## GoalProduce a **plan only** (no file edits, no rendering) that routes the user request to the right v2 skill(s):- `content-prompts` → material → `$HUMAN_MATERIAL_PATH/slides/<deck>/prompts/content/<deck>.md`- `styled-prompts` → content prompt + style brief → `$HUMAN_MATERIAL_PATH/slides/<deck>/prompts/styled/<deck>.md`- `styled-artifacts` → styled prompt → images + `$HUMAN_MATERIAL_PATH/slides/<deck>/artifacts/<deck>/<deck>.pdf` / image-PPTX `$HUMAN_MATERIAL_PATH/slides/<deck>/artifacts/<deck>/<deck>.pptx`The plan must be written in the same format as the `create-plan` skill template.## RoutingDecide the starting point from the user’s input:- Raw notes / folder / “material” → run `content-prompts`- Already has `$HUMAN_MATERIAL_PATH/slides/<deck>/prompts/content/<deck>.md` → start at `styled-prompts`- Already has `$HUMAN_MATERIAL_PATH/slides/<deck>/prompts/styled/<deck>.md` → start at `styled-artifacts`Decide the stopping point from the requested output:- Wants **Content PROMPT** → stop after `content-prompts`- Wants **Styled PROMPT** → stop after `styled-prompts`- Wants **PDF / images / image-PPTX** → include `styled-artifacts`- Wants **editable PPTX** → out of scope for this repo (the upstream `pptx` skill was proprietary)## Style selection (v2)- If the user names a style, use `$HUMAN_MATERIAL_PATH/slides/styles/<style>.md`.- Otherwise, use `$HUMAN_MATERIAL_PATH/slides/<deck>/configs/deck.yaml` (`style:`) if present.- If neither is available, default to `$HUMAN_MATERIAL_PATH/slides/styles/blueprint.md` (or ask 1 question if the choice matters).## Review policy (required)Keep generation cheap:- Review happens on **prompts** (`prompts/content/*` and/or `prompts/styled/*`).- Do **not** plan “regenerate + review” loops for final artifacts.## Output formatOutput only a plan, using the exact template structure:- `# Plan`- `## Scope`- `## Action items` (include the exact skill invocations and file paths)- `## Open questions` (max 3; ask only if blocking)## References- Routing cheatsheet: `references/routing.md`- Example plans: `references/examples.md`## Completion behavior (required)When this skill is triggered:1. **Do only this step**: output a plan (no file edits, no rendering).2. The plan must include the **exact next skill invocations** and any **CLI commands** needed.3. Do not execute the plan steps automatically.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/uv-xiao) — claim your Tome and manage your conversions.

Frequently asked questions