Cursor Capabilities Bridge

Map Cursor rules, MCP, and hooks into VibeOS.

Skill metadata

Source	Bundled (installed by default)
Path	skills/software-development/cursor-capabilities-bridge
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos, windows
Tags	cursor, plugins, mcp, hooks, skills, adoption
Related skills	requesting-code-review, cursor-review-bridge, cursor-sdk-bridge, cursor-notebook-bridge, vibeos-local-verify-deploy, vibeos-agent-skill-authoring, plan, mcp-safe-hygiene, pr-babysit, split-to-prs, cursor-subagent-cookbook, session-loop, design-to-code-loop, desktop-local-preview, analytical-ui, niche-mcp-kit, niche-integrations-onboarding

Reference: full SKILL.md

信息

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Cursor Capabilities Bridge

Use this skill when the user asks to bring Cursor-style tools, rules, hooks, or plugins into VibeOS. Do not install Cursor IDE plugins into VibeOS. Map each Cursor idea onto an existing VibeOS extension socket.

When to Use

• User says “как в Cursor”, “добавь MCP/hooks/plugins”, “перенеси rules”
• Choosing between skill vs MCP vs plugin vs core tool
• Cleaning up TermitPro-style stub plugins that do nothing in VibeOS

Prerequisites

• Read docs/cursor-vibeos-guidebook.md for the Day-20 one-pager
• Read docs/cursor-capabilities-adoption.md for the live inventory
• Prefer ~/.vibeos paths via get_vibeos_home() / display_vibeos_home()
• Secrets only in ~/.vibeos/.env, never in git

How to Run

1. Identify the Cursor surface (rules / skill / hook / MCP / subagent / IDE).
2. Pick the highest rung that fits (skill → CLI+skill → MCP → plugin hook → plugin tool → core last).
3. Implement at the edge; verify with a concrete prompt, not only config edits.
4. Prefer a new session after MCP/toolset changes (cache + schema stability).

Quick Reference

Cursor	VibeOS	Command / path
Rules	project AGENTS.md + user skills	~/.vibeos/skills/
Skills	bundled / optional / user skills	skill_view / skills hub
Hooks	plugin / gateway / shell hooks	ctx.register_hook, ~/.vibeos/hooks/
MCP	mcp_servers in config	vibeos mcp / /reload-mcp
Plugins	real register(ctx) plugins	vibeos plugins enable <name>
Subagents	delegate_task / kanban / profiles	skill cursor-subagent-cookbook
/loop	cron + Monitor	skill session-loop
babysit / split PRs	recipes	skills pr-babysit, split-to-prs
/review / Bugbot / security	independent verify	skill cursor-review-bridge
Agent SDK / programmatic	API + ACP	skill cursor-sdk-bridge
EditNotebook	jupyter / file	skill cursor-notebook-bridge
Niche SaaS MCP	catalog + cookbook	skill niche-mcp-kit
Coding SaaS staging	disabled profile MCP copy	vibeos adoption sync-coding-mcp
Cursor bridge skill sync	safe local skill refresh	vibeos adoption sync-skills --force
Hook event names	plugin/shell hooks	docs/ops/cursor-hooks-parity.md
IDE	ACP	vibeos-acp / acp_adapter/

Procedure

1. Rules → durable instructions

• Put project-wide engineering rules in AGENTS.md (already present).
• Put personal always-on habits in ~/.vibeos/skills/cursor-* (already imported).
• Do not inject large rule blobs mid-conversation into the system prompt.

2. Skills → recipes

• Author with vibeos-agent-skill-authoring standards (description ≤ 60 chars).
• For review use cursor-review-bridge → requesting-code-review; for tests+Timeweb use vibeos-local-verify-deploy.

3. MCP → external hands

• Add under mcp_servers.<name> in ~/.vibeos/config.yaml.
• Always set tools.include: [...].
• Scope filesystem servers to one project dir, never $HOME.
• Do not enable TermitPro stub dirs like ~/.vibeos/plugins/mcp-filesystem expecting VibeOS MCP — they are not VibeOS plugins.
• Skip GitHub MCP while the no-github policy is active.
• Ops runbook + smoke: skill mcp-safe-hygiene.
• This machine: project_fs (read FS) + project_git (read-only git via uvx).
• SaaS: skill saas-mcp-onboarding — Linear catalog entry is pre-staged disabled with read-first whitelist; OAuth when you enable it.
• Use vibeos adoption sync-coding-mcp to copy the default profile's Linear, Figma, and Notion MCP definitions into the coding profile as disabled entries.
• Use vibeos adoption sync-skills --force to refresh the Cursor bridge skill pack only when you intend to replace locally edited copies.

4. Hooks → guardrails

• Policy / blocks: user plugin hooks (pre_tool_call returning {"action":"block","message":"..."}).
• Messaging-only side effects: gateway hooks under ~/.vibeos/hooks/.
• Tiny shell scripts: hooks: in config; copy from examples/agent-hooks/.
• Event name map (Cursor → VibeOS): docs/ops/cursor-hooks-parity.md.
• Local audit (no outbound telemetry): vibeos-policy + skill vibeos-local-audit.
• Keep security-guidance enabled for write-pattern warnings.

5. Subagents → bounded workers

• Short parallel work: delegate_task with leaf roles and toolset limits.
• Work that must survive restart: kanban or cron, not process-local background.

Pitfalls

• Enabling stub plugins from plugins.disabled that only have plugin.yaml wastes time — check for __init__.py + register(ctx) first.
• Unfiltered MCP tool floods raise cost every turn.
• Mid-session /reload-mcp changes tool schemas; start a new chat when possible.
• Never add a core tool because “Cursor has a Task tool” — use delegation/skills.

Verification

• Ask: “Which MCP tools are available?” and confirm only whitelisted names (mcp_project_fs_* etc.).
• Trigger a blocked git push / gh pr create via terminal and confirm vibeos-policy blocks it.
• Load this skill and another recipe skill; complete one small end-to-end task without editing tools/ or toolsets.py.