What one of us figures out, all of us get.

LyraLink turns the agent skills and workflows you build at a client into something every Lyra engineer can install. Client code stays at the client.

Get startedTry the redactor

Your best workflow shouldn't roll off with you.

The auth scripts, typecheck wrappers and QA runners that make someone fast at a client live in their home directory, and leave when they do. Five commands get them to the next person.

~/client-repoyour machine
# Reads your Claude Code and Codex transcripts on your machine and turns them into session records.$ lyralink scan1,084 sessions from 51 projects in 41s tasksessionsprstok/merged prloopsmigration142611.9M12feature3881742.4M31bugfix2011190.8M18review-qa96401.1M4 14 practice card drafts ready

See exactly what crosses.

This half is client land. Edit the prompt or the denylist and the real LyraLink redactor rewrites the other half as you type.

Who sees it
You, and everyone on that client's roster
What's in it
Raw transcripts, paths, PR links, real skill contents, harness configs
Lives in
Your machine and an engagement store the client's engineers already use

What the rest of Lyra sees

Picking up [ticket] for [client]. Migrate [ident] in [path] to the new Dialog, same approach [client] used in [url] Branch is [branch] Do it one slice at a time in a worktree and run [code] between slices, never the root tsc.

  • Stripped
  • 2 names
  • 1 paths
  • 1 links
  • 1 tickets
  • 1 code
  • 1 identifiers
  • 1 branches
Who sees it
Every Lyra engineer
What's in it
Practice cards and stripped skills. No code, paths, client names or identifiers
Lives in
The org registry, in separate storage from anything client-side

Then it's everyone's.

Once something crosses, the rest of Lyra can find it, install it and get nudged toward it when they need it.

  • Skills

    Claude Code skills, codemods, hooks, agent configs and harness scripts, versioned with a manifest that says where they install.

    lyralink install pr-writeup

  • Practice cards

    How someone approached a kind of task, what it cost and how it turned out, abstracted from their own sessions.

    lyralink cards

  • Nudges

    Running the same command by hand every session, or stuck in a loop a teammate already solved? You get pointed at the fix.

    lyralink nudge

  • Starter packs

    Day one on a client, install the whole team's harness in one go instead of rebuilding it from Slack threads.

    lyralink install --engagement acme

  • Your dashboard

    Tokens per merged PR, cache hit ratio, loops and session shape. Private to you, exportable as promotion evidence.

    lyralink export --evidence

Learn from each other, not about each other.

  • Nothing uploads silently

    Every card, skill, Feed post and decision waits for your approval. Session projections and the config snapshot upload counts and names only. lyralink pause stops both.

  • Your numbers are yours

    Personal metrics are private by default. Sharing them is opt-in.

  • Three people or it doesn't show

    Org-wide numbers need at least three engineers in a bucket, so nothing traces back to one person.

  • No leaderboard, ever

    Org views compare practices and task types. They never rank people.