Agent skill

Linear Context Handover

by langfuse in langfuse/langfuse

Use Linear as the org's memory: reconstruct a feature's history before touching it, and leave the reasoning behind finished work in the ticket description so the next agent inherits it.

Custom licenceAuto-check passedAI & LLM Engineering

Install Linear Context Handover

skills CLI
$ npx skills add langfuse/langfuse --skill linear-context-handover -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install langfuse/langfuse linear-context-handover --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/linear-context-handover .claude/skills/linear-context-handover && rm -rf skills-src

Use ~/.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/

Facts

Skill name
linear-context-handover
GitHub stars
35k
Token cost
~1.7k tokens
SKILL.md length
968 words
Files
4 (incl. scripts, references)
Skills in repo
33
Repo updated
First seen
Licence
Custom licence

At a glance

Use Linear as the org's memory: reconstruct a feature's history before touching it, and leave the reasoning behind finished work in the ticket description so the next agent inherits it.

  • Works in 2 steps: Before you touch a feature, reconstruct… → When you wrap up, propose the handover…
  • Starting work on an existing feature
  • SKILL.md covers Before you touch a feature:…, When you wrap up: ask, then…, The labels, and the one note… and No Linear access
  • Runs Shell scripts from its folder; calls bash, git and gh; needs LINEAR_API_KEY

What it does

Linear Context Handover is an agent skill from langfuse/langfuse. Use Linear as the org's memory: reconstruct a feature's history before touching it, and leave the reasoning behind finished work in the ticket description so the next agent inherits it. Use when starting work on an existing feature, when splitting a large change, and always when wrapping up — "what happened to this screen before", "write the handover", "why is this code like this".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/handover-template.md` and `scripts/lf-context.sh`).

It sits in AI & LLM Engineering. The repository describes itself as: 🪢 Open source agent evals & observability: Trace, evaluate, and improve LLM applications with one open platform.

When your agent uses it

  • Starting work on an existing feature
  • Splitting a large change
  • Always when wrapping up — what happened to this screen before
  • Write the handover

Example prompts

  • “s memory: reconstruct a feature”
  • “what happened to this screen before”
  • “write the handover”
  • “/linear-context-handover”

Requirements

  • A Bash shell
  • A credential in LINEAR_API_KEY

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Before you touch a feature, reconstruct its history. Most "new" work on an
  2. When you wrap up, propose the handover for the ticket's description.

What it can do on your machine

Read from SKILL.md and the folder at commit 8b58764. 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

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash
    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • LINEAR_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Linear Context Handover loads about 1.7k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 968 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

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); the scripts in this folder 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 968 words (~1,710 tokens).

“Linear is the org's long-term memory. Agent sessions are not — they end, and everything they worked out ends with them. This skill is how reasoning survives the session that produced it.”

— opening of SKILL.md by langfuse, Custom licence
name
linear-context-handover

Read the full SKILL.md on GitHub

Files

SKILL.md and 3 other files (scripts, references) in .agents/skills/linear-context-handover of langfuse/langfuse.

  • SKILL.md
  • agents/openai.yaml
  • references/handover-template.md
  • scripts/lf-context.sh

Open the folder on GitHubat commit 8b58764

Compare with similar skills

Linear Context Handover 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.

Linear Context Handover compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linear Context Handover this skilllangfuse/langfuse35k—~1.7kAutomated safety check: PassCustom licence
Agent BuildershareAI-lab/learn-claude-code78k6 repos~1.2kAutomated safety check: PassMIT
Add Uint Supportpytorch/pytorch104k2 repos~2.3kAutomated safety check: PassCustom licence
Peft Fine TuningOrchestra-Research/AI-Research-SKILLs13k9 repos~3.1kAutomated safety check: PassMIT
Segment Anything Model GuideOrchestra-Research/AI-Research-SKILLs13k9 repos~3.3kAutomated safety check: PassMIT
1passwordtrpc-group/trpc-agent-go1.8k13 repos~656Automated safety check: PassApache-2.0

Similar skills

  • Agent Builder

    shareAI-lab/learn-claude-code

    Design and build AI agents for any domain. An agent skill from shareAI-lab/learn-claude-code.

    78k GitHub starsUsed in 6 repos~1.2k tokens
    AI & LLM EngineeringAuto-check passed
  • Add Uint Support

    pytorch/pytorch

    Add unsigned integer (uint) type support to PyTorch operators by updating ATDISPATCH macros.

    104k GitHub starsUsed in 2 repos~2.3k tokens
    AI & LLM EngineeringAuto-check passed
  • Peft Fine Tuning

    Orchestra-Research/AI-Research-SKILLs

    Parameter-efficient fine-tuning for LLMs using LoRA, QLoRA, and 25+ methods.

    13k GitHub starsUsed in 9 repos~3.1k tokens
    AI & LLM EngineeringAuto-check passed
  • Segment Anything Model Guide

    Orchestra-Research/AI-Research-SKILLs

    Guide to using Meta's Segment Anything Model for zero-shot image segmentation with point, box or mask prompts, or automatic mask generation.

    13k GitHub starsUsed in 9 repos~3.3k tokens
    AI & LLM EngineeringAuto-check passed
  • 1password

    trpc-group/trpc-agent-go

    Set up and use 1Password CLI (op). An agent skill from trpc-group/trpc-agent-go.

    1.8k GitHub starsUsed in 13 repos~656 tokens
    AI & LLM EngineeringAuto-check passed
  • Chroma Vector Database

    Orchestra-Research/AI-Research-SKILLs

    Shows how to store documents and embeddings in Chroma, query them by similarity with metadata filters, and persist them to disk for RAG and semantic search projects.

    13k GitHub starsUsed in 8 repos~2.3k tokens
    AI & LLM EngineeringAuto-check passed

More from langfuse/langfuse

All 33 skills in this repo
  • Add Model Price

    langfuse/langfuse

    A skill your agent uses when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/types.ts, pricing tiers, tokenizer IDs, or matchPattern regexes for OpenAI…

    35k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Backend Dev Guidelines

    langfuse/langfuse

    Build or review Langfuse backend code. An agent skill from langfuse/langfuse.

    35k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Navigate Langfuse repositories, code areas, and agent skills.

    35k GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Refactor React Effects

    langfuse/langfuse

    Refactor avoidable React useEffect usage in Langfuse frontend code.

    35k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Add To Dependabot CSV

    langfuse/langfuse

    Append GitHub Dependabot or Snyk/code-scanning alerts to an existing vulnerability CSV after verifying their API metadata.

    35k GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Clickhouse Best Practices

    langfuse/langfuse

    MUST USE when reviewing ClickHouse schemas, queries, or configurations.

    35k GitHub stars~3.5k tokensUpdated today
    Auto-check passed

Questions about Linear Context Handover

What does Linear Context Handover do?

Use Linear as the org's memory: reconstruct a feature's history before touching it, and leave the reasoning behind finished work in the ticket description so the next agent inherits it. Linear Context Handover is an agent skill from langfuse/langfuse. Use Linear as the org's memory: reconstruct a feature's history before touching it, and leave the reasoning behind finished work in the ticket description so the next agent inherits it.

When should I use Linear Context Handover?

Linear Context Handover fits situations like: starting work on an existing feature; splitting a large change; always when wrapping up — what happened to this screen before; write the handover.

How do I install Linear Context Handover in Claude Code?

Run `npx skills add langfuse/langfuse --skill linear-context-handover -a claude-code`. Or copy the skill folder (.agents/skills/linear-context-handover in langfuse/langfuse) into .claude/skills/linear-context-handover in your project. Claude Code loads it when a task matches its description.

How do I install Linear Context Handover in Codex?

Run `npx skills add langfuse/langfuse --skill linear-context-handover -a codex`. Or copy the skill folder (.agents/skills/linear-context-handover in langfuse/langfuse) into .agents/skills/linear-context-handover in your project. Codex loads it when a task matches its description.

Can I use Linear Context Handover 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 langfuse/langfuse --skill linear-context-handover -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linear-context-handover, .gemini/skills/linear-context-handover, .github/skills/linear-context-handover and .opencode/skills/linear-context-handover in your project.

What does Linear Context Handover need to run?

Going by SKILL.md and its folder, Linear Context Handover needs a shell for the scripts in its folder, the command-line tools its instructions call (bash, git and gh) and credentials named LINEAR_API_KEY. Our summary lists: A Bash shell; A credential in LINEAR_API_KEY.

Does Linear Context Handover access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Linear Context Handover 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Linear Context Handover use?

Linear Context Handover 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 Linear Context Handover use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 592 tokens, read only when the agent opens those files.

What are the alternatives to Linear Context Handover?

Skills that share tags, products or a category with Linear Context Handover: Agent Builder (shareAI-lab/learn-claude-code, 78k stars), Add Uint Support (pytorch/pytorch, 104k stars), Peft Fine Tuning (Orchestra-Research/AI-Research-SKILLs, 13k stars) and Segment Anything Model Guide (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linear Context Handover?

langfuse (a GitHub organization) maintains it in langfuse/langfuse, which has 35,460 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.

Source: langfuse/langfuse on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.