Agent skill

Backend Dev Guidelines

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

Custom licenceAuto-check passedBackend & APIs

Install Backend Dev Guidelines

skills CLI

$ npx skills add langfuse/langfuse --skill backend-dev-guidelines -a claude-code

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

GitHub CLI

$ gh skill install langfuse/langfuse backend-dev-guidelines --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/backend-dev-guidelines .claude/skills/backend-dev-guidelines && 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/

Paste into Claude Code

Install the "backend-dev-guidelines" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/backend-dev-guidelines into .claude/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", 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

$skill-installer install https://github.com/langfuse/langfuse/tree/main/.agents/skills/backend-dev-guidelines

Type 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.

skills CLI

$ npx skills add langfuse/langfuse --skill backend-dev-guidelines -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install langfuse/langfuse backend-dev-guidelines --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/backend-dev-guidelines .agents/skills/backend-dev-guidelines && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "backend-dev-guidelines" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/backend-dev-guidelines into .agents/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", 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.

skills CLI

$ npx skills add langfuse/langfuse --skill backend-dev-guidelines -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install langfuse/langfuse backend-dev-guidelines --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/backend-dev-guidelines .cursor/skills/backend-dev-guidelines && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "backend-dev-guidelines" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/backend-dev-guidelines into .cursor/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", 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

$ gemini skills install https://github.com/langfuse/langfuse.git --path .agents/skills/backend-dev-guidelines

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add langfuse/langfuse --skill backend-dev-guidelines -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install langfuse/langfuse backend-dev-guidelines --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/backend-dev-guidelines .gemini/skills/backend-dev-guidelines && rm -rf skills-src

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

Paste into Gemini CLI

Install the "backend-dev-guidelines" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/backend-dev-guidelines into .gemini/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", 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.

GitHub CLI

$ gh skill install langfuse/langfuse backend-dev-guidelines

Installs 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).

skills CLI

$ npx skills add langfuse/langfuse --skill backend-dev-guidelines -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/backend-dev-guidelines .github/skills/backend-dev-guidelines && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "backend-dev-guidelines" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/backend-dev-guidelines into .github/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", 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.

skills CLI

$ npx skills add langfuse/langfuse --skill backend-dev-guidelines -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install langfuse/langfuse backend-dev-guidelines --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/langfuse/langfuse.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/backend-dev-guidelines .opencode/skills/backend-dev-guidelines && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "backend-dev-guidelines" agent skill from https://github.com/langfuse/langfuse/tree/main/.agents/skills/backend-dev-guidelines into .opencode/skills/backend-dev-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-dev-guidelines", 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: backend-dev-guidelines
GitHub stars: 35k
Token cost: ~1.9k tokens
SKILL.md length: 786 words
Files: 9 (incl. references)
Skills in repo: 33
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Custom licence

At a glance

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

Public REST APIs
SKILL.md covers When to Apply, How to Read This Skill, Before Adding a New Concept and Quick Start Checklists, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
BullMQ processors

What it does

Backend Dev Guidelines is an agent skill from langfuse/langfuse. Build or review Langfuse backend code. Use for tRPC routers, public REST APIs, BullMQ processors, services, middleware, Prisma or ClickHouse access, OpenTelemetry, Zod, environment configuration, or backend tests.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `references/architecture-overview.md`, `references/configuration.md` and `references/database-patterns.md`).

It sits in Backend & APIs, covering REST APIs, gRPC and Protobuf and Observability. It works with Langfuse, tRPC, ClickHouse and Prisma. 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

Public REST APIs
BullMQ processors
ClickHouse access
Environment configuration

Example prompts

“/backend-dev-guidelines”

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
No scripts in the folder and no shell commands in SKILL.md.
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

Backend Dev Guidelines loads about 1.9k tokens when it runs, and up to ~39k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 786 words of instructions outside code blocks.

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

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 786 words (~1,900 tokens).

“Use this skill for backend and API work across web/, worker/, and packages/shared/.”

— opening of SKILL.md by langfuse, Custom licence

name: backend-dev-guidelines

Read the full SKILL.md on GitHub

Files

SKILL.md and 8 other files (references) in .agents/skills/backend-dev-guidelines of langfuse/langfuse.

SKILL.md
references/architecture-overview.md
references/configuration.md
references/database-patterns.md
references/middleware-guide.md
references/new-concepts.md
references/routing-and-controllers.md
references/services-and-repositories.md
references/testing-guide.md

Open the folder on GitHubat commit 8b58764

Compare with similar skills

Backend Dev Guidelines 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.

Backend Dev Guidelines compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Backend Dev Guidelines this skilllangfuse/langfuse	35k	—	~1.9k	Automated safety check: Pass	Custom licence	today
Backend Dev Guidelineslitefuse/litefuse	100	1 repos	~5.8k	Automated safety check: Pass	Custom licence	14 days ago
Cross Package Typesbitovi/ai-enablement-prompts	121	—	~1.1k	Automated safety check: Pass	MIT	26 days ago
Nestjs Trpctrycompai/crm	11k	—	~2.8k	Automated safety check: Pass	MIT	26 days ago
Trpcpproenca/dot-skills	214	—	~2.8k	Automated safety check: Pass	MIT	1 mo ago
Agentsop Observability Setupagentsope/SkillAlchemy	457	—	~4.4k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Backend Dev Guidelines
litefuse/litefuse
Comprehensive backend development guide for Litefuse's Next.js 14/tRPC/Express/TypeScript monorepo.
100 GitHub starsUsed in 1 repo~5.8k tokens
Backend & APIsAuto-check passed
Cross Package Types
bitovi/ai-enablement-prompts
Type flow patterns for tRPC + Prisma monorepos. An agent skill from bitovi/ai-enablement-prompts.
121 GitHub stars~1.1k tokensUpdated 26 days ago
DatabasesAuto-check passed
Nestjs Trpc
trycompai/crm
Build end-to-end type-safe tRPC APIs inside NestJS using the nestjs-trpc adapter — @Router/@Query/@Mutation/@Subscription decorators, TRPCModule.forRoot, injectable middlewares and context, Zod…
11k GitHub stars~2.8k tokensUpdated 26 days ago
Backend & APIsAuto-check passed
Trpc
pproenca/dot-skills
Corrects the wrong defaults a model has for tRPC v11 (verified against 11.18.0).
214 GitHub stars~2.8k tokensUpdated 1 mo ago
Backend & APIsAuto-check passed
Agentsop Observability Setup
agentsope/SkillAlchemy
Enhancement-overlay skill — the DECISION + WIRING layer for LM observability that the single-backend skills [[langsmith]], [[phoenix]], [[mlflow]] do NOT cover.
457 GitHub stars~4.4k tokensUpdated 1 mo ago
AI & LLM EngineeringAuto-check passed
Ag2 Telemetry
ag2ai/build-with-ag2
Add OpenTelemetry traces to an AG2 beta Agent via TelemetryMiddleware (autogen.beta.middleware.builtin).
252 GitHub stars~1.9k tokensUpdated 1 mo ago
DevOps & CloudAuto-check passed

Questions about Backend Dev Guidelines

What does Backend Dev Guidelines do?

Build or review Langfuse backend code. An agent skill from langfuse/langfuse. Backend Dev Guidelines is an agent skill from langfuse/langfuse. Build or review Langfuse backend code.

When should I use Backend Dev Guidelines?

Backend Dev Guidelines fits situations like: public REST APIs; bullMQ processors; clickHouse access; environment configuration.

How do I install Backend Dev Guidelines in Claude Code?

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

How do I install Backend Dev Guidelines in Codex?

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

Can I use Backend Dev Guidelines 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 backend-dev-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/backend-dev-guidelines, .gemini/skills/backend-dev-guidelines, .github/skills/backend-dev-guidelines and .opencode/skills/backend-dev-guidelines in your project.

What does Backend Dev Guidelines need to run?

SKILL.md names no scripts, command-line tools or credentials: Backend Dev Guidelines is instructions for the agent only.

Does Backend Dev Guidelines 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 Backend Dev Guidelines 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 Backend Dev Guidelines use?

Backend Dev Guidelines 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 Backend Dev Guidelines use?

About 1.9k tokens (SKILL.md is roughly 7.6k 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 37k tokens, read only when the agent opens those files.

What are the alternatives to Backend Dev Guidelines?

Skills that share tags, products or a category with Backend Dev Guidelines: Backend Dev Guidelines (litefuse/litefuse, 100 stars), Cross Package Types (bitovi/ai-enablement-prompts, 121 stars), Nestjs Trpc (trycompai/crm, 11k stars) and Trpc (pproenca/dot-skills, 214 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Backend Dev Guidelines?

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.

Backend Dev Guidelines

Install Backend Dev Guidelines

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills