Update to Paperpal

{
  "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.",
  "included_files": [],
  "name": "manuscript-readiness",
  "skill_md_contents": "---\nname: manuscript-readiness\ndescription: 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.\n---\n\n# Assess manuscript readiness\n\n1. Resolve the document source before assessing readiness:\n   - Current message has a DOCX/PDF attachment: call `check_attached_document`.\n   - 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.\n   - 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.\n2. Let the upload/check-selection app run before attempting an assessment.\n3. Base the assessment only on completed Paperpal checks and their returned details.\n4. State the coverage first: completed checks versus pending, failed, or unavailable checks.\n5. Group attention into `Resolve before submission`, `Review`, and `No reported issue` only when supported by results.\n6. Keep the recommendation concise and direct the user to Paperpal for editing.\n7. In case of a check/API failure, direct the user to https://edit.paperpal.com/ to retry.\n\nNever convert an incomplete check set into an overall approval. Treat plagiarism output as a signal requiring human review, not proof of misconduct.\n"
}