Skills are reusable instructions Roomote can use when a task needs a specialized workflow. Use Skills when the same guidance keeps showing up across tasks in an environment: a framework-specific review checklist, a release process, a design-system rule, a data workflow, or a repeatable debugging path.Documentation Index
Fetch the complete documentation index at: https://docs.roomote.dev/llms.txt
Use this file to discover all available pages before exploring further.
What Skills Settings controls
The Skills settings page is for admin-managed skills attached to environments. A skill only applies to tasks that run in an environment where it is enabled. You can add skills in two ways:| Skill type | How it is added | Best for |
|---|---|---|
| Marketplace skill | Search and install from the Vercel Marketplace | Reusing a maintained public skill for a common tool or workflow |
| Custom skill | Paste your own skill content and choose environments | Capturing team-specific behavior that does not belong in one repository |
When to use a custom skill
Create a custom skill when the instruction is:- repeatable across many tasks
- specific enough that Roomote can tell when to use it
- more detailed than a short line of environment guidance
- durable enough to maintain over time
- a support-investigation workflow for your product
- a design-system implementation checklist
- a release-note drafting process
- a database migration review guide
- a customer-escalation triage playbook
Write the description carefully
The description helps Roomote decide when the skill is relevant. Make it concrete. Prefer:How Skills interact with repo-defined skills
Some repositories define their own skills in the repo, usually as checked-inSKILL.md files. Those repo-defined skills travel with the repository and are best for instructions that should stay versioned with that codebase.
Skills configured in Roomote settings are different:
- Settings skills are environment-level. They apply to selected Roomote environments, even when the guidance is not checked into a repository.
- Repo-defined skills are codebase-level. They apply when the task is working in that repository and the active workflow finds them relevant.
- Both are supplemental. They help Roomote perform specialized work after a Roomote task is underway; they do not replace the built-in task flow, environment setup, or the user’s prompt.
- Built-in Roomote skills stay authoritative. If a custom or repo-defined skill uses the same name as a built-in Roomote workflow, Roomote’s built-in workflow wins. Use distinct names for team skills.
Choosing the right home
| Put it in | Use it for |
|---|---|
| Skills Settings | Reusable playbooks for selected environments |
| Repo-defined skills | Codebase-specific playbooks that should live with the repo |
| Environment guidance | Setup commands, services, ports, secrets, and workspace-specific rules |
| Agent Guidance | Organization-wide expectations that apply to most tasks |
| Task prompt | One-off context for the current ask |
Common issues
- Roomote does not use the skill. Make the description more specific and confirm the task is running in an environment where the skill is enabled.
- The skill applies too broadly. Narrow the description or limit it to fewer environments.
- Two skills seem to overlap. Keep the more specific one, or split the workflow so each skill has a clear trigger.
- A repo already has a similar skill. Prefer the repo-defined skill for codebase-owned behavior, and use Settings skills for cross-environment behavior.