The primary interface for managing knowledge and structured data within a Synap pod.

Install

mkdir -p .claude/skills/synap && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14414" && unzip -o skill.zip -d .claude/skills/synap && rm skill.zip

Installs to .claude/skills/synap

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

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).
844 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • →Capture unstructured text into structured entities
  • →Retrieve information from the user's data pod
  • →Link entities within a knowledge graph
  • →Log meetings or contacts
  • →Read existing data before answering questions
  • →Post to personal AI channels

How it works

The skill interacts with a Synap Data Pod to capture, retrieve, and structure information. It prioritizes recalling existing knowledge before creating new entries and treats 'proposed' responses as successful-in-review.

Inputs & outputs

You give it
Unstructured information, search queries, entity creation requests
You get back
Structured entities in Synap pod, retrieved information, linked entities

When to use synap

  • →Capture new task in pod
  • →Search notes on project
  • →Link entities in knowledge graph

About this skill

Synap — core data operations

You are connected to a Synap Data Pod at {SYNAP_POD_URL}. All requests use Authorization: Bearer {SYNAP_HUB_API_KEY}.

If you have Bash access (Claude Code, agent with tools): use the synap CLI — see CLI Data Operations below. Auth is automatic, --json gives clean output, no manual header management.

If you only have HTTP access: use the REST endpoints documented below. Your userId is in {SYNAP_USER_ID} (set by synap connect). If it's missing, call GET /api/hub/users/me → .id once.

Your job is to turn unstructured input into a connected knowledge graph. Isolated entities are anti-value. Every entity you create should link to at least one other entity.


Reflexes — what holds on every door

Canonical source — the MCP instructions field is derived from this file and composed with live grounding under ONE 2 KB budget (pinned by instructions-budget.test.ts). Most important first. Depth belongs in a skill, never here.

The user's Synap pod: source of truth. Tool names below are stems; your door may prefix them (synap_ask).

  1. Recall first. get_* a known id, else ask.
  2. Capture as you go. A decision, learning, pain (finding), win (proof-point), fact or task: capture it when it happens; about the user: remember_fact.
  3. Orient once. orient: pending review, open sessions.
  4. Work in a session. start_session or resume (playbook templateId); goal (TRACK): list_tracks, else start_track; work in it = start_session + trackId; 2-5 criteria; status moves carry expectedStatus; person-only: owner:'human' slot + blockedReason + ask (confirm/choose with 1 recommended/form/act/provide), then wait_for_answer if listed; post progress, questions and results in its room (post_message to session.channelId); your own chat may repeat them (Q-<id8>); chat answer → relay_answer, words verbatim; PR = outcome pr-<repo>-<n> (ref.url); evaluate_session, close open asks, complete_session.
  5. Never guess a project: pin only what the user names (set_*_focus).
  6. proposed is success: keep going, never retry.
  7. Discover before inventing: list_profiles / list_capabilities; extend, never a twin.
  8. One space per domain; projects filter it (file_into_project, project_use_workspace).

Depth: load_skill system/synap/concepts, work-model, focus-sessions, from-intent, escalation-ladder, writes.


Concepts — one word per idea

The ONE glossary; other skills point here. Word = what the user sees; internal = tools and tables.

WordInternalAnswersTest · e.g. · not
Spaceworkspacewhich domain: kinds + tools?owns kinds, never done · CRM · not a project or method; findable, not emphasised
Projectprojectwhat am I committed to, with whom?ends with the commitment; spans spaces · a launch · not a task, method, or the owner's company
Pillarproject-to-space link (uses) + purposewhich space carries this project, and why?a space the project uses, with a purpose; its health is derived from the goals that advance it · not a kind, not the Content OS pillar kind or Brand "content pillars" (editorial themes)
Goalproject_trackswhat goal am I pursuing?in ONE project; open while it matters, or its judge closes it with a verdict; criteria say when it is done; work = sessions · grow the newsletter · tools say "track"
Stepstagewhere does this work stand?= the subject's status: move the thing, the step follows · legacy: steps of a goal started from a method
Workfocus_sessionwhat am I doing this sitting?one aim · no noun: "Start work"
Processplaybookhow do I reuse it?kind DERIVED, never declared: scope session = process (a method a session or worker follows), project = goal process (legacy) · "Template" now names only a space template
Packsuitewhich templates come together?a bundle; depends on space templates, never creates a space
Ruleskill rulewhat do my agents always follow?a standing instruction written for agents · "always cite sources" · not an Automation, not Approvals
Automationautomationwhat runs by itself, when?standing · "every Monday…" · not a Rule, not Approvals
Approvalsgovernance ruleswhich AI writes wait for me?decides review vs auto, does no work
Toolscapability, skill, toolwhat can it act with?one word; the detail shows the kind
Cardcellwhat block did I make?the made UI block · "a deals summary" · never Cell, Widget or Interface
Displayrendererhow does this kind look?a card bound to a kind's slot · "Change display" · Renderer stays an engine word
Viewviewhow do I look at the data?a saved arrangement of things · a table, a board · not a Card
Appbuilt-in surfacewhat do I open in Synap?CRM, Calendar, a space's own front end · never a space, never outside software
Connected appapplicationwhich outside software holds a grant?reaches the pod with a grant · not an App
Accountprovider connectionwhich of my accounts is linked?a person's link to an outside service · never Connection, Connector or Integration
Kindprofilewhat shape does a thing have?its fields and status list · never Data type, Schema or Profile
Makedestinationwhere do I make things?a view, a card, a space, an automation · pairs with Work
Get moredestinationwhere do I add more?the store · never Marketplace or Get more tools
To reviewproposalwhat awaits my approval?proposed is success
Rolerole profile + facetwhich hat does it wear?one role per name, pod-wide; spaces add properties by overlay; its entities show in all · client · never a twin
Thingentitywhat is being worked on?one kind, maybe roles · a post, a

Content truncated.

When not to use it

  • →When extending the schema
  • →When building dashboards and views
  • →When inventing workspaces from capture

Prerequisites

SYNAP_HUB_API_KEYSYNAP_POD_URL

Limitations

  • →Do NOT use this skill for extending the schema
  • →Do NOT use this skill for building dashboards and views
  • →Capture placement routes to EXISTING lenses only , never invent a workspace from capture

How it compares

This skill provides a structured way to manage personal data as a 'sovereign source of truth,' differing from relying on the agent's own context or training data for user-specific information.

Compared to similar skills

synap side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
synap (this skill)04moReviewIntermediate
agent-memory-mcp810moReviewIntermediate
braindump79moNo flagsBeginner
context-management11yNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry