agent-setup-maintenance

Q: How do I install agent-setup-maintenance?

Run npx skills add https://github.com/langfuse/langfuse --skill agent-setup-maintenance in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/agent-setup-maintenance/ (personal) or .claude/skills/agent-setup-maintenance/ (project).

by langfuse OfficialProductivity & Automation

Shared workflow for editing Langfuse's repo-owned agent setup under .agents/. Use when changing AGENTS files, shared skills, .agents/config.json, generated shim behavior, provider discovery paths, or install-time agent sync.

Installs: 42
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/langfuse/langfuse --skill agent-setup-maintenance

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads agent-setup-maintenance automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Agent Setup Maintenance

Use this skill when changing the shared agent setup for the repository.

Start Here

Read ../../README.md for the shared config and shim model.
Read root ../../AGENTS.md for repo-level expectations.
When adding or editing shared skills, use ../skill-creator/SKILL.md, then apply the repo-specific checks in this skill.
Inspect ../../../scripts/agents/sync-agent-shims.mjs before changing generated outputs or provider discovery behavior.
Inspect ../../../scripts/postinstall.sh and ../../../package.json when changing install-time sync behavior.

Workflow

Edit the canonical files under .agents/, not generated provider outputs.
Keep root AGENTS.md as a symlink to .agents/AGENTS.md. Write folder instructions in AGENTS.md directly; do not generate CLAUDE.md companions.
Treat tool-specific directories such as .claude/, .cursor/, .codex/, .vscode/, and .mcp.json as generated discovery surfaces unless the tool requires a truly tool-specific feature.
Keep root AGENTS.md concise. Move detailed or conditional workflows into shared skills or package AGENTS.md files.
Treat developer feedback as a learning loop: when a task reveals a durable repo convention, recurring pitfall, reusable workflow, or verification pattern, update the smallest relevant AGENTS.md or shared skill.
When adding or changing a shared skill, keep SKILL.md as the entrypoint; do not add skill-by-skill links to root AGENTS.md.
When shared setup behavior changes materially, update README.md and contributor-facing docs in the same PR.

Docker / Install-Time Constraint

pnpm install runs in environments that may not contain the full repo source tree.
In Docker builds, Turbo's pruned install stage can run root postinstall before scripts/ and .agents/ are available in the image.
Keep install-time agent setup logic robust in those pruned contexts: skip cleanly when the required repo-owned files are not present.

Required Verification

Run after changing shared agent setup:

pnpm run agents:sync
pnpm run agents:check
node --test scripts/agents/sync-agent-shims.test.mjs when sync behavior changes

Run additional verification when relevant:

pnpm run postinstall when install-time behavior changes
targeted tests for any scripts you changed

Design Rules

Prefer one repo-owned source of truth over duplicated provider-specific files.
Keep shared setup tool-neutral where possible.
Only keep provider-specific files in source control when the provider requires a fixed discovery path or feature that cannot be expressed through the shared setup model.

FAQ

What does the agent-setup-maintenance skill do?

How do I install agent-setup-maintenance?

Run npx skills add https://github.com/langfuse/langfuse --skill agent-setup-maintenance in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/agent-setup-maintenance/ (personal) or .claude/skills/agent-setup-maintenance/ (project).

Which AI agents can use agent-setup-maintenance?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is agent-setup-maintenance safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains agent-setup-maintenance?

It is published by langfuse in langfuse/langfuse, and it is an official skill from the maker of the technology it covers. It has 42 recorded installs.

More from langfuse/langfuse

View all →

backend-dev-guidelines

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.

OfficialBackend & APIs1.4K installs