Agent skills

Documentation Index

Fetch the complete documentation index at: https://docs.replit.com/llms.txt

Use this file to discover all available pages before exploring further.

Skills teach Agent new capabilities. They let you share your expertise, preferred patterns, and specialized knowledge with Agent so it produces better, more consistent results.

​

Why skills matter

Every time you build with Agent, you create useful context: solutions to problems, design decisions, framework preferences. But that context disappears when the chat ends. Skills preserve it. A GSAP animation skill teaches Agent how to use a specific library correctly. A design system skill ensures it applies your exact colors and spacing rules. A bug fix skill captures a solution so Agent doesn’t repeat the same mistake. Tasks that were previously inconsistent become reliable. Skills are also an open standard. They work with any agent, including Replit Agent, so you can carry them between tools.

​

Proactive vs. reactive skills

A framework for thinking about when and how to create skills. Understanding both patterns makes you more effective.

​

Proactive skills

Proactive skills are ones you add before you start building. Research the libraries or patterns you want to use, find or create skills for them, then start prompting. Example: Before building a portfolio site with handwritten SVG animations, research animation libraries and find GSAP. Install a GSAP React skill, then prompt Agent to build the animations. Agent has the specialized knowledge it needs from the start — it understands the library’s API, best practices, and common patterns. Without the skill, it might produce something generic or incorrect. This pattern works well when:

• You’re using a library that’s popular but has nuanced patterns Agent may not nail on its own
• You want consistent design choices across the project (typography, spacing, animation style)
• You’re starting a project and already know the technical direction

​

Reactive skills

Reactive skills are ones you create after solving a problem. You encounter an issue, debug it with Agent, fix it, and then capture the solution so it doesn’t happen again. Example: While building a canvas for a mobile app, you notice jagged edges on images that get worse when zooming in. Debugging with Agent reveals this is minification aliasing — a rendering issue where images look worse as they shrink, counterintuitively. After implementing a fix, ask Agent to create a skill: Agent uses the conversation history to write a project-specific skill. Next time the issue comes up, you can point Agent to the skill instead of debugging from scratch. This pattern works well when:

• You’ve fixed a non-obvious bug and want to prevent it from recurring
• You’ve learned something about your app’s architecture during a debugging session
• You want to encode a solution that took significant effort to discover

​

Being selective with skills

Think of skills like directions you’d give a friend to find your apartment. A targeted list of instructions works. A binder full of documentation doesn’t — nobody has time to read that, and the important details get lost. The same applies to Agent. If you add too many skills, Agent can get confused. Be deliberate about which skills you enable for a given project, and remove ones you no longer need.

​

Security considerations

Skills from the Replit Skills pane are audited for safety. But skills can be installed from anywhere — they come from an open source repository where anyone can contribute. Since skills are instructions that Agent follows, a malicious skill could tell Agent to exfiltrate sensitive data from your project. Before installing any skill from an external source:

1. Open the file. Skills are just markdown. Read the contents in /.agents/skills/ before using them.
2. Check the source. Verify the skill comes from a trusted repository or author.
3. Review what it instructs. Make sure the skill doesn’t reference suspicious external URLs or request sensitive information.

​

Skills vs. MCP servers

Skills and MCP servers are the two main ways to extend agents, and they serve different purposes. Skills are context-efficient. Only a brief description loads until the skill is invoked. Use skills for:

• Workflows and conventions (“how to deploy,” “code review checklist”)
• Reference materials (API patterns, style guides, design systems)
• Reusable prompts and specialized knowledge (animation libraries, framework patterns)

MCP servers are context-heavy. All tool descriptions load upfront, which can degrade output quality if you add too many. Use MCP servers for:

• Connecting to external services (Notion, Linear, Figma)
• Actions that need API access
• Tools that do things, not just instruct

The key distinction: skills define how your agent should work. MCP servers define what your agent can access. Both work for coding agents like Replit Agent and for agents you build yourself.

​

Next steps