Waleed e257d067f2 feat(integrations): suggest curated skills per integration with one-click add (#4912)
* feat(integrations): suggest curated skills per integration with one-click add

Curate research-backed, capability-grounded skills for every catalog
integration and surface them on the integration detail page. Each skill
maps to operations the block actually supports and can be added to the
workspace in one click; track adds in PostHog.

- Add SuggestedSkill type + skills field on BlockMeta; populate skills
  for all 193 catalog integrations (3 audit passes for grounding/sourcing)
- getSuggestedSkillsForBlock() with versioned-type (e.g. notion_v2) base fallback
- Skills section on the integration detail page with add/added states
- integration_skill_added PostHog event with workspace/integration metadata

* fix(integrations): flip suggested-skill row to Added immediately after add

The row derived Added state solely from the useSkills cache, so between a
successful create and the list refetch the row still showed Add and could
be clicked again, hitting the server duplicate-name check. Track added
names in local state so the row reflects the add immediately.

* fix(integrations): harden suggested-skill add flow; document skill authoring

Address PR review feedback on the suggested-skills section:
- Make useSkills the single source of truth for Added state by writing the
  created skill into the React Query cache onSuccess (fixes stale Added that
  survived a delete, and the lag that allowed a duplicate click)
- Track in-flight adds in a Set so concurrent adds keep independent pending
  state and cannot be double-submitted
- Surface failures with toast.error instead of swallowing the rejection
- Extract the duplicated SkillTile into a shared workspace component

Also document the new BlockMeta.skills field in the add-block and
validate-integration skills (+ blocks AGENTS.md): skills must be grounded in
the block's tools.access and sourced from real online use cases, never invented.

* fix(integrations): synchronous in-flight guard for skill add; align cursor docs

- Guard handleAdd with a ref so two rapid clicks cannot both fire a create
  before the disabled state re-renders (pendingNames is async)
- Fold the create-cache-merge rationale into the hook's TSDoc and drop
  non-TSDoc inline comments to match the repo convention
- Align .cursor add-block/validate-integration command docs with the newer
  .claude/.agents versions: BlockMeta section + skills authoring/validation
  guidance (grounded in tools.access, sourced from real online use cases)

* fix(integrations): gate skill Add/Added on authoritative workspace skills

useSkills uses keepPreviousData, so during initial load or a workspace switch
the list could be empty or a prior workspace's placeholder — making rows show
a misleading Add (duplicate-submittable) or a false Added. Derive skillsReady
from !isPending && !isPlaceholderData, only mark Added when ready, and disable
Add until the current workspace's list has loaded.

* chore(integrations): drop local-variable comments in skills section

Keep to the repo's TSDoc-on-declarations convention — the in-flight guard and
skillsReady derivation are self-evident from naming.
2026-06-08 16:52:07 -07:00

Sim Logo

The open-source AI workspace where teams build, deploy, and manage AI agents. Build conversationally, visually, or with code. Connect 1,000+ integrations and every major LLM to automate real work.

Sim.ai Discord Twitter Documentation

Ask DeepWiki Set Up with Cursor

Build everything in Mothership

Your AI command center. Describe what you want in plain language. Mothership knows your entire workspace and takes action: building agents, running them, querying data, and more.

Mothership building and running an agent from chat

Create files and documents

Generate documents, reports, and presentations from a single prompt, grounded in your workspace data.

Mothership generating a document from a prompt

Ground agents in your knowledge

Upload documents to a knowledge base and let agents answer questions from your own content.

Creating a knowledge base

Structured data with Tables

A database, built in. Store, query, and wire structured data into agent runs.

Tables view with typed columns

Build visually with Workflows

Prefer a canvas? Design agents block by block in the visual builder, and let Copilot generate blocks, wire variables, and fix errors from natural language.

Workflow builder demo

Quickstart

Cloud-hosted: sim.ai

Sim.ai

Self-hosted: NPM Package

npx simstudio

→ http://localhost:3000

Note

Docker must be installed and running on your machine.

Options

Flag Description
-p, --port <port> Port to run Sim on (default 3000)
--no-pull Skip pulling latest Docker images

Self-hosted: Docker Compose

git clone https://github.com/simstudioai/sim.git && cd sim
docker compose -f docker-compose.prod.yml up -d

Open http://localhost:3000

Sim also supports local models via Ollama and vLLM. See the Docker self-hosting docs for setup details.

Self-hosted: Manual Setup

Requirements: Bun, Node.js v20+, PostgreSQL 12+ with pgvector

  1. Clone and install:
git clone https://github.com/simstudioai/sim.git
cd sim
bun install
bun run prepare  # Set up pre-commit hooks
  1. Set up PostgreSQL with pgvector:
docker run --name simstudio-db -e POSTGRES_PASSWORD=your_password -e POSTGRES_DB=simstudio -p 5432:5432 -d pgvector/pgvector:pg17

Or install manually via the pgvector guide.

  1. Configure environment:
cp apps/sim/.env.example apps/sim/.env
# Create your secrets
perl -i -pe "s/your_encryption_key/$(openssl rand -hex 32)/" apps/sim/.env
perl -i -pe "s/your_internal_api_secret/$(openssl rand -hex 32)/" apps/sim/.env
perl -i -pe "s/your_api_encryption_key/$(openssl rand -hex 32)/" apps/sim/.env
# DB configs for migration
cp packages/db/.env.example packages/db/.env
# Edit both .env files to set DATABASE_URL="postgresql://postgres:your_password@localhost:5432/simstudio"
  1. Run migrations:
cd packages/db && bun run db:migrate
  1. Start development servers:
bun run dev:full  # Starts Next.js app and realtime socket server

Or run separately: bun run dev (Next.js) and cd apps/sim && bun run dev:sockets (realtime).

Copilot API Keys

Copilot is a Sim-managed service. To use Copilot on a self-hosted instance:

  • Go to https://sim.ai → Settings → Copilot and generate a Copilot API key
  • Set COPILOT_API_KEY environment variable in your self-hosted apps/sim/.env file to that value

Environment Variables

See the environment variables reference for the full list, or apps/sim/.env.example for defaults.

Tech Stack

Contributing

We welcome contributions! Please see our Contributing Guide for details.

License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

Made with ❤️ by the Sim Team

Languages
TypeScript 77%
MDX 20.8%
JavaScript 1.9%
CSS 0.1%