Syncmeta logo

Syncmeta

CommunityPopular
pawurb
syncmeta

Sync changes from the hotpath, hotpath-macros and hotpath-drain crates to their meta counterparts (hotpath-meta, hotpath-macros-meta and hotpath-drain-meta). Use when meta crates need to be updated with recent changes.

Overview

Publisherpawurb
Repositoryhotpath-rs
Skill namesyncmeta
Stars
1.7K
Forks
51
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by pawurb on GitHub. Read the source before you install it.

Installation

Install the Syncmeta AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/pawurb/hotpath-rs.git /tmp/hotpath-rs
mkdir -p .claude/skills
cp -r /tmp/hotpath-rs/skills/syncmeta .claude/skills/syncmeta
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Syncmeta in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Syncmeta on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Syncmeta is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Sync Meta Crates

Sync recent changes from hotpathhotpath-meta, hotpath-macroshotpath-macros-meta and hotpath-drainhotpath-drain-meta.

The meta crates are copies of the main crates used to profile the profiler itself. They must stay in sync with the source crates.

Effective Approach

DO NOT copy entire files from hotpath to hotpath-meta and then sed-replace. This approach fails because the meta crates have many naming differences beyond simple hotpath::hotpath_meta:: substitution:

  • Feature flags: hotpathhotpath-meta, hotpath-allochotpath-alloc-meta, hotpath-cpuhotpath-cpu-meta, hotpath-cloudhotpath-cloud-meta, hotpath-prometheushotpath-prometheus-meta, hotpath-mcphotpath-mcp-meta
  • Crate imports: hotpath_macroshotpath_macros_meta, hotpath_drainhotpath_drain_meta
  • Environment variables: HOTPATH_FOCUSHOTPATH_META_FOCUS, HOTPATH_EXCLUDE_WRAPPERHOTPATH_META_EXCLUDE_WRAPPER, HOTPATH_OUTPUT_PATHHOTPATH_META_OUTPUT_PATH
  • Self-instrumentation: lines like #[cfg_attr(feature = "hotpath-meta", hotpath_meta::measure_all)] exist in hotpath but must NOT exist in hotpath-meta
  • hotpath-drain-meta is the simplest mirror: it has no features and no dependencies, so syncing hotpath-drain means applying the diff and dropping the #[cfg_attr(feature = "hotpath-meta", hotpath_meta::measure(...))] lines. Nothing else is renamed - there is no hotpath-drain-meta feature flag.

Instead, apply diffs to the existing meta files:

  1. Get the actual diff for each changed file: git diff HEAD~N..HEAD -- crates/hotpath/src/path/to/file.rs
  2. Read the corresponding meta file
  3. Apply the equivalent semantic changes, preserving all meta-specific naming

Steps

  1. Check the last N commits (default 1, user can specify more) for changes to crates/hotpath/, crates/hotpath-macros/ and crates/hotpath-drain/:
git log --oneline -N
git diff HEAD~N..HEAD --name-only -- crates/hotpath/src/ crates/hotpath-macros/src/ crates/hotpath-drain/src/
  1. For each changed file, get the source diff:
git diff HEAD~N..HEAD -- crates/hotpath/src/path/to/file.rs
git diff HEAD~N..HEAD -- crates/hotpath-drain/src/lib.rs
  1. Read the corresponding meta file and apply the equivalent changes using Edit tool. The meta files are at:

    • crates/hotpath/src/**crates/hotpath-meta/src/**
    • crates/hotpath-macros/src/**crates/hotpath-macros-meta/src/**
    • crates/hotpath-drain/src/**crates/hotpath-drain-meta/src/**
  2. Verify the meta crates compile:

cargo check -p hotpath-drain-meta
cargo check -p hotpath-meta
cargo check -p hotpath-meta --features hotpath-meta
cargo check -p hotpath-macros-meta --features hotpath-meta
cargo check -p hotpath-meta --features hotpath-meta,hotpath-alloc-meta
cargo check -p hotpath-meta --features hotpath-meta,hotpath-alloc-meta,hotpath-prometheus-meta

The no-feature check covers the lib_off path. Every *-meta sub-feature (hotpath-alloc-meta, hotpath-cpu-meta, hotpath-cloud-meta, hotpath-prometheus-meta, hotpath-mcp-meta) requires hotpath-meta and hits a compile_error! on its own, so always combine them with hotpath-meta. Add hotpath-cloud-meta / hotpath-mcp-meta / hotpath-cpu-meta to the last command when the synced files touch those subsystems.

  1. Report a summary of what was synced.

Rules

  • Only sync src/ files, never Cargo.toml or other config files. examples/ and tests/ (including the miri test in hotpath-drain) are not mirrored either.
  • If no changes were made to the source crates in the specified commits, report that and exit.
  • NEVER copy entire files and do bulk find-and-replace. Always apply diffs to existing meta files.
  • Preserve ALL meta-specific naming conventions (feature flags, env vars, crate names, self-instrumentation removal).
  • Lines with #[cfg_attr(feature = "hotpath-meta", hotpath_meta::...)] in hotpath are self-instrumentation and must NOT be copied to meta crates.
  • The meta feature flags are hotpath-meta, hotpath-alloc-meta, hotpath-cpu-meta, hotpath-cloud-meta, hotpath-prometheus-meta, hotpath-mcp-meta (NOT hotpath, hotpath-alloc, ...). There is no hotpath-off-meta; the disabled path is the no-feature build.

Frequently asked questions

What does the Syncmeta AI skill do?

Sync changes from the hotpath, hotpath-macros and hotpath-drain crates to their meta counterparts (hotpath-meta, hotpath-macros-meta and hotpath-drain-meta). Use when meta crates need to be updated with recent changes.

Why use Syncmeta on TypingMind?

Because you install it once and use it with any model. Syncmeta is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Syncmeta in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/pawurb/hotpath-rs/tree/main/skills/syncmeta. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Syncmeta?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Syncmeta?

As many as you like. As long as a model supports skills, you can use Syncmeta with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Syncmeta AI skill free?

Yes. It is published on GitHub by pawurb under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇