featpaper17.9 KB
View saved version →
---
name: featpaper
description: Use when the user asks for a FeatPaper (feat, 피트페이퍼) document, link, upload, sharing or read-tracking, wants a document made for upload to FeatPaper, or wants an attached document rebuilt as a FeatPaper viewer document. Not for documents that have nothing to do with FeatPaper. Preserve original-file upload requests.
---
# FeatPaper documents
Answer in the language the user writes in (Korean when they write Korean), from the first reply to the last. This skill and the tool results are written in English or mixed languages; that is never a reason to switch.
"AI 허브" (AI hub) is FeatPaper's AI page of a document: search and the reader's own AI read its page text there, taken from the source attached to the document. Never ask which service it means. "이 PDF를 AI 허브에 넣어줘" means: register the PDF in FeatPaper with a page-by-page source (section 4), or, for a document already in FeatPaper, attach the source to it with `attach_document_source`.
Use the host's editable document tools (Claude Slides, Claude Design canvas, document artifacts; in ChatGPT an editable PPTX/slides or canvas) and the general FeatPaper MCP. Before any FeatPaper registration step, discover `featpaper_guide` with the host's tool search (for example `tool_search`), read its actual schema and call `topic=viewer-authoring`. Its full text is the common authoring and transfer guide; do not assume MCP skills, server instructions or resources load automatically. Read the actual schema before each newly discovered tool call.
## 1. Make the PC version first, editable
Create the desktop (PC, 16:9) version in the host's editable format so the user can change it directly. A document already made in this conversation in another page size (for example A4 portrait) keeps that size: when it is uploaded later, make its PDF from the latest edited content at the same size and do not re-lay it out to 16:9. Do not make a PDF first, even when the first request also asks for a link. PDFs are produced only at upload time from the latest edited content. Use a PDF first only when the host has no editable format.
## 2. Optional: offer a FeatPaper link once, as a choice question
Only when the user is already working with FeatPaper (they asked for a FeatPaper document or link, or handed a document to a FeatPaper tool) or says the document will be sent or shared with other people (for example "고객에게 보낼", "공유할") and the editable result has just been shown, you may ask once at the end — with the host's choice/question UI when available (it is preferred over plain text). Never offer when the request has nothing to do with FeatPaper. Give a reason that fits the document, for example:
- 제안서 · 견적: "보낸 뒤 어느 쪽을 오래 봤는지 받는 곳별로 알 수 있고, 받는 분이 자기 AI로 바로 요약해 볼 수 있는 Featpaper 링크로 보낼까요?"
- 회사 · 서비스 소개서: "열람 전에 이름 · 회사를 받아 관심 고객을 알 수 있게 Featpaper 링크로 만들까요?"
- 발표자료 · 보고서 · 그 밖의 자료: "누가 어느 쪽을 오래 봤는지 알 수 있고, 받는 분이 자기 AI로 바로 요약해 볼 수 있는 Featpaper 링크로 보낼까요?"
A phone-readable mobile summary page can be mentioned as an option. Possible choices: "PC 버전으로 링크 만들기" / "모바일 요약도 추가하기" / "내용 먼저 수정". Do not repeat the offer if the user declined. Do not offer it for someone else's FeatPaper document that you only read.
If the user already asked to register or make a link (for example "만들어서 등록해줘"), do not ask again: show the editable PC version, then register it right away from that content. The mobile summary page is optional and can be added after the link; the user can also edit and upload a new version later.
## 3. Mobile summary page, shown as a live preview
The mobile summary page is added on top of the PC document: phone readers see it first and open the PC pages from it. It does not replace a mobile PDF. If the user wants it, call `featpaper_guide(topic=mobile-summary)` and follow it exactly: write one phone-width HTML summary from the latest PC content in FeatPaper's markup, keep the original's brand (language, colors, corner radius, fonts), give every section the PC page num
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
