Reusing work from another Overskill app

Attach one of your other Overskill apps to a chat so the AI can look at how you solved something there and build the same thing in the Overskill app you're working on.

If you already solved something in one Overskill app — a checkout, a booking flow, a look and feel you like — you don't have to describe it again from memory. Attach that Overskill app to the chat, and the AI can go and look at how you did it.

💬 Ask your AI to set this up Attach the other app first (see below), then paste this into the chat:

Reuse the checkout from the app I've attached as a reference — look at how it works there and build the same thing here, adapted to this app. If something it depends on isn't available on my account, tell me honestly instead of guessing.

One thing the AI can't do for you: passwords and keys never travel between your apps. If the original app connects to an outside service, you'll be asked to paste that key in again here. That's on purpose.

How to attach another Overskill app

  1. In the chat, find the small Reference another app button in the row of buttons under where you type.
  2. Pick the Overskill app you want it to look at from the Reference an app list.

The app you picked stays attached to that chat until you remove it, so you can keep referring back to it across several messages. To remove it, click the × on the app's name above the message box.

You can also do this before an app exists: attach one from the same button on the new-app box on your dashboard, and your new app starts out able to see it.

What the AI can see

Once an app is attached, the AI can:

  • read how that app is built and search it for whatever you're asking about
  • see the names of any outside services it connects to, and how it connects to them
  • copy an approach across and adapt it to the app you're actually working on

What it can't see, and can't do

  • It can't change the app you attached. It only reads. Your other app is untouched.
  • It never copies your passwords or keys. It will see that an app uses, say, a Printful key — but not the key itself. It'll ask you to paste that in.
  • It's one app at a time. Attaching a second one replaces the first.
  • Both Overskill apps have to be yours, in the same workspace.

Do I need to mention it in my message?

No. Attaching an app is enough — before the AI builds something, it checks whether the attached app already solves it.

You'll get a better result if you say what you're after, though. Reuse the checkout from my other app gets you further than add a checkout, because it tells the AI which part of a big app you actually care about.

Why bother

The AI is good at building something from a description. It's better at copying something that already works for you — your real setup, your real edge cases, the fixes you made the first time round. Attaching the app is how you hand it that.

A good moment to use it: you're building a second app that needs something the first one already does well, and you'd rather not rediscover every detail you got right the first time.

Was this helpful?

Thanks for the signal — it helps us improve the docs.

More in Building apps

Build with OverSkill, not against it

The single biggest way to get more out of your credits: lean on what OverSkill already gives you instead of asking it to rebuild things from scratch. Here's how to spot the difference.

How to ask the AI for changes

Better prompts get better results. The short guide to writing requests the AI nails on the first try.

What the AI can — and can't — do

Realistic expectations for what you can build with OverSkill, what the AI handles, and where you might hit limits.

Still need help?

If this didn't answer your question, our team is one click away.