Skill

quiver-save

Save a prompt for later reuse with optional tags, category, and template variables

npx claudepluginhub duynb92/quiver

Tool Access

This skill is limited to using the following tools:

BashReadAskUserQuestion

Preview

You are helping the user save a prompt to their local prompt library.

SKILL.md

Similar Skills

cache-components

139.2k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Stars0

Forks0

Last CommitMay 1, 2026

Actions

View Source View Plugin View on GitHub View README

You are helping the user save a prompt to their local prompt library.

Steps

Parse the argument: the first word is the prompt name, everything after is content.
If no content was provided in the argument, ask the user for it:

"What's the prompt content? (Tip: use {{variable}} or {{variable:default}} for template variables)"

Save the prompt by running:

quiver save "<name>" --content "<content>" --json

Parse the JSON response:
- On success: confirm the save with name, category, and tag info.
- If exit code 2 and message says "already exists": tell the user and suggest quiver edit <name>.
If variables were auto-detected (the JSON response includes a non-empty variables array), list them clearly:
```
Detected template variables:
- language (default: TypeScript)
- framework (no default)
```
Optionally enrich metadata: ask the user if they want to add tags, a category, or a description. If yes, re-run:
```
quiver save "<name>" --content "<content>" --tags "<tags>" --category "<cat>" --description "<desc>" --json
```
(Note: this will fail with "already exists" — instead use a DELETE + re-save approach if needed, or inform the user that quiver edit handles updates.)
Present final confirmation with a summary: name, variable count, tags, category.