Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Map source-code relationships between symbols. An agent skill from syncable-dev/memtrace-public.
Install Memtrace Relationships
$ npx skills add syncable-dev/memtrace-public --skill memtrace-relationships -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-relationships --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-relationships .claude/skills/memtrace-relationships && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "memtrace-relationships" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-relationships into .claude/skills/memtrace-relationships/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-relationships", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-relationshipsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add syncable-dev/memtrace-public --skill memtrace-relationships -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-relationships --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-relationships .agents/skills/memtrace-relationships && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "memtrace-relationships" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-relationships into .agents/skills/memtrace-relationships/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-relationships", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add syncable-dev/memtrace-public --skill memtrace-relationships -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-relationships --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-relationships .cursor/skills/memtrace-relationships && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "memtrace-relationships" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-relationships into .cursor/skills/memtrace-relationships/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-relationships", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/syncable-dev/memtrace-public.git --path plugins/memtrace-skills/skills/memtrace-relationships--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add syncable-dev/memtrace-public --skill memtrace-relationships -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-relationships --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-relationships .gemini/skills/memtrace-relationships && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "memtrace-relationships" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-relationships into .gemini/skills/memtrace-relationships/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-relationships", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install syncable-dev/memtrace-public memtrace-relationshipsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add syncable-dev/memtrace-public --skill memtrace-relationships -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-relationships .github/skills/memtrace-relationships && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "memtrace-relationships" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-relationships into .github/skills/memtrace-relationships/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-relationships", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add syncable-dev/memtrace-public --skill memtrace-relationships -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-relationships --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/syncable-dev/memtrace-public.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/memtrace-skills/skills/memtrace-relationships .opencode/skills/memtrace-relationships && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "memtrace-relationships" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-relationships into .opencode/skills/memtrace-relationships/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-relationships", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
memtrace-relationships- GitHub stars
- 487
- Token cost
- ~895 tokens
- SKILL.md length
- 288 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Map source-code relationships between symbols. An agent skill from syncable-dev/memtrace-public.
- Works in 4 steps: Get the symbol name → Choose your approach → Interpret results → …
- The user asks about callers
- SKILL.md covers Overview, Quick Reference, Graph tool parameters and Steps, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Memtrace Relationships is an agent skill from syncable-dev/memtrace-public. Map source-code relationships between symbols. Use when the user asks about callers, callees, references, imports, exports, type usages, class hierarchy, inheritance, implementations, overrides, or dependencies between symbols. Do not use Grep, Glob, rg, find, or manual text search for references; Memtrace traverses typed AST graph edges.
Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: Structural memory for AI coding agents. Bi-temporal graph, MCP-native, zero LLM calls. Cursor · Claude Code · Codex · DeepSeek Harness · Hermes · VS Code · Windsurf.
When your agent uses it
- The user asks about callers
- Class hierarchy
- Implementations
- Dependencies between symbols
Example prompts
- “/memtrace-relationships”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Get the symbol name
- Choose your approach
- Interpret results
- Follow up
What it can do on your machine
Read from SKILL.md and the folder at commit 3a3084d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Memtrace Relationships loads about 895 tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 288 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 288 words (~895 tokens).
“Traverse the code knowledge graph to map relationships between symbols — callers, callees, class hierarchies, imports, exports, and type usages. Essential for understanding a symbol's neighbourhood before modifying it.”
- name
- memtrace-relationships
Files
Just SKILL.md in plugins/memtrace-skills/skills/memtrace-relationships of syncable-dev/memtrace-public.
Open the folder on GitHubat commit 3a3084d
Compare with similar skills
Memtrace Relationships next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Memtrace Relationships this skillsyncable-dev/memtrace-public | 487 | — | ~895 | Automated safety check: Pass | Custom licence | |
| Vercel Composition Patternssupabase/supabase | 111k | 59 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from syncable-dev/memtrace-public
All 27 skills in this repoMemtrace Change Impact Analysis
syncable-dev/memtrace-public
Compute what a planned source-code change will break — blast radius, affected processes, cross-repo callers, temporal stability, and Cortex decision-memory constraints — and produce a risk-rated…
Memtrace Cochange
syncable-dev/memtrace-public
Find files that historically co-change with a target symbol or file, ranked by co-occurrence across git episodes.
Memtrace Code Review
syncable-dev/memtrace-public
Review GitHub pull requests with Memtrace's local graph-backed review engine.
Memtrace Codebase Exploration
syncable-dev/memtrace-public
Map an indexed source-code repo into a structured overview — scale, communities, central symbols, execution flows, API surface, recent activity.
Memtrace Continuous Memory
syncable-dev/memtrace-public
Keep the Memtrace index fresh while editing by watching a repo for live, incremental re-indexing.
Memtrace Decision Memory
syncable-dev/memtrace-public
Use Cortex decision memory through the normal Memtrace MCP tools.
Related
Categories
Questions about Memtrace Relationships
What does Memtrace Relationships do?
Map source-code relationships between symbols. An agent skill from syncable-dev/memtrace-public. Memtrace Relationships is an agent skill from syncable-dev/memtrace-public. Map source-code relationships between symbols.
When should I use Memtrace Relationships?
Memtrace Relationships fits situations like: the user asks about callers; class hierarchy; implementations; dependencies between symbols.
How do I install Memtrace Relationships in Claude Code?
Run `npx skills add syncable-dev/memtrace-public --skill memtrace-relationships -a claude-code`. Or copy the skill folder (plugins/memtrace-skills/skills/memtrace-relationships in syncable-dev/memtrace-public) into .claude/skills/memtrace-relationships in your project. Claude Code loads it when a task matches its description.
How do I install Memtrace Relationships in Codex?
Run `npx skills add syncable-dev/memtrace-public --skill memtrace-relationships -a codex`. Or copy the skill folder (plugins/memtrace-skills/skills/memtrace-relationships in syncable-dev/memtrace-public) into .agents/skills/memtrace-relationships in your project. Codex loads it when a task matches its description.
Can I use Memtrace Relationships in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add syncable-dev/memtrace-public --skill memtrace-relationships -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memtrace-relationships, .gemini/skills/memtrace-relationships, .github/skills/memtrace-relationships and .opencode/skills/memtrace-relationships in your project.
What does Memtrace Relationships need to run?
SKILL.md names no scripts, command-line tools or credentials: Memtrace Relationships is instructions for the agent only.
Does Memtrace Relationships access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Memtrace Relationships safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Memtrace Relationships use?
Memtrace Relationships has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Memtrace Relationships use?
About 895 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Memtrace Relationships?
Skills that share tags, products or a category with Memtrace Relationships: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Memtrace Relationships?
syncable-dev (a GitHub organization) maintains it in syncable-dev/memtrace-public, which has 487 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 8, 2026.
Source: syncable-dev/memtrace-public on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.