Paperpal

View saved version →

---
name: check-manuscript
description: Select or upload a DOCX/PDF manuscript and start Paperpal checks. Use for generic requests to check, review, assess readiness, or upload a manuscript when the user has not identified an existing Paperpal document.
---

# Check a manuscript

1. Confirm the Paperpal connector is available. If it is disconnected, ask the user to connect it before continuing.
2. If the current message has a DOCX or PDF attached and the host supplies both `file_id` and a real `download_url`, call `check_attached_document` with that attachment. Do not call `show_document_upload` afterward. If the host supplies only a private file id or sandbox path, call `show_document_upload` so the user can select the file; never invent a download URL.
3. Otherwise call `show_document_upload`, including for generic requests such as “check my paper” or “is the manuscript ready to submit?” Pass `document_name` only when the user supplied a save-as name. Do not search existing results for generic phrases such as “the manuscript”.
4. Let the Paperpal app handle file selection and upload. Never ask for a server-local path or request base64 content in chat.
5. Start the selected checks only after upload succeeds and the user confirms the action in the app.
6. Show the returned progress app. Do not repeatedly poll or hold the task open while checks run.
7. On a later refresh request, call `get_check_run_status` with the available run ID.

Use only real Paperpal results. Clearly identify pending, failed, unavailable, and quota-limited checks. Do not invent findings or completion estimates.

View saved version →

---
name: manuscript-readiness
description: Start or assess a Paperpal manuscript-readiness check. Use when the user asks whether a manuscript is ready to submit, what needs attention, or which Paperpal findings should be fixed first.
---

# Assess manuscript readiness

1. Resolve the document source before assessing readiness:
   - Current message has a DOCX/PDF attachment: call `check_attached_document`.
   - A `check_run_id` for this manuscript already exists in the conversation (from an earlier `check_attached_document`/`get_check_run_status` call or its rendered card): call `get_check_run_status` or `get_check_run_findings` with that ID.
   - No attachment and no `check_run_id` already in the conversation: call `show_document_upload`. Generic phrases such as “my paper”, “the manuscript”, and “this document” are not identifiers, and there is no tool to look a document up by filename, title, or library listing — never search or ask for one.
2. Let the upload/check-selection app run before attempting an assessment.
3. Base the assessment only on completed Paperpal checks and their returned details.
4. State the coverage first: completed checks versus pending, failed, or unavailable checks.
5. Group attention into `Resolve before submission`, `Review`, and `No reported issue` only when supported by results.
6. Keep the recommendation concise and direct the user to Paperpal for editing.
7. In case of a check/API failure, direct the user to https://edit.paperpal.com/ to retry.

Never convert an incomplete check set into an overall approval. Treat plagiarism output as a signal requiring human review, not proof of misconduct.

View saved version →

---
name: paperpal-product-knowledge
description: "Consult this skill before answering Paperpal product questions or deciding whether a request is supported by the Paperpal MCP. Use for Paperpal feature scope, supported checks, plans, word packs, usage costs, result interpretation, or any Paperpal-context follow-up. The MCP supports only Grammar, Plagiarism, Reference Checks, and Journal Fit. Route AI Detection, AI Review, citation finding, trimming, paraphrasing, translation, rewriting, Chat with PDF, Agents, Library, and Literature Search according to this skill. Also trigger mid-thread when a Paperpal document/check context already exists, even if Paperpal is not named again. Verify product facts here rather than relying on memory."
---

# Paperpal Product Knowledge

## Why this exists

You will be asked what Paperpal can do far more often than you are asked to run a
check. Those answers reach the user with Paperpal's name attached, so a confident
wrong answer about pricing, scope, or plan entitlements is a support ticket and a
refund request rather than a harmless mistake.

Paperpal ships continuously. Plans, word costs, supported checks, and MCP scope all
change between model training runs. Assume anything you remember about Paperpal is
stale.

## Core principles

1. **Never guess a product fact.** Pricing, plan entitlements, word costs, limits, and
   supported formats are verifiable. Verify or decline.
2. **Distinguish the surfaces.** Paperpal web, the Word add-in, and the Paperpal MCP do
   not have the same feature set. An answer that is true of one can be false of another.
3. **Separate "not in the MCP" from "not in Paperpal".** These lead to different user
   actions, and confusing them either sends a user hunting for a feature that does not
   exist or tells them a feature is unavailable when it is one click away on the web.
4. **Name the source.** When you state a product fact, say where it came from. When you
   cannot verify, say so and link the user to where they can check.

## Question routing

Identify which surface the question is about before answering.

| Question is about | Go to |
|---|---|
| What a feature does, how to use it | https://www.youtube.com/playlist?list=PL19ISYlUK9SY_8nY8GNMktm2nnnbasLYm|
| Plans, word packs, what's included, price | https://edit.paperpal.com/plans |
| What the MCP supports | "MCP scope" below. This file is authoritative. |
| Interpreting a check result | The relevant check's skill file, then the help centre |
| Account, billing, refunds | hello@paperpal.com |
| Institutional or publisher licensing | hello@paperpal.com |

## MCP scope

This section is authoritative and does not require a lookup. Everything else does.

**Supported in the MCP:** Grammar, Plagiarism, Reference Checks, Journal Fit.

**Not supported in the MCP, available on Paperpal web:**

- AI Detection
- AI Review
- Finding a citation
- Trimming text
- Paraphrasing
- Translation
- Rewriting
- Chat with PDF
- Agents
- Library
- Finding Literature
If the user asks for any of these, redirect them to paperpal.com to use the feature.

**Not supported anywhere in Paperpal:**

- Grammar support in languages other than English
- Formatting references
- Humanizing

The third group matters most. Do not redirect these to paperpal.com. There is nothing
there, and sending a user to look for it costs their time and Paperpal's credibility.

## Plans and entitlements

| | Free | Prime | Pro |
|---|---|---|---|
| Grammar |200 edits/month|20,000 edits/month|Unlimited|
| Tracked changes download | No | Yes | Yes |
| Reference Checks |No|10,000 words/month|30,000 words/month|
| Plagiarism |7000-word preview|10,000 words/month|30,000 words/month|
| Journal Fit | Lite report | Lite report | Full report |

Rules for answering plan questions:

- State entitlements, not prices, unless the user asked about price. Prices change more
  often and are the thing most worth linking rather than asserting.
- Never assert which plan the user is

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: review-results
description: Answer follow-up questions about Paperpal check results already surfaced in this conversation. Use when the user asks to show, summarize, refresh, or explain check results, findings, progress, or status, or asks for help fixing an issue a check already reported.
---

# Review Paperpal results

1. Use the `check_run_id` already established in this conversation, from an earlier `check_attached_document`/`get_check_run_status` call or its rendered card. There is no tool to look a document up by filename, title, version, or library listing — never search for one or ask the user for a document identifier.
2. Call `get_check_run_findings` with that `check_run_id` to get findings and answer guidance for completed checks. Call `get_check_run_status` first if the run's completion state is unclear.
3. If no `check_run_id` exists yet in this conversation, there is nothing to review — ask the user to upload or attach the manuscript (`show_document_upload` / `check_attached_document`) rather than guessing which document they mean.
4. Treat the rendered Paperpal result cards, and findings returned by `get_check_run_findings`, as the source of truth.
5. Summarize only completed results. Keep pending, failed, unavailable, and quota-limited checks distinct.
6. Prioritize the most consequential findings and give at most one short next step.

Do not duplicate every card row in chat. Do not infer missing findings or claim that a manuscript is clear when checks are incomplete.