Labsco
langfuse logo

agent-setup-maintenance

★ 30,400

by langfuse · part of langfuse/langfuse

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

🔥🔥✓ VerifiedFreeQuick setup
#automation#devops#git
🔒 Repo-maintenance skill. It exists to help maintain langfuse/langfuse itself — it's only useful if you contribute code to that project.

This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.

by langfuse

Use this skill when changing the shared agent setup for the repository. npx skills add https://github.com/langfuse/langfuse --skill agent-setup-maintenance Download ZIPGitHub30.4k

Start Here

Workflow

  • Edit the canonical files under .agents/, not generated provider outputs.

  • Keep root AGENTS.md and CLAUDE.md as discovery symlinks; do not turn them back into manually maintained copies.

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

Required Verification

Run after changing shared agent setup:

  • pnpm run agents:sync

  • pnpm run agents:check

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.