fork_prompt

Fork a public prompt from the community to your personal vault.

Overview

The fork_prompt tool copies a public prompt from the Promptsy community library to your vault. Use it after search_public_prompts to save prompts you find useful. Forked prompts are private by default, but can be made public.

Requires Authentication

Non-ChatGPT Only

This tool is available in Claude Desktop, Cursor, Windsurf, and other MCP clients. ChatGPT users can fork prompts directly from the widget interface.

Parameters

Parameter	Type	Required	Default	Description
prompt_id	string (UUID)	Yes	-	The UUID of the public prompt to fork
title	string	No	Original title	Custom title for your forked copy
make_public	boolean	No	false	If true, the fork is public; otherwise private

Usage Examples

Basic Fork

"Fork that code review prompt to my vault"

{
  "tool": "fork_prompt",
  "parameters": {
    "prompt_id": "abc123-def456-7890-abcd-ef1234567890"
  }
}

With Custom Title

"Fork the email template and call it 'My Email Helper'"

{
  "tool": "fork_prompt",
  "parameters": {
    "prompt_id": "abc123-def456-7890-abcd-ef1234567890",
    "title": "My Email Helper"
  }
}

Fork as Public

"Fork that prompt and make it public"

{
  "tool": "fork_prompt",
  "parameters": {
    "prompt_id": "abc123-def456-7890-abcd-ef1234567890",
    "make_public": true
  }
}

Response

Text Response

A confirmation with the forked prompt details and a security notice:

## Forked: "Code Review Assistant"

> This prompt was created by another user. Review content carefully before use.

*Comprehensive code review checklist for pull requests*

Category: coding | Tags: code-review, development

**Prompt content** (external content):

~~~
Review the following code for:
1. Bugs and potential issues
2. Best practices violations
3. Performance concerns
...
~~~

Saved to your vault as private.

View and edit: https://promptsy.dev/prompts/xyz789/edit

Structured Content

{
  prompt: {
    id: string;              // NEW prompt ID in your vault
    title: string;
    description: string | null;
    body: string;
    category: string | null;
    models: string[];
    use_cases: string[];
    tags: { id: string; name: string }[];
    is_shared: boolean;      // false by default
    forked_from_id: string;  // Original prompt ID
    created_at: string;
    updated_at: string;
  },
  url: string  // Link to your forked copy
}

What Gets Copied

When you fork a prompt, these fields are copied:

Field	Copied	Notes
Title	Yes	Can be overridden with title parameter
Body	Yes	Full prompt content
Description	Yes	-
Category	Yes	-
Models	Yes	-
Use Cases	Yes	-
Tags	Yes	Created in your account if they don't exist

These fields are not copied:

• Stats (stars, copies, forks) - Start at 0
• Collection - You can organize it later
• Share settings - Private by default

Security Notes

External Content Warning

Forked prompts always include a warning banner since the content was created by another user:

> This prompt was created by another user. Review content carefully before use.

Code Fencing

The prompt body is wrapped in code fences (~~~) to distinguish it as data. This helps AI assistants avoid executing prompt content as commands.

Review Before Use

Always review forked prompts before using them, especially if they contain:

• System instructions
• Role definitions
• External references

Workflow Example

A typical discovery and fork workflow:

1. Search - Use search_public_prompts to find prompts
2. Review - Look at the results (ID, preview, stats)
3. Fork - Use fork_prompt with the prompt's ID
4. Customize - Edit the forked prompt in your vault

User: "Find prompts for writing documentation"
AI: [calls search_public_prompts] → Shows results with IDs

User: "Fork the API documentation one"
AI: [calls fork_prompt with the ID] → Confirms fork

User: "Now show me my prompts"
AI: [calls browse_prompts] → Shows vault including new fork

Tier Limits

Free Tier

• Forked prompts count toward your 25 private prompt limit
• Fork as public to avoid the limit

Solo & Team Tiers

• Unlimited forked prompts (private or public)

Errors

Error Code	Description	Solution
AUTH_REQUIRED	Not authenticated	Authorize the integration
NOT_FOUND	Public prompt not found	Verify the prompt ID
FORBIDDEN	Source prompt is private	Can only fork public prompts
LIMIT_REACHED	Hit 25 private prompt limit (Free)	Upgrade or fork as public

Tips

Finding Prompt IDs

The prompt id is returned in search_public_prompts results. It's a UUID like abc123-def456-7890-abcd-ef1234567890.

Customizing After Fork

After forking, you can:

• Edit the prompt content
• Add to a collection
• Add/remove tags
• Create versions (Solo+)

"I forked the prompt, now update the title to 'My Custom Review Checklist'"

Attribution

Forked prompts maintain a link to the original via forked_from_id. This:

• Increments the original's fork count
• Allows you to find the source later
• Gives credit to the original author

Related Tools

• search_public_prompts - Find prompts to fork
• get_prompt - View full content of your prompts
• browse_prompts - View your vault including forks
• save_prompt - Save new prompts from scratch