1. Conduid
  2. AI
  3. The Prompt Library
MCP server · AI

The Prompt Library

A curated collection of production‑ready AI prompts with MCP integration, organised for humans and machines alike.

39Low

Scored 4 months ago · breakdown

About The Prompt Library

The Prompt Library is an MCP server in the AI category: a curated collection of production‑ready AI prompts with MCP integration, organised for humans and machines alike. It has been installed 0 times through Conduid.

Install

Clone
git clone https://github.com/JuliusBrussee/the-prompt-library

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about The Prompt Library

Powered by Claude · Grounded in docs

I know everything about The Prompt Library. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • ·Scoped permissionsNot checked yet.

README

The Prompt Library

A curated collection of production-ready AI prompts, organised for humans and machines alike.

Stars Prompts License


Why this library?

  • Ready-to-Run: Each prompt is a self-contained YAML file with a clear role, objective, and requirements.
  • Searchable & Hackable: Browse prompts on the website or access them programmatically with the provided tools.
  • Quality-Gated: Every contribution is linted and validated by CI to maintain high standards.
  • Includes AI System Prompts: Contains system prompts from a variety of AI models, including Codex, ChatGPT, Claude, Cluely, Lovable, and more.
  • Community-Driven: Contributions are welcome via Discussions, Issues, or Pull Requests.

Getting Started

Follow these steps to set up the project and its tools on your local machine.

1. Set Up the Project

First, clone the repository and navigate into the project directory:

git clone https://github.com/juliusbrussee/the-prompt-library.git
cd the-prompt-library

2. Install Dependencies

It is recommended to use a virtual environment. Then, install the required Python packages using pip:

# Create and activate a virtual environment (optional but recommended)
python3 -m venv .venv
source .venv/bin/activate

# Install dependencies
pip install -r src/prompt_toolkit/requirements.txt

3. Build the Search Index

The library uses a JSON index for fast prompt searching. Build it by running:

python3 -m src.prompt_toolkit.build_index

You only need to run this once initially, or whenever you add or modify prompt files.


Usage

You can interact with the prompt library in several ways: as a command-line tool, by running automated workflows, or by connecting to it as an MCP server.

1. Find and Use Prompts (CLI)

The interactive script (src/prompt_toolkit/interactive.py) is the primary way to find and use prompts.

  • find <query>: Searches the library for prompts matching your keywords.
  • get <query>: Retrieves the single best-matching prompt.
  • get <query> --interactive: Starts a guided session to select a prompt and fill in its placeholders.

Examples:

# Find relevant prompts by keyword
python3 -m src.prompt_toolkit.interactive find "code documentation"

# Get the best prompt for a task
python3 -m src.prompt_toolkit.interactive get "Create a unit test for my function"

# Use interactive mode to get help with a code review
python3 -m src.prompt_toolkit.interactive get "code review" --interactive

2. Run Automated Workflows

Workflows chain multiple prompts together to accomplish complex tasks. They are defined in .workflow.yaml files inside the /prompt_workflows directory.

How to Run a Workflow:

Use the src/prompt_toolkit/workflow.py script to execute a workflow file.

# Example: Transform a user story into code and tests
python3 -m src.prompt_toolkit.workflow run prompt_workflows/user-story-to-code-test.workflow.yaml

# Example: Generate a content marketing campaign
python3 -m src.prompt_toolkit.workflow run prompt_workflows/content-marketing-campaign.workflow.yaml

3. Test Prompts (WIP)

The testing framework validates a prompt's output against a set of assertions using a real LLM. Tests are defined in .test.yaml files in the /tests directory.

LLM Configuration:

  1. Install LLM Libraries:
    pip install google-generativeai openai
    
  2. Set API Keys: For the tool to work, you must set your LLM provider's API key as an environment variable.
    export GEMINI_API_KEY="YOUR_API_KEY"
    export OPENAI_API_KEY="YOUR_API_KEY"
    
  3. Configure Defaults (Optional): You can set a default LLM provider and model in a mcp_config.yaml file at the project root.
    # mcp_config.yaml
    llm_config:
      default_provider: gemini
      default_model: gemini-pro
    

How to Run Tests:

Use the src/prompt_toolkit/testing.py script to run a test file.

# Run a test file using the default configured LLM
python3 -m src.prompt_toolkit.testing tests/unit_test_generator.test.yaml

# Override the LLM provider and model for a specific run
python3 -m src.prompt_toolkit.testing tests/unit_test_generator.test.yaml --llm-provider openai --llm-model gpt-4

4. Use as an MCP Server

The library includes a server that exposes its tools over the Model Context Protocol (MCP), allowing clients like the Gemini CLI to connect to it.

Running the Server:

Once you have installed dependencies and built the index, you can start the server:

python3 -m src.prompt_toolkit.mcp_server

Connecting with Gemini CLI:

To connect the Gemini CLI to the server, create a .gemini/settings.json file in the root of this project with the following content:

{
    "mcpServers": {
        "prompt-library": {
            "command": "python3",
            "args": [
                "-m",
                "src.prompt_toolkit.mcp_server"
            ],
            "transport": "stdio",
            "trust": "trusted"
        }
    }
}

With this file in place, running /mcp in the Gemini CLI from this directory will connect to the server and list its available tools.


Project Structure

prompt-library/
├── data/                   # CSV / JSON bulk exports
├── docs/                   # Website source code
├── prompts/                # Individual YAML prompts split by domain
├── prompt_workflows/       # Definitions for multi-step prompt sequences
├── schemas/                # YAML schemas for prompts, tests, and workflows
├── src/                    # Python source code for all tooling
│   └── prompt_toolkit/
└── tests/                  # Definitions for prompt test cases

Prompt Schema

All prompts adhere to a standard YAML format for consistency and machine readability.

Field Description
role Persona framing the assistant
objective One-sentence goal of the task
requirements Bullet list of must-haves
placeholders List of dynamic tokens like {topic}
output_format Expected structure (e.g., Markdown table)
tags Optional keywords for search

The official schema is defined in schemas/prompt.schema.yaml.


Contributing

We love new prompts! Please read CONTRIBUTING.md for style guidelines and open a PR. If you’re unsure, create a Discussion first.


License

MIT © Julius Brussee

If you use this library in academic work, please cite it.

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About The Prompt Library

How do I install The Prompt Library?

Run git clone https://github.com/JuliusBrussee/the-prompt-library, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is The Prompt Library safe to use with an AI agent?

Its trust score is 39 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is The Prompt Library still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.