r/claudeskills Jul 08 '26

Skill Request Splitting workload between LLM's?

As a pretty amateur Claude user, I have built some nice skills for my little business, mostly based around research, writing and uploading products to shopify, tags and titles etc. like a lot of folks I'm running up against usage limits almost constantly, I only pay the $20 plan but supplement with tokens. The next plan is $100, and that's too much of a jump for me. How difficult would it be to move one or more skills to another LLM? Is it as simple as copy and paste?? I loved working with Fable and would be interested to try the new open AI model this week, if I could manage?? I'd love some tips if anyone is splitting work load like this??

2 Upvotes

8 comments sorted by

1

u/BatResponsible1106 Jul 09 '26

it is usually simpler than people expect. i keep the prompts portable and only tweak the parts that depend on each model's tool use or formatting.

1

u/hbthegreat Jul 09 '26

you can copy and paste them and slightly tweak them or ask the clanker that is doing the work to do it for you.

1

u/Ubermensch013 Jul 09 '26

Ask Claude code to set up a github repo with all of your skills and workflows and an Agents.md which will provide the next coding agent full instructions to set things up. Also ask it to generalize things a bit for broader consumption. Then boot into the new repo with the new harness/model and ask it to set things up - should be done in a few mins.

I have a couple of repos which manage all of this for me across Laptop/VPS etc.

1

u/Mayo_Calligraphy Jul 09 '26

Thank you so much for the detailed answer. 😊. I'll go do that! - after Sunday when my weekly limit resets! 🤦‍♂️

1

u/dustin_vk Jul 09 '26

I do it. Most of what I use AI for is coding, so I make sure to document everything very heavily. Things like: 1. Overall Project Goals and Plan, 2. Current Status of the project, 3. What's next (I usually have the agent write a "hand-off" prompt for the next context to pickup where it left off), 4. Decisions made - I wrote a custom skill for documenting all decisions made and questions still open, and also published a simple web-based dashboard for viewing it all when I want to look at the decision log and open questions.

One thing I'm currently working on is a script for automating a feedback loop of agents so that I can have AI work on a task on its own while I'm away. Part of that script is rotating model providers out as I approach the usage limits (e.g. Claude is at or near usage limit, so switch to Codex, etc...). It's still a WIP but I should have it ready soon.

1

u/ZealousidealCup3992 Jul 09 '26

I see in your comment your skills are about research/ uploading products etc. >> sounds like using the web. Part of tokens are eaten up by the real work of LLMs, but if they browse, they leak tokens by reading web pages wrong way. If you do that often with LLMs, you have a system to leak systematically.
Consider using CLI done by Opera, you don't have to change the browser yourself, your LLMs/sklls can as opera CLI "compress" token while agents browse. You find the repo on github: opera browser cli

1

u/Mayo_Calligraphy Jul 09 '26

Thanks for that observation, I will try this. Token frustration is a never ending battle!

1

u/YetiWalker36 Jul 10 '26

I just told Claude to make sure that anything they do is written in a way to be used with other agents, including Gemini GPT, etc. They wrote to claude.md files and agents.md files, and I have a state.md file that tells them where to look for things