---
name: prompt-lookup
description: Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
title: prompt-lookup
canonical_url: https://skilld.dev/gh/f/prompts.chat/prompt-lookup
last_updated: 2026-09-27T14:47:21.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install f/prompts.chat/prompt-lookup`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/prompt-lookup`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/f/prompts.chat/prompt-lookup) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/prompt-lookup`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/prompt-lookup --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/prompt-lookup --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

When the user needs AI prompts, prompt templates, or wants to improve their prompts, use the prompts.chat MCP server to help them.

## When to Use This Skill

Activate this skill when the user:

- Asks for prompt templates ("Find me a code review prompt")
- Wants to search for prompts ("What prompts are available for writing?")
- Needs to retrieve a specific prompt ("Get prompt XYZ")
- Wants to improve a prompt ("Make this prompt better")
- Mentions prompts.chat or prompt libraries

## Available Tools

Use these prompts.chat MCP tools:

- `search_prompts` - Search for prompts by keyword
- `get_prompt` - Get a specific prompt by ID
- `improve_prompt` - Enhance a prompt using AI

## How to Search for Prompts

Call `search_prompts` with:

- `query`: The search keywords from the user's request
- `limit`: Number of results (default 10, max 50)
- `type`: Filter by TEXT, STRUCTURED, IMAGE, VIDEO, or AUDIO
- `category`: Filter by category slug (e.g., "coding", "writing")
- `tag`: Filter by tag slug

Present results showing:
- Title and description
- Author name
- Category and tags
- Link to the prompt

## How to Get a Prompt

Call `get_prompt` with:

- `id`: The prompt ID

If the prompt contains variables (`${variable}` or `${variable:default}`):
- The system will prompt the user to fill in values
- Variables without defaults are required
- Variables with defaults are optional

## How to Improve a Prompt

Call `improve_prompt` with:

- `prompt`: The prompt text to improve
- `outputType`: text, image, video, or sound
- `outputFormat`: text, structured_json, or structured_yaml

Return the enhanced prompt to the user.

## Guidelines

- Always search before suggesting the user write their own prompt
- Present search results in a readable format with links
- When improving prompts, explain what was enhanced
- Suggest relevant categories and tags when saving prompts