Niche Integrations Onboarding

Install niche Cursor plugins as user skills or MCP.

Skill metadata

Source	Bundled (installed by default)
Path	skills/devops/niche-integrations-onboarding
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos, windows
Tags	cursor, mcp, foundry, scylla, paradedb, figma, linear, niche
Related skills	niche-mcp-kit, saas-mcp-onboarding, mcp-safe-hygiene, cursor-capabilities-bridge, figma-edit, notion

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.

Niche Integrations Onboarding

Bring Cursor marketplace / Agent Skills (Foundry, ScyllaDB, ParadeDB, Figma, Linear, …) into VibeOS without adding in-tree third-party product plugins. Install into ~/.vibeos only.

When to Use

• User has Cursor plugins (Scylla, Foundry, ParadeDB) and wants them in VibeOS
• Enabling Figma / Linear after the general SaaS skill
• Operator asks “перенеси плагин Cursor X”

Prerequisites

• Read docs/cursor-capabilities-gap-plan.md policy: no in-tree SaaS plugins
• Secrets only in ~/.vibeos/.env
• MCP: always set tools.include (mcp-safe-hygiene)
• Skills: copy into ~/.vibeos/skills/<name>/ (not plugins/ of this repo)

How to Run

Catalog MCP (preferred)

Full cookbook: skill niche-mcp-kit + examples/mcp/README.md.

Integration	Action
Linear	vibeos mcp install linear — OAuth; may need VPN outside RU
Figma	vibeos mcp install figma → login → configure → figma-edit / design-to-code
Notion	vibeos mcp install notion (OAuth); fallback skill notion + API key
n8n	vibeos mcp install n8n + .env keys

vibeos mcp catalog
vibeos mcp install figma
vibeos mcp login figma
vibeos mcp test figma
# new session

Cursor Agent Skills → user skills

Copy only the skill folders you need (example paths on a Mac with Cursor):

# ScyllaDB skills from Cursor plugin cache (adjust hash/path)
SRC=~/.cursor/plugins/cache/cursor-public/scylladb
DEST=~/.vibeos/skills/scylladb
mkdir -p "$DEST"
# copy each skills/<name>/ tree that has SKILL.md
find "$SRC" -type d -name 'scylladb-*' 2>/dev/null | head
# then: cp -R …/skills/scylladb-cloud-setup "$DEST/"

Microsoft Foundry:

SRC=~/.agents/skills/microsoft-foundry
DEST=~/.vibeos/skills/microsoft-foundry
mkdir -p "$DEST"
# copy the specific sub-skills the user named (deploy-model, foundry-agent, …)
# Do NOT commit these into the VibeOS git tree.

ParadeDB: use the MCP server from Cursor’s catalog when available, or keep using the Cursor session for docs search — do not vendor the plugin into plugins/ of this repo.

Verify

vibeos skills list | head
vibeos mcp list
vibeos doctor   # MCP hygiene + stubs

Quick Reference

Source	VibeOS socket	In-tree?
Linear / Figma / n8n catalog	mcp_servers:	Catalog OK
Scylla / Foundry skills	~/.vibeos/skills/	No
ParadeDB MCP	user mcp_servers	No product plugin
TermitPro stub dirs	quarantine	Never enable

Procedure

1. Identify: MCP vs skill-only vs Azure CLI scripts.
2. MCP → catalog install + whitelist + new session.
3. Skill-only → copy to ~/.vibeos/skills/; fix description ≤ 60 chars if needed.
4. Smoke with one real prompt (“list Linear issues”, “explain Scylla partition key”).
5. Leave GitHub MCP off under no-github policy.

Pitfalls

• Copying into VibeOS/plugins/ will be rejected by project policy / doctor stubs.
• Foundry skills often need Azure CLI + login — document that in the user skill.
• Linear geo-block in RU: complete OAuth on an allowed network first.
• Do not enable filesystem MCP rooted at $HOME.

Verification

• vibeos doctor shows no new stub plugins under plugins/.
• Niche skill appears in skills list for the active profile.
• MCP tools are only the whitelisted names.