agent-setup-maintenance

AI Community

Repo stars 27,778
Author repo langfuse

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: | Use this skill when changing the shared agent setup for the repository. ../skill-creator/SKILL.md, then apply the repo-specifi…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Start Here”, “Workflow”, “Docker / Install-Time Constraint”, “Required Verification”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name agent-setup-maintenance directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Start Here / Workflow / Docker / Install-Time Constraint” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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 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 and router-like. 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, update skills/README.md and link it from root AGENTS.md if it changes the default reusable workflow.
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

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.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: AI
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @langfuse · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Docker
Runtime requirements: Docker
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview agent-setup-maintenance.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# 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` and `CLAUDE.md` as discovery symlinks; do not turn
   them back into manually maintained copies.
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 and router-like. 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, update `skills/README.md` and link
   it from root `AGENTS.md` if it changes the default reusable workflow.
7. When shared setup behavior changes materially, update `README.md` and

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Start Here → Workflow → Docker / Install-Time Constraint → Required Verification → Design Rules
terms    -> Use this skill when changing the shared agent setup for the repository. · - Read [../../README.md](../../README.md) for the shared config and shim model. · 1. Edit the canonical files under .agents/, not generated provider outputs. · - pnpm install runs in environments that may not contain the full repo source tree. · - Prefer one repo-owned source of truth over duplicated provider-specific files.
files/cmd -> ../../README.md · ../../AGENTS.md · ../skill-creator/SKILL.md · ../../../scripts/agents/sync-agent-shims.mjs · ../../../scripts/postinstall.sh · ../../../package.json · .agents/ · AGENTS.md
body sha256 -> 42dfba56043c