Automated summary

Manually uploads the current repository's persistent memory database to a self-hosted dashboard.

Strengths

Single command that runs the sync script with no extra runtime setup
Repository slug is derived automatically from the git remote URL, so pushes land in the right per-repo storage
Clear error messages for common failures (no configured remote, no local database) with next steps
Handy for quickly confirming dashboard reachability and that the token works

Limitations

Assumes the plugin is already installed (claude-turbo-search directory) and the dashboard is reachable
Does not set up the remote or token itself; that requires memorydb config set
Redundant after /remember, which already pushes automatically

When to use it

Use it after running add-fact, add-knowledge, or consolidate directly, or to force a mid-session sync.

When not to use it

Skip it after /remember or in routine workflows, where the push happens at the natural session boundary.

Security analysis

Caution

Quality score80/100

The instructions are transparent and the upload targets a user-configured self-hosted dashboard, so this is not inherently malicious. However, it shells out to a script and transmits the local memory database plus an auth token over the network, which warrants a caution rating rather than safe.

Findings

•Executes a local shell script ($PLUGIN_DIR/memory/memory-db.sh push) via bash, giving the agent arbitrary command execution within the plugin directory
•Uploads the full memory database (.claude-memory/memory.db) — potentially containing sensitive session data, facts, and knowledge — to a remote HTTP endpoint
•Uses a stored auth token and a user-configurable remote URL; a misconfigured or spoofed remote/token could send memory data to an unintended destination
•PLUGIN_DIR is taken from the environment, so a tampered or unexpected path could execute a different script
•No declared allowed-tools, so tool permissions are implicit rather than explicit

How this analysis is made

Examples

Sync after manual fact edit

/push — I just ran add-fact directly and want the dashboard to reflect it.

Force a mid-session refresh

Push the current memory database now so the dashboard is up to date before I wrap up.

Check dashboard connectivity

/push to verify my token still works and the dashboard is reachable.

name: push description: Manually upload the persistent memory database to your self-hosted dashboard. Useful after directly running add-fact or add-knowledge — for normal session work, /remember already auto-pushes.

/push - Upload Memory To Dashboard

Name: Push memory to dashboard
Author: Skills Guide Bot

Send the current repo's .claude-memory/memory.db to your self-hosted Fly.io dashboard. Slug is derived from git remote get-url origin, so it lands on the right per-repo storage automatically.

Instructions

When the user invokes /push, run:

PLUGIN_DIR="${PLUGIN_DIR:-$HOME/claude-turbo-search}"
MEMORY_SCRIPT="$PLUGIN_DIR/memory/memory-db.sh"

"$MEMORY_SCRIPT" push

Common outcomes

Happy path:

Pushed .../memory.db to https://<dashboard>/api/repos/<slug>/push

Tell the user the dashboard now reflects this push.

No config — message will be:

no sync remote configured. run `memorydb config set --remote URL --token TOKEN`

Tell the user how to configure it.

No local DB — message will be:

no memory database at <path> — nothing to push

Suggest running /remember first (which creates the DB if needed).

When to use

After manually editing memory — running add-fact, add-knowledge, or consolidate directly via memory-db.sh doesn't trigger an auto-push. Use /push to sync.
Forcing a sync mid-session — when you want the dashboard fresh without waiting for /remember.
Verifying connectivity — quick way to confirm the dashboard is reachable and your token works.

When NOT to use

After /remember — that skill auto-pushes already.
Routine workflow — let /remember handle pushes at the natural session boundary.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/push-memory-to-dashboard-ms47vpjz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/push-memory-to-dashboard-ms47vpjz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/push-memory-to-dashboard-ms47vpjz/download' --output '.skill-downloads/push-memory-to-dashboard-ms47vpjz/SKILL.md.part' && mv '.skill-downloads/push-memory-to-dashboard-ms47vpjz/SKILL.md.part' '.skill-downloads/push-memory-to-dashboard-ms47vpjz/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/push-memory-to-dashboard-ms47vpjz/SKILL.md' && test -s '.skill-downloads/push-memory-to-dashboard-ms47vpjz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/push' && cp -R '.skill-downloads/push-memory-to-dashboard-ms47vpjz' '.claude/skills/push'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/push-memory-to-dashboard-ms47vpjz'

openskills read 'push-memory-to-dashboard-ms47vpjz'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/push-memory-to-dashboard-ms47vpjz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122

Skills Guide Bot