Skip to content
Skills Library
AI & agents · Automation

synapt

/synapt

synapt recall and dashboard workflow. Use this when operating the MCP memory/channel tools, debugging recall index or channel issues, or working on dashboard and mission-control flows.

Repository
recall ↗
Licence
MIT
Last repository change
23.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

synapt recall and dashboard workflow. Use this when operating the MCP memory/channel tools, debugging recall index or channel issues, or working on dashboard and mission-control flows.

Original author description

synapt recall and dashboard workflow. Use this when operating the MCP memory/channel tools, debugging recall index or channel issues, or working on dashboard and mission-control flows.

How it works

  1. Core Rules
  2. Tool Choice
  3. Channel Debugging
  4. Index / Recall Debugging
  5. Dashboard / Mission Control
  6. Review Bias
Original SKILL.md headings · 86 lines, 399 words
SKILL.md preview
---
name: synapt
description: synapt recall and dashboard workflow. Use this when operating the MCP memory/channel tools, debugging recall index or channel issues, or working on dashboard and mission-control flows.
---

# synapt Workflow

Use the synapt MCP and repo surfaces deliberately. Prefer the narrowest tool that matches the job, and keep channel/index/root-resolution bugs scoped to the real store in play.

## Core Rules

1. Treat `#dev` as shared operational memory. Read the live channel state before acting on stale assumptions.
2. Use `recall_quick` for cheap speculative lookup, `recall_search` for real retrieval, and `recall_context` only when you need the raw supporting detail.
3. Use `recall_channel(action="unread")` for loop polling first; fall back to a bounded `read` only when unread looks suspicious.
4. Distinguish local project recall state from shared/global channel or org state before debugging.
5. For dashboard or channel bugs, verify the actual runtime checkout and install path before assuming the local repo is what is serving traffic.

## Tool Choice

### Retrieval

```text
recall_quick
recall_search
recall_context
recall_sessions
recall_files
```

### Channel / Ops

```text
recall_channel(action="unread")
recall_channel(action="read", limit=5)
recall_channel(action="post")
recall_channel(action="who")
recall_channel(action="heartbeat")
```

### Persistent memory

```text
recall_journal(action="read" | "write" | "pending")
recall_save
recall_promote
recall_identity
recall_career
```

## Channel Debugging

When channel behavior looks wrong, check these explicitly:

- which project root resolved the channel DB path
- whether the session is in the correct channel store
- whether `unread`, `who`, and `join` agree on membership
- whether the bug is channel-log based, DB-based, or dashboard/API glue

Do not assume a dashboard send bug, unread bug, and store-routing bug are the same issue.

## Index / Recall Debugging

When a recall tool is slow or timing out:

1. isolate whether the cost is `_get_index()` / load time or the actual operation
2. check whether embeddings are being loaded unnecessarily
3. distinguish “no local index” from “shared index is huge/slow”
4. verify whether the current workspace is using the intended recall store

For session/history tools, prefer the no-embeddings path when embeddings are not required.

## Dashboard / Mission Control

For dashboard work, check all three paths:

- API shape in `dashboard/app.py`
- recall/channel read/write helpers underneath
- actual runtime install path serving the dashboard

Cross-project mission-control work should preserve the selected org/project/channel all the way through fetch, send, and live refresh.

## Review Bias

When reviewing synapt changes, look for:

- wrong store/root/channel path resolution
- hidden fallback from shared wrapper to local DB implementation
- tests that only cover the happy path, not cross-project or restart behavior
- performance fixes that accidentally pull embeddings or full index loads into cheap operations

Versions

RepositoryScoreLicence
This page · synapt-dev/recall100MIT
synapt-dev/recall100MIT

Database snapshot: 13.11.2026 · package version 5dd0b311627a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100recall-lang
    Configure the language(s) used by the agd-memory auto-recall hook for stopword filtering. Use when the user says \"enable italian recall\", \"abilita italiano per il recall\", \"set recall language\", \"which languages for recall\", \"disabilita italiano recall\", \"reset recall…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.