uploading-files
File-upload bridge for Claude Code on the Web. CCotw has no native file mount; this skill creates a throwaway GitHub branch the user can drop files onto via the github.com web UI, then fetches them locally on the next turn. Use when the user wants to upload, share, or send files into the session, or when a task clearly needs files the user has on disk that aren't in the repo.
What this skill does
# Uploading Files Claude Code on the Web has no file-upload widget and no shared mount. Whenever the user needs to get a file (image, PDF, CSV, doc, archive, anything) into the session, route them through a temporary GitHub branch on the working repo's `origin` remote. ## When to use Trigger this skill when: - The user asks to upload, attach, share, or send a file - A task clearly needs a file the user has locally that isn't in the repo (e.g. "summarize this PDF", "the spreadsheet I exported", "the screenshot from earlier") - You're about to ask the user to paste a long binary or large text blob — offer upload instead Don't trigger when the file is already in the repo, on a public URL you can fetch, or short enough to paste inline. ## Workflow The script lives at `/mnt/skills/user/uploading-files/scripts/upload.py` once installed. It must be run from inside the working git repo (it uses `origin` and `cwd`). ### Step 1 — Create the upload branch ```bash python3 /mnt/skills/user/uploading-files/scripts/upload.py init ``` This creates `upload-<short-session-id>` on origin (from the default branch) and prints a GitHub upload URL. **Show that URL to the user on its own line, with no surrounding markdown** — no `**bold**`, no `[link](...)`, no backticks. Some chat renderers concatenate trailing punctuation/markup onto the URL when the user clicks it, breaking the branch name. Bare URL only. Then tell them: > Open that link, drag the file(s) into the page, scroll to the bottom and click **Commit changes** (the default options are fine). Reply here when done. Then stop and wait for the user. Do not pretend they've uploaded. ### Step 2 — Fetch files After the user confirms the upload: ```bash python3 /mnt/skills/user/uploading-files/scripts/upload.py fetch ``` This downloads everything on the branch (vs default) into `./.uploads/` (filenames are flattened to basenames) and ensures `.uploads/` is in `.gitignore`. Treat the files in `.uploads/` like any other local input. If the script reports "No files on branch yet", the user probably forgot to click commit. Ask them to refresh the upload page and verify they committed, then re-run `fetch`. ### Step 3 — Cleanup When the uploaded files are no longer needed — typically after the work is done and anything worth keeping has been moved into the repo proper, **and before opening a PR** — delete the remote branch: ```bash python3 /mnt/skills/user/uploading-files/scripts/upload.py cleanup ``` Local files in `./.uploads/` are kept (they're gitignored). If the user might want them again, leave them; otherwise `rm -rf .uploads` after cleanup. ### Optional — status ```bash python3 /mnt/skills/user/uploading-files/scripts/upload.py status ``` Prints the repo, branch name, whether the branch exists on origin, and the upload URL. Useful when you've context-switched and want to recover the URL without recreating the branch. ## How it works - **Branch name** — `upload-<short>` where `<short>` is the first hyphen-segment of `$CLAUDE_SESSION_ID`, or of the most recent transcript filename under `~/.claude/projects/<encoded-cwd>/`, or a UTC timestamp `tsYYYYMMDD-HHMMSS` as fallback. The same session always resolves to the same branch, so re-running `init` is idempotent. - **Repo** — parsed from `git remote get-url origin`. Must be a github.com remote. - **Auth** — uses `$GH_TOKEN` (then `$GITHUB_TOKEN`, `$GITHUB_PAT`, `$GH_PAT`). Token needs `Contents: write` on the working repo. - **Network calls** — only `api.github.com` and `raw.githubusercontent.com`. ## Constraints - GitHub web upload caps at **25 MB per file**. Larger files won't work via this flow. - Filenames are flattened to basenames in `.uploads/`. If the user uploads two files with the same name in different subdirs, the second overwrites the first. Tell them to rename first if it matters. - Binary files survive the round-trip fine (raw download, byte-exact). - The skill does not read the upload branch's history beyond "what's there now vs default". If the user pushes multiple commits, you get the union of files. ## Anti-patterns - Don't ask the user to paste binary content (base64, hex dumps). Use this skill. - Don't create the branch and immediately try to fetch — the user has to upload first. - Don't leave the upload branch around after a PR is opened. It clutters the repo's branch list. - Don't commit anything in `.uploads/` to the working repo. If a file should be persisted, copy it to a proper location first (and `git add` from there).
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.