stitch::upload-to-stitch

Upload images, HTML, and markdown files directly to Stitch projects.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/qapdex-maker/stitch-skills-collection --skill stitch-upload-to-stitch-qapdex-maker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stitch::upload-to-stitch
Source: https://github.com/qapdex-maker/stitch-skills-collection/tree/main/plugins/stitch-design/skills/upload-to-stitch
Command: npx skills add https://github.com/qapdex-maker/stitch-skills-collection --skill stitch-upload-to-stitch-qapdex-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Skill overcomes token limits in MCP tools by directly uploading local assets to a Stitch project, ensuring that files like images, HTML, and markdown documents can be uploaded successfully.

Core Features & Use Cases

  • Direct Uploads: Uploads images, mockups, HTML, and markdown files directly to Stitch projects.
  • Token Limit Workaround: Bypasses the base64 encoding token limit of MCP tools for direct file uploads.
  • Use Case: When direct MCP tool calls fail or truncate due to token limits, use this Skill to upload assets like design mockups or extracted HTML pages to Stitch projects.

Quick Start

Run the upload script to upload a file 'mockup.png' to the 'my-project' Stitch project. Make sure to confirm the file before execution.

Frequently Asked Questions about stitch::upload-to-stitch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload large design mockups to a Stitch project without hitting token limits?

To upload large design mockups without hitting token limits, use a direct file upload script to bypass base64 encoding limits. This uploads local images and HTML directly to your Stitch project, preventing truncation.

Why does my MCP tool truncate file uploads to Stitch projects?

MCP tools truncate file uploads because base64 encoding large files exceeds token limits. Directly uploading local assets bypasses this mechanism, ensuring images and markdown files transfer completely to your Stitch project.

What do I need to upload local files directly to a Stitch project?

You need local file paths, a valid API key, and your target Stitch project ID. Providing these inputs allows the upload script to transfer images, mockups, and HTML directly without MCP interference.

Can I upload markdown and HTML files to Stitch using this method?

Yes, you can upload markdown and HTML files directly to Stitch. The script handles various file types, making it ideal for transferring extracted HTML pages and markdown documents into Stitch projects efficiently.

When should I use a direct upload script instead of MCP tools for Stitch?

Use a direct upload script when MCP tool calls fail or truncate due to token limits. It is specifically designed for uploading large local assets like design mockups that exceed base64 encoding constraints.