> ## 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 > Teach Replo to do specific things well by installing skills others have built or creating your own. export const TryPromptButton = ({prompt, imageSrc, imageAlt = "Template preview", imageStyles = {}, buttonCta = "Build in Replo"}) => { const [isLoading, setIsLoading] = useState(false); const [error, setError] = useState(null); const API_BASE = "https://api.replo.app"; const APP_URL = "https://dashboard.replo.app"; const LoaderIcon = ; const ChevronIcon = ; async function postJSON(url, body, headers = {}, timeoutMs = 120000) { const controller = new AbortController(); const timeoutId = setTimeout(() => controller.abort(), timeoutMs); try { const response = await fetch(url, { method: "POST", headers: { "Content-Type": "application/json", ...headers }, body: JSON.stringify(body ?? ({})), signal: controller.signal }); const responseText = await response.text(); if (!response.ok) throw new Error(`API Error: ${response.status}`); return responseText ? JSON.parse(responseText) : {}; } finally { clearTimeout(timeoutId); } } async function handleTryPrompt(event) { event.preventDefault(); event.stopPropagation(); setIsLoading(true); setError(null); try { const body = { prompt, file: null }; const {seed} = await postJSON(`${API_BASE}/api/v1/marketing/issue-marketing-site-jwt`, body); if (!seed) throw new Error("No seed returned from API"); const url = new URL(APP_URL); url.searchParams.set("type", "agent"); url.hash = `seed=${encodeURIComponent(seed)}`; window.open(url.toString(), "_blank"); setIsLoading(false); } catch (caughtError) { console.error("Failed to generate prompt:", caughtError); const message = caughtError instanceof Error ? caughtError.message : null; setError(message ?? "Something went wrong. Please try again."); setIsLoading(false); } } return
{} {imageSrc && {imageAlt}} {}
{} {} {error &&
{error}
}
; }; 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
{} {}
{finalAltText}
; }; A skill packages know-how for a particular task, so when that task comes up, Replo already knows the right way to handle it. Think of a skill as a reusable playbook: instructions plus any reference files Replo should follow. Install skills the Replo team and community have built, or create your own to capture a workflow that is specific to your business. ## When to use a skill Reach for a skill when you catch yourself re-teaching Replo the same approach. Writing or installing a skill once means Replo applies that approach every time, without you spelling it out again. Pair skills with [Tasks](/apps/tasks) to run them on a schedule, like a weekly competitor teardown that lands in your inbox every Monday. You can reach Skills from the **+** in the tab bar or the Cmd+K menu. ## Find your way around The home view has three sections: * **Featured** highlights a rotating set of skills worth a look. * **My skills** is everything you have installed or created, the skills available to Replo in this project right now. * **Discover** is the full library shared by the community and team. Search across it, sort it, and filter by category. Discover groups skills into six categories so you can browse by the kind of work you are doing: | Category | Covers | | ------------------------------ | ---------------------------------------------------------- | | **Brand & Design** | Visual identity, brand voice, photography, video, layout | | **Marketing & Acquisition** | Paid ads, SEO, content, social, influencer, referral | | **Conversion & Merchandising** | PDP, quizzes, bundles, offers, social proof, checkout | | **Customers & Retention** | Email and SMS, loyalty, subscriptions, reviews, support | | **Operations & Analytics** | Inventory, shipping, integrations, attribution, dashboards | | **Strategy & Finance** | Positioning, market research, pricing, unit economics | ## Install a skill Open any skill to see what it does, the instructions it runs, and the files it bundles. If it is not installed yet, click **Install** to add it to your project so Replo can use it. Once installed, the skill moves into **My skills** and its action flips to **Uninstall**. Uninstalling a Replo-built skill just removes it from your project, you can always re-install it from Discover later. ## Use a skill Once a skill is installed, you call it from the chat. Type `/` followed by the skill's slash command, or `@` and pick it from the menu the same way you would [mention a page, asset, or integration](/sessions-and-history#mentions). Either way works. Hit `/` and the list of installed skills appears, filtering as you type, with a short description on each so you pick the right one. Either way, Replo picks up the skill's instructions and runs the task the way the skill defines it. The chat shows which skill it is using as it works. You do not always have to call a skill by name. When a request matches an installed skill, Replo reaches for it on its own. Here, asking "what are people saying about Graza" loaded the `voice-of-customer` skill automatically, no slash command or mention needed. ## Create your own skill When you find yourself explaining the same process to Replo over and over, turn it into a skill. From **My skills**, open the **New skill** menu and pick how you want to build it. The fastest path. Replo asks what workflow you want to capture, you describe it in plain language, and it writes the name, slash command, description, category, and instructions for you. The more specific you are about what the skill does, who uses it, and when it should run, the better the result. ```text theme={null} A weekly competitor teardown: pull my top 3 competitors' landing pages, compare their offers, headlines, and pricing to mine, and list what I should test next. ``` When it finishes, the new skill is ready to use, with its own slash command, just like any other. Prefer to write it yourself? **Create from scratch** opens the editor directly. Set the name, slash command, and description, write the instructions in `SKILL.md`, and optionally upload supporting files. ### What goes in a skill Every skill is the same shape, whether Replo wrote it or you did: * **Name and slash command** are how you and Replo refer to it. * **Description** tells Replo (and you) when to reach for it. * **`SKILL.md`** is the main instruction file, written in Markdown, that Replo follows when the skill runs. * **Files** are optional extras the skill bundles, such as a brand-voice guide, a checklist, or a CSV Replo should reference. Upload individual files or a whole folder. ## Edit, share, and delete Skills you create are yours to manage. From a skill you own, you can: * **Edit** the name, description, instructions, or files at any time. * **Share** it as a reusable link so a teammate can open the same skill in Replo. * **Delete** it when you no longer need it. A skill you create lives only in your workspace. Deleting it removes it permanently, there is no copy in the registry to re-install from. (Replo-built skills are different: uninstalling one just removes it from your project, and you can re-install it later.) ## Related Get the best results from Replo. Run skills and prompts on a schedule.