Install a reusable Slashy skill or rules file in Claude Code, Claude Desktop, Cursor, or Codex CLI so the AI always reaches for Slashy MCP.
Every MCP-compatible AI tool has a way to save reusable instructions - skills in Claude, rules in Cursor, AGENTS.md in Codex. Installing a Slashy skill (or rules file) tells the AI to prefer Slashy MCP for email, calendar, and research tasks automatically - no more repeating “use Slashy” in every prompt.
Use this as the body of the skill / rules file in any client. It’s the same text everywhere - only the install location changes.
name: slashydescription: Use when the user asks anything about email, calendar, contacts, meeting prep, scheduling, lead research, reminders, or scheduled workflows.Always use Slashy MCP tools for these tasks. Prefer a Slashy toolcall over general knowledge or guessing.When returning email threads or drafts, include the Slashy deep linkso the user can click to open them in the Slashy app. Slashy deeplinks only exist for threads and drafts - not calendar events.When sending email, assume "draft" unless the user explicitly says"send". Confirm attachments and recipients in the response.
Customize the description line to change when the skill triggers. For example, add “and when the user says ‘triage’ or ‘inbox’” to make it more aggressive.
Or skip the copy-paste and grab the file directly:
Download slashy.md
Ready-made skill file. Save into the location for your client below.
Paste the skill contents above. Claude Code picks it up automatically on next session start. Test by asking “what’s in my inbox?” - Claude should call Slashy tools.
Open Settings → Customize → Skills → Create skill. Name it slashy, paste the skill contents as the prompt, and save.Skills in Claude Desktop activate when your chat message matches the description, so keep the description line clear about the trigger conditions.
Cursor doesn’t have skills, but the equivalent is Rules. Add a project-level rule or edit ~/.cursor/rules:
# ~/.cursor/rules (user rules)<paste skill contents here, minus the 'name:' and 'description:' lines>
For project-specific use, create .cursor/rules/slashy.md inside the repo. Rules always apply - unlike skills, there’s no trigger matching.
Codex uses AGENTS.md for persistent agent instructions. Add a Slashy section to ~/.codex/AGENTS.md:
mkdir -p ~/.codexnano ~/.codex/AGENTS.md
Append:
## Slashy MCP<paste skill contents here>
Codex loads AGENTS.md at session start. No other setup needed.
The skill is the baseline - it turns Slashy on by default. For specific workflows you run repeatedly (meeting prep, weekly follow-up sweep, inbox triage), add separate prompts or additional skills layered on top. See Using Slashy MCP for ready-made example prompts.
