> ## Documentation Index
> Fetch the complete documentation index at: https://beta-docs.replo.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Skills & Plans
> Two ways to get more out of every conversation with Replo: teach it your workflows with skills, and steer its approach with plans.
export const Screenshot = ({src, altText, width, shadow = true}) => {
const generateAltText = imageSrc => {
if (!imageSrc) return "Screenshot";
const filename = imageSrc.split("/").pop() ?? "";
const nameWithoutExt = filename.replace(/\.[^/.]+$/, "");
const readable = nameWithoutExt.replace(/[-_]/g, " ").replace(/\b\w/g, char => char.toUpperCase());
return readable === "" ? "Screenshot" : readable;
};
const finalAltText = altText ?? generateAltText(src);
const imageWidth = width ? `${width}px` : "100%";
return ;
};
Most of what you do with Replo is just talking to it. Two features make those conversations far more powerful: **skills**, which teach Replo how you like work done, and **plans**, which let you see what it intends to do before it does it. You may not have run into either yet, so this page starts from scratch. Together, they make Replo more predictable: you reuse what works, and you get a say before it builds.
Teach Replo a workflow once, then reuse it in any conversation.
See the steps Replo intends to take, and edit them before it commits.
## Skills: teach it once, use it everywhere
A skill is a saved set of instructions for something you do often, so you only have to explain it once. Instead of re-typing how you like your product descriptions written or your ad campaigns set up every single time, you save it as a skill and Replo follows it from then on. You can write your own, or install ones the Replo team already built.
The best part: you usually do not have to remember they exist. When something you ask lines up with a skill, Replo picks it up on its own. (You can also call one by name with `/` or `@` if you want to be explicit.) Below, the plain question "what are people saying about Replo" quietly loaded the `voice-of-customer` skill, with no command typed.
So every conversation starts with Replo already knowing how you like things done. See [Skills](/apps/skills) to install, create, and share them.
## Plans: see the approach before it builds
Before tackling anything bigger than a quick edit, Replo writes a plan: a short, numbered list of what it is about to do. Think of it as an outline you get to approve before any work starts, so nothing happens behind your back.
The plan shows up in the chat and in the Plans app. If something looks off, you can fix it before Replo starts:
* **Reword** a step to say what you actually want
* **Add** a step it missed
* **Remove** anything you do not need
When it looks right, hit **Build** and Replo gets to work. Fixing a plan takes seconds; fixing the wrong thing after it is built takes a lot longer. See [Plans](/plans) to browse, edit, and build them.
## Better together
Skills and plans complement each other: a skill defines *how* a task should be done, and a plan lays out *what* Replo will do this time. Pair them with [Tasks](/apps/tasks) to run the combination on a schedule, like a weekly competitor teardown that follows your skill and lands every Monday.
## Related
Write prompts that produce good skills and plans.
Run skills and plans on a schedule.