Skip to content
Skills Library
AI & agents · Building & coding

agent-setup-maintenance

/agent-setup-maintenance

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.

Repository
langfuse ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

  1. Start Here
  2. Workflow
  3. Docker / Install-Time Constraint
  4. Required Verification
  5. Design Rules
Original SKILL.md headings · 66 lines, 372 words
SKILL.md preview
---
name: agent-setup-maintenance
description: |
  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.
---

# Agent Setup Maintenance

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

## Start Here

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

## Workflow

1. Edit the canonical files under `.agents/`, not generated provider outputs.
2. Keep root `AGENTS.md` as a symlink to `.agents/AGENTS.md`. Write folder
   instructions in `AGENTS.md` directly; do not generate `CLAUDE.md` companions.
3. 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.
4. Keep root `AGENTS.md` concise. Move detailed or conditional workflows into
   shared skills or package `AGENTS.md` files.
5. 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.
6. When adding or changing a shared skill, keep `SKILL.md` as the entrypoint; do
   not add skill-by-skill links to root `AGENTS.md`.
7. 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.

Versions

The database has no other skills named agent-setup-maintenance.

Database snapshot: 13.11.2026 · package version 1178f7b0dca6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90writing-for-agents
    Use when creating or editing skills, or modifying AGENTS.md or other agent instruction files.
  • 85workflow-writing-for-agents
    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
  • 100init-agent-config
    Use if creating, auditing, or migrating CLAUDE.md/AGENTS.md/REVIEW.md instruction files.
  • 100create-repo-agent
    Design, implement, review, or harden Langfuse repo-owned autonomous agents. Use for LLM-powered GitHub Actions, scheduled or dispatched agents, agent-created PRs, prompts, allowlists, tokens, untrusted content, or self-updating instructions.
  • 100guidance-maintenance
    Use when changing the agent guidance layer, meaning AGENTS.md or anything under .agents (guardrails, rules, agents, skills, commands, workflows, policy, hooks, areas.json), the knowledge graph, or the retrieval evals. Covers adding, renaming or removing a guardrail, rule, skill…
  • 90writing-for-agents
    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.