npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@lmzhen/dsh-evolution-learning-graph

v0.3.74

Published

Learning graph over skills and memory (community build)

Readme

@deepseek-ai/dsh-evolution-learning-graph

Learning graph over skills and memory

Graph surface

/graph renders the learning graph. A skill node is its name; a memory node is memory:<source>:<index>, where <source> is memory|user and <index> is the position in that file's entries.

Memory node ids carry a trailing snapshot token (memory:<source>:<index>:<snapshot> — an 8-hex digest of the node label's first line). It exists so graph edit/graph delete can detect index drift: any memory write between the last render and the command shifts indices, and a stale id is rejected (requiring a re-run of /graph) instead of mutating a different entry.

Memory→skill edges are word-level, not substring: the entry is tokenized on non-letter/digit/hyphen runs and a skill name links only when it is a whole token. This prevents a skill named run from linking the words running/grunt.

graph edit/graph delete route through the evolution approval seam when it is mounted (soft-probed; the write executes directly when it is absent) — for BOTH skill nodes and memory nodes (P2-6, v15; memory staged args mirror the memory tool runner's replay shape). Before staging, the seam's hasRunner is checked (P2-7, v15): with approval enabled, a session policy that is not never, and the write actually staging (foreground stages per approval stageForeground; subagent origins always stage), a missing replay runner's row (tool-skill-manage / tool-memory) refuses the write; allow-direct combinations execute unchanged instead of creating a pending record no approver could replay. Each approved/executed edit bumps the skill's patch counter and a delete archives it, matching skill_manage — including the no-op gate: an edit whose content is byte-equivalent to the current file (noop) writes nothing and does not bump the patch counter, exactly as skill_manage treats an unchanged update/patch. The command invocation's session rides the approval request (v12 N1), so a never-policy session stages nothing instead of deriving every graph write as foreground.

Model Experience

Indirect model surface

@deepseek-ai/dsh-evolution-learning-graph registers no direct prompt or tool schema itself. Model-visible effects are owned by the packages that consume this service.

Token effect

Zero direct token effect from this package; consumers add any model-visible tokens.

KV Cache effect

Independent of request-prefix construction. This package does not alter the assembled prompt or tool list.

Known Limitations and Deferred Work

  • The memory drift snapshot covers only the node label (first line, first 80 chars): a change confined to a later line of the same entry is not detected, because the rendered node label is the comparison anchor.
  • A hand-typed bare memory:<source>:<index> id has no snapshot and skips the drift check (legacy path; the rendered ids always carry the snapshot).