Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
Declare a structural intent BEFORE editing in a fleet — what symbols you'll touch and why — so other agents on your branch coordinate around you.
Install Memtrace Fleet Publish Intent
$ npx skills add syncable-dev/memtrace-public --skill memtrace-fleet-publish-intent -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-fleet-publish-intent --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-fleet-publish-intent .claude/skills/memtrace-fleet-publish-intent && 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-fleet-publish-intent" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-fleet-publish-intent into .claude/skills/memtrace-fleet-publish-intent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-fleet-publish-intent", 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-fleet-publish-intentType 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-fleet-publish-intent -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-fleet-publish-intent --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-fleet-publish-intent .agents/skills/memtrace-fleet-publish-intent && 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-fleet-publish-intent" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-fleet-publish-intent into .agents/skills/memtrace-fleet-publish-intent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-fleet-publish-intent", 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-fleet-publish-intent -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-fleet-publish-intent --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-fleet-publish-intent .cursor/skills/memtrace-fleet-publish-intent && 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-fleet-publish-intent" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-fleet-publish-intent into .cursor/skills/memtrace-fleet-publish-intent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-fleet-publish-intent", 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-fleet-publish-intent--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-fleet-publish-intent -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install syncable-dev/memtrace-public memtrace-fleet-publish-intent --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-fleet-publish-intent .gemini/skills/memtrace-fleet-publish-intent && 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-fleet-publish-intent" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-fleet-publish-intent into .gemini/skills/memtrace-fleet-publish-intent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-fleet-publish-intent", 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-fleet-publish-intentInstalls 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-fleet-publish-intent -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-fleet-publish-intent .github/skills/memtrace-fleet-publish-intent && 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-fleet-publish-intent" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-fleet-publish-intent into .github/skills/memtrace-fleet-publish-intent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-fleet-publish-intent", 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-fleet-publish-intent -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-fleet-publish-intent --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-fleet-publish-intent .opencode/skills/memtrace-fleet-publish-intent && 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-fleet-publish-intent" agent skill from https://github.com/syncable-dev/memtrace-public/tree/main/plugins/memtrace-skills/skills/memtrace-fleet-publish-intent into .opencode/skills/memtrace-fleet-publish-intent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memtrace-fleet-publish-intent", 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-fleet-publish-intent- GitHub stars
- 486
- Token cost
- ~675 tokens
- SKILL.md length
- 156 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Declare a structural intent BEFORE editing in a fleet — what symbols you'll touch and why — so other agents on your branch coordinate around you.
- The user says Im about to edit/rename/refactor X
- SKILL.md covers Overview, Call it, Output and Intent kinds (JSON,…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Starting any non-trivial edit while other agents share your repo+branch
What it does
Memtrace Fleet Publish Intent is an agent skill from syncable-dev/memtrace-public. Declare a structural intent BEFORE editing in a fleet — what symbols you'll touch and why — so other agents on your branch coordinate around you. Use when the user says 'I'm about to edit/rename/refactor X', or when starting any non-trivial edit while other agents share your repo+branch. Returns the graph blast radius, overlapping live intents on your branch, and a shift-left coordination/partition hint. Do not start editing shared symbols without publishing first.
Its SKILL.md is about 680 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, covering Refactoring. 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 says Im about to edit/rename/refactor X
- Starting any non-trivial edit while other agents share your repo+branch
Example prompts
- “m about to edit/rename/refactor X”
- “/memtrace-fleet-publish-intent”
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 jsonc and 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 Fleet Publish Intent loads about 675 tokens when it runs. Until then it costs about 125 tokens; SKILL.md has 156 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 156 words (~675 tokens).
“fleet_publish_intent is step 1 of the fleet protocol: announce what you're about to touch so other agents on the same (repo, branch) coordinate around you. It's a typed, ~20-token declaration — not prose.”
- name
- memtrace-fleet-publish-intent
Files
Just SKILL.md in plugins/memtrace-skills/skills/memtrace-fleet-publish-intent of syncable-dev/memtrace-public.
Open the folder on GitHubat commit 3a3084d
Compare with similar skills
Memtrace Fleet Publish Intent 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 Fleet Publish Intent this skillsyncable-dev/memtrace-public | 486 | — | ~675 | Automated safety check: Pass | Custom licence | |
| Guidelinesakash-network/node | 1.1k | 22 repos | ~577 | Automated safety check: Pass | MIT | |
| Component Refactoringlangflow-ai/langflow | 156k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 41k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| ast-grep Structural Searchcode-yeongyu/oh-my-openagent | 70k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Systematic Code Refactoringluongnv89/claude-howto | 42k | — | ~3k | Automated safety check: Pass | MIT |
Similar skills
Component Refactoring
langflow-ai/langflow
Refactor high-complexity React components in Langflow frontend.
Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
ast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
Systematic Code Refactoring
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
Codex
skills-directory/skill-codex
A skill your agent uses when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing
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 Fleet Publish Intent
What does Memtrace Fleet Publish Intent do?
Declare a structural intent BEFORE editing in a fleet — what symbols you'll touch and why — so other agents on your branch coordinate around you. Memtrace Fleet Publish Intent is an agent skill from syncable-dev/memtrace-public. Declare a structural intent BEFORE editing in a fleet — what symbols you'll touch and why — so other agents on your branch coordinate around you.
When should I use Memtrace Fleet Publish Intent?
Memtrace Fleet Publish Intent fits situations like: the user says Im about to edit/rename/refactor X; starting any non-trivial edit while other agents share your repo+branch.
How do I install Memtrace Fleet Publish Intent in Claude Code?
Run `npx skills add syncable-dev/memtrace-public --skill memtrace-fleet-publish-intent -a claude-code`. Or copy the skill folder (plugins/memtrace-skills/skills/memtrace-fleet-publish-intent in syncable-dev/memtrace-public) into .claude/skills/memtrace-fleet-publish-intent in your project. Claude Code loads it when a task matches its description.
How do I install Memtrace Fleet Publish Intent in Codex?
Run `npx skills add syncable-dev/memtrace-public --skill memtrace-fleet-publish-intent -a codex`. Or copy the skill folder (plugins/memtrace-skills/skills/memtrace-fleet-publish-intent in syncable-dev/memtrace-public) into .agents/skills/memtrace-fleet-publish-intent in your project. Codex loads it when a task matches its description.
Can I use Memtrace Fleet Publish Intent 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-fleet-publish-intent -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-fleet-publish-intent, .gemini/skills/memtrace-fleet-publish-intent, .github/skills/memtrace-fleet-publish-intent and .opencode/skills/memtrace-fleet-publish-intent in your project.
What does Memtrace Fleet Publish Intent need to run?
SKILL.md names no scripts, command-line tools or credentials: Memtrace Fleet Publish Intent is instructions for the agent only.
Does Memtrace Fleet Publish Intent 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 Fleet Publish Intent 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 Fleet Publish Intent use?
Memtrace Fleet Publish Intent 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 Fleet Publish Intent use?
About 675 tokens (SKILL.md is roughly 2.7k 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 Fleet Publish Intent?
Skills that share tags, products or a category with Memtrace Fleet Publish Intent: Guidelines (akash-network/node, 1.1k stars), Component Refactoring (langflow-ai/langflow, 156k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars) and ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Memtrace Fleet Publish Intent?
syncable-dev (a GitHub organization) maintains it in syncable-dev/memtrace-public, which has 486 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 6, 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.