Synap-core
@Synap-core Organization
Public Skills
synap
by Synap-core
Use this skill whenever the user wants to capture, remember, find, or structure information in their Synap data pod. Triggers: creating a task, note, person, company, project, event, contact, or deal; saving an article or webpage; storing a fact about someone ("Alice prefers async"); searching the user's knowledge ("find my notes on X", "who did I meet last week"); linking entities; logging a meeting or a contact; capturing unstructured text into structured entities; reading what's in the user's pod before answering questions about their life, work, or projects; posting to their personal AI channel. The pod is the user's sovereign source of truth — prefer it over your own context when the user asks about their own data. Do NOT use this skill for extending the schema (use synap-schema) or building dashboards and views (use synap-ui).
synap-app
by Synap-core
Use this skill when the user wants to BUILD THEIR OWN APP on top of Synap — a personal project or a product — using Synap as the backend (auth, typed data API, realtime). Two paths: add the SDK (@synap-core/sdk) to an existing app, or scaffold the opinionated Next.js + HeroUI base app (npx create-synap-app). Triggers: "build an app on Synap", "use Synap as my backend", "scaffold a Synap project", "add the Synap SDK", "connect my app to my pod", "npx create-synap-app". NOT the synap skill (capture/recall in a pod) nor synap-ui (views inside the pod's own UI) — this is about writing app CODE.
agent-os
by Synap-core
Use this skill to PROVISION operational domains (workspaces) from templates — Company OS / "add a CRM" / "we need somewhere to record deals". Triggers: "set up my company", "launch agent OS", "build my company OS", "onboard my company", "add a Marketing workspace", "this project doesn't have a CRM". NOT for a lasting goal a project pursues (grow the newsletter, the build) — that is a goal (synap_start_track), not a workspace. Find existing workspace → marketplace template → confirm → packages/apply. NOT the skill for "the user stated an intent, what graph should exist" — that conductor is system/synap/from-intent (orient, questions, extend-first, then load THIS skill only if a domain is actually missing). A project is optional (reuse if present; never invent one on a team pod). Ask, don't assume.
onboard
by Synap-core
Use this skill when the active LENS (a workspace, a project, or both) has little/no data and the user wants it set up — including a NEW project that is empty even though its workspace already holds other projects' data. Triggers: "onboard this", "set up my <X> workspace", "set up this project", "help me fill this in", a freshly-created workspace, or scoping to a project with no entities. This is the ONE shared, adaptive onboarding process: it detects emptiness THROUGH the active lens, reads the space's BRIEF (settings.onboarding — its interview fields are the onboarding mode) for the domain knowledge, runs a goal-driven interview, and scopes every captured entity to the active lens (workspace + project). No per-domain skill — the domain is data on the space; this skill is the reusable intelligence that consumes it.