Skill: Public Files

Description

Upload reference files (images, documents) for use in outline generation. This skill documents the public API at /api/v2/files (PublicApiFileController). Flow: 1) POST /prepare → get upload_url and s3_key; 2) PUT file to upload_url; 3) POST /confirm; use s3_key in file_s3_keys when calling slide-deck outline/generate. Authenticate with X-API-KEY header. Max 20 MB; allowed types: PDF, DOCX, PPTX, TXT, MD, PNG, JPEG, WebP, SVG, BMP, TIFF, HEIC, HEIF, AVIF, ICO.

---

TypeScript types (request / response)

Mirrors PublicApiFileController (/api/v2/files) data classes.

// --- Prepare (POST) ---
type PrepareFileUploadRequest = {
  file_name: string;   // max 255 chars
  mime_type: string;
  size: number;        // 1 to 20*1024*1024
};
type PrepareFileUploadResponse = {
  upload_url: string;
  s3_key: string;
  expires_at: string;  // ISO 8601, ~10 min
};

// --- Confirm (POST) ---
type PublicApiConfirmFileUploadRequest = { s3_key: string };
type PublicApiConfirmFileUploadResponse = { s3_key: string; uploaded: boolean };

// --- Delete (POST) ---
type PublicApiDeleteFileRequest = { s3_key: string };
type PublicApiDeleteFileResponse = { success: boolean };

// --- Download URL (POST) ---
type PublicApiDownloadUrlRequest = {
  s3_key: string;
  expiry_seconds?: number;  // 60–604800, default 3600
};
type PublicApiDownloadUrlResponse = {
  download_url: string;
  expires_at: string;
};

---

Prepare Public File Upload

Request body: PrepareFileUploadRequest. Response: PrepareFileUploadResponse. Then PUT file to upload_url with matching Content-Type.

curl -X POST "$LAYERPROOF_BASE_URL/api/v2/files/prepare" \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: $LAYERPROOF_API_KEY" \
  -d '{"file_name":"doc.pdf","mime_type":"application/pdf","size":1024}'

---

Confirm Public File Upload

Request body: PublicApiConfirmFileUploadRequest. Response: PublicApiConfirmFileUploadResponse.

curl -X POST "$LAYERPROOF_BASE_URL/api/v2/files/confirm" \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: $LAYERPROOF_API_KEY" \
  -d '{"s3_key":"<s3_key_from_prepare>"}'

---

Delete Public File

Request body: PublicApiDeleteFileRequest. Response: PublicApiDeleteFileResponse.

curl -X POST "$LAYERPROOF_BASE_URL/api/v2/files/delete" \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: $LAYERPROOF_API_KEY" \
  -d '{"s3_key":"<s3_key>"}'

---

Get Public File Download URL

Request body: PublicApiDownloadUrlRequest. Response: PublicApiDownloadUrlResponse.

curl -X POST "$LAYERPROOF_BASE_URL/api/v2/files/download-url" \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: $LAYERPROOF_API_KEY" \
  -d '{"s3_key":"<s3_key>","expiry_seconds":3600}'

---

Agent behavior

When the user asks to upload or manage reference files (for outlines), do the following.

1. Choose the right endpoint

User intent	Endpoint	Method
Get upload URL for a file	/api/v2/files/prepare	POST
Confirm file uploaded to S3	/api/v2/files/confirm	POST
Delete a file by s3_key	/api/v2/files/delete	POST
Get download URL for a file	/api/v2/files/download-url	POST

2. Build and run the request

Step 1 — Check environment variables first. Before running any curl command, verify both LAYERPROOF_BASE_URL and LAYERPROOF_API_KEY are set on the user's machine:

if [[ -z "${LAYERPROOF_BASE_URL}" ]]; then
  echo "ERROR: LAYERPROOF_BASE_URL is not set."
  return 1
fi
if [[ -z "${LAYERPROOF_API_KEY}" ]]; then
  echo "ERROR: LAYERPROOF_API_KEY is not set."
  return 1
fi

If running from a project directory with a .env.local file, load it first:

if [[ -f .env.local ]]; then
  set -a
  source .env.local
  set +a
fi

Step 2 — Auth: Include X-API-KEY: $LAYERPROOF_API_KEY. Read env vars; if missing, tell the user. Step 3 — Body: All endpoints use JSON body (file_name, mime_type, size for prepare; s3_key for confirm/delete/download-url). Run curl and show the result.

3. Upload flow

After prepare: tell the user to PUT the file to upload_url with Content-Type: <mime_type>, then call confirm with the returned s3_key. Use that s3_key in file_s3_keys when calling slide-deck outline/generate.

4. Response handling

• Always show the raw JSON response in a JSON code block.
• If the response contains a URL for an image, show the image and the JSON.
• On error, show the response body and status code.

5. Example workflows

Workflow A — User: "Upload a reference PDF for outline generation."

1. POST /api/v2/files/prepare with {"file_name":"brief.pdf","mime_type":"application/pdf","size":<bytes>}; get upload_url, s3_key, expires_at.
2. User PUTs file to upload_url with Content-Type: application/pdf. POST /api/v2/files/confirm with {"s3_key":"<s3_key>"}.
3. Use this s3_key in slide-deck POST .../outline/generate body as file_s3_keys: ["<s3_key>"].

Workflow B — User: "Upload two reference files (PDF + DOCX), confirm both, then generate an outline that uses them."

1. For first file: prepare → user uploads → confirm; capture s3_key_1. For second: prepare → upload → confirm; capture s3_key_2.
2. Hand off to slide-decks: resolve projectId and slideDeckId. POST .../outline/generate with {"prompt":"...", "slide_count":5, "file_s3_keys":["<s3_key_1>","<s3_key_2>"]}.
3. Poll jobs for activity_id; when DONE, GET deck to show outline that was informed by the references.

Workflow C — User: "Get a download URL for a file I uploaded earlier (I have the s3_key), then delete it when done."

1. POST /api/v2/files/download-url with {"s3_key":"<s3_key>","expiry_seconds":3600}; show download_url and expires_at.
2. When user is done: POST /api/v2/files/delete with {"s3_key":"<s3_key>"}; show success response. Warn that delete is irreversible.

---

Response format (required)

• (if response contains url to show image) please show image and show json response instead of table
• Always show the raw JSON response (verbatim) in a JSON code block.
• If the response contains a URL for an image, render/show the image and also show the JSON response (do not convert to a table).