# I would like to upload the claude deep writing skills to claude on the web. given that these deep... ## Retrieval Notes - Session id: `019ded28-cd22-7a31-8cdd-77252b8cb77f` - Source: `Codex raw session` - Last activity: `2026-05-03T09:29:30.125Z` - Model: `gpt-5.5` - CWD: `/Users/nickyoung` ## My Notes <!-- Add your notes here. This section is preserved across syncs. --> ## Conversation ### User I would like to upload the claude deep writing skills to claude on the web. given that these deep-writing-mode is a skill that skills other skills i am not sure where to begin. ### Assistant I’ll treat this as a skills/config question and first check the operational map plus the local skill instructions, then I’ll give you a practical path for bundling the deep-writing setup for Claude web without flattening its structure too badly. ### Assistant I’ve loaded the cross-runtime and file-management instructions. Since this touches Claude web and local skills, I’m also checking the local skill graph and the operational notes so the advice is grounded in your actual setup rather than generic “make a zip” advice. ### Assistant The local graph is now clear: `deep-writing-mode` is a composite wrapper, and its mandatory dependencies are real skills in `~/.claude/skills`. I’m going to check the skill-packaging instructions next, then I can either outline the upload order or make a ready-to-upload folder of ZIPs for you. ### Assistant The important finding: uploading only `deep-writing-mode` would give Claude web a conductor with no orchestra. The right shape is either “one ZIP per component skill, then the composite ZIP” or a new web-specific mega-skill that embeds the needed instructions; I’m going to prepare the safer first option as a ready-to-upload folder so you have something concrete. ### Assistant One more useful wrinkle: most of the local descriptions are longer than Claude.ai’s current 200-character upload limit, so the first ZIP set may be too faithful to upload cleanly. I’m making a second “web-ready” set with shortened descriptions and a slightly less Claude-Code-specific `deep-writing-mode`. ### Assistant I’d begin with the component skills, not `deep-writing-mode` itself. Claude.ai wants one ZIP per skill folder, and the ZIP must contain the skill directory at the root. Its docs also say Claude can combine multiple skills automatically, but a skill cannot reliably “call” another skill by name the way your Claude Code composite skill tries to do. Sources: [Claude custom skills](https://support.claude.com/en/articles/12512198-creating-custom-skills), [Claude skills docs](https://claude.com/docs/skills/how-to). I made a web-ready upload set here: [claude-web-skill-zips/deep-writing-web-ready/zips](/Users/nickyoung/claude-web-skill-zips/deep-writing-web-ready/zips) Use these first, in this order: 1. `nick-analytic-voice.zip` 2. `writing-standards.zip` 3. `epistemic-discipline.zip` 4. `source-work.zip` 5. `deep-writing-mode.zip` Then add the optional/post-hoc ones: `depth-audit.zip`, `anti-metacommentary.zip`, `nick-philosophical-prose.zip`, `voice-fix.zip`, `source-check.zip`, `write-from-plan.zip`, `twork.zip`, `contemplate.zip`, `draft-audit.zip`. I also shortened the descriptions to stay under Claude.ai’s 200-character limit and adjusted the web-ready `deep-writing-mode` so it says to keep the component skills enabled rather than trying to invoke a Claude Code-only Skill tool. I verified the ZIP structure on the staged set. The thing to watch: `source-work` on Claude web cannot see your local vault or `Learning/` folder unless you upload files into that chat, so it should function as an upload-and-extract discipline there, not as a local Obsidian/source filesystem workflow. *La soluzione più ordinata è trattare la scrittura profonda come un insieme di capacità coordinate, non come una sola istruzione onnipotente.*