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.zipInstalls 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).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
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
instructionsfield is derived from this file and composed with live grounding under ONE 2 KB budget (pinned byinstructions-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).
- Recall first.
get_*a known id, elseask. - Capture as you go. A decision, learning, pain (
finding), win (proof-point), fact or task:captureit when it happens; about the user:remember_fact. - Orient once.
orient: pending review, open sessions. - Work in a session.
start_sessionor resume (playbooktemplateId); goal (TRACK):list_tracks, elsestart_track; work in it =start_session+trackId; 2-5criteria; status moves carryexpectedStatus; person-only:owner:'human'slot +blockedReason+ask(confirm/choose with 1recommended/form/act/provide), thenwait_for_answerif listed; post progress, questions and results in its room (post_messagetosession.channelId); your own chat may repeat them (Q-<id8>); chat answer →relay_answer, words verbatim; PR = outcomepr-<repo>-<n>(ref.url);evaluate_session, close open asks,complete_session. - Never guess a project: pin only what the user names (
set_*_focus). proposedis success: keep going, never retry.- Discover before inventing:
list_profiles/list_capabilities; extend, never a twin. - 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.
| Word | Internal | Answers | Test · e.g. · not |
|---|---|---|---|
| Space | workspace | which domain: kinds + tools? | owns kinds, never done · CRM · not a project or method; findable, not emphasised |
| Project | project | what am I committed to, with whom? | ends with the commitment; spans spaces · a launch · not a task, method, or the owner's company |
| Pillar | project-to-space link (uses) + purpose | which 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) |
| Goal | project_tracks | what 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" |
| Step | stage | where does this work stand? | = the subject's status: move the thing, the step follows · legacy: steps of a goal started from a method |
| Work | focus_session | what am I doing this sitting? | one aim · no noun: "Start work" |
| Process | playbook | how 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 |
| Pack | suite | which templates come together? | a bundle; depends on space templates, never creates a space |
| Rule | skill rule | what do my agents always follow? | a standing instruction written for agents · "always cite sources" · not an Automation, not Approvals |
| Automation | automation | what runs by itself, when? | standing · "every Monday…" · not a Rule, not Approvals |
| Approvals | governance rules | which AI writes wait for me? | decides review vs auto, does no work |
| Tools | capability, skill, tool | what can it act with? | one word; the detail shows the kind |
| Card | cell | what block did I make? | the made UI block · "a deals summary" · never Cell, Widget or Interface |
| Display | renderer | how does this kind look? | a card bound to a kind's slot · "Change display" · Renderer stays an engine word |
| View | view | how do I look at the data? | a saved arrangement of things · a table, a board · not a Card |
| App | built-in surface | what do I open in Synap? | CRM, Calendar, a space's own front end · never a space, never outside software |
| Connected app | application | which outside software holds a grant? | reaches the pod with a grant · not an App |
| Account | provider connection | which of my accounts is linked? | a person's link to an outside service · never Connection, Connector or Integration |
| Kind | profile | what shape does a thing have? | its fields and status list · never Data type, Schema or Profile |
| Make | destination | where do I make things? | a view, a card, a space, an automation · pairs with Work |
| Get more | destination | where do I add more? | the store · never Marketplace or Get more tools |
| To review | proposal | what awaits my approval? | proposed is success |
| Role | role profile + facet | which hat does it wear? | one role per name, pod-wide; spaces add properties by overlay; its entities show in all · client · never a twin |
| Thing | entity | what 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
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| synap (this skill) | 0 | 4mo | Review | Intermediate |
| agent-memory-mcp | 8 | 10mo | Review | Intermediate |
| braindump | 7 | 9mo | No flags | Beginner |
| context-management | 1 | 1y | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
agent-memory-mcp
davila7
A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
braindump
huytieu
Quick capture of raw thoughts with intelligent domain classification and competitive intelligence extraction
context-management
No-Trade-No-Life
在多轮对话和多 Agent 协作场景下,帮助模型管理指令、项目状态和长上下文。通过外部文档与会话笔记实现可控的“记忆”、指令冲突检测和高质量交接。适用于任务跨多次调用、跨 Agent、需要稳定行为规范时使用。
hindsight-cloud
vectorize-io
Store team knowledge, project conventions, and learnings from tasks. Use to remember what works and recall context before new tasks. Connects to Hindsight Cloud. (user)
ask
Lambenthan
对 wiki 提问,综合检索相关页面后回答,好的回答可 crystallize 回 wiki
knowledge-ops
ThanhTrunggDEV
Knowledge base management, ingestion, sync, and retrieval across multiple storage layers (local files, MCP memory, vector stores, Git repos). Use when the user wants to save, organize, sync, deduplicate, or search across their knowledge systems.