dotagents

作者: sentry

使用 dotagents 管理代理技能依賴。當被要求「新增技能」、「安裝技能」、「移除技能」、「dotagents init」、「agents.toml」…時使用。

npx skills add https://github.com/getsentry/dotagents --skill dotagents

dotagents Skill Management

Use dotagents as the skill dependency manager. Do not copy managed skills into individual agent directories.

Choose the scope first

  1. Use project scope when the repository has agents.toml or the user ties the dependency to the repository or team.
  2. Translate “global,” “personal,” or “for every project” into dotagents --user scope.
  3. Do not add --user to a general request made in a configured project.
  4. If a Git repository has no agents.toml, initialize the project before adding dependencies.
  5. Do not initialize user scope separately; user commands create ~/.agents/agents.toml automatically.
# Initialize an unconfigured project
npx --yes @sentry/dotagents@latest init

# Personal user scope bootstraps on first use
npx --yes @sentry/dotagents@latest --user add getsentry/skills find-bugs

Interactive init asks which agent tools and trust policy to configure. If those choices require user input, present the command instead of inventing answers.

Add skills through dotagents

add updates agents.toml and runs install immediately. Do not run a redundant install afterward.

# Project dependency
npx --yes @sentry/dotagents@latest add getsentry/skills find-bugs

# Several skills from one source
npx --yes @sentry/dotagents@latest add getsentry/skills find-bugs commit pr-writer

# Explicit personal/global skill
npx --yes @sentry/dotagents@latest --user add getsentry/skills find-bugs

# Track every current and future skill from a source
npx --yes @sentry/dotagents@latest add dcramer/agents --all

# Pin a tag, branch, or commit
npx --yes @sentry/dotagents@latest add getsentry/warden --ref v1.0.0

If a source contains multiple skills, pass explicit names or --all; do not depend on an interactive picker in an agent workflow.

Supported sources include GitHub/GitLab repositories, explicit Git URLs, well-known HTTPS catalogs, and project-relative path: sources. Read references/configuration.md when choosing source syntax.

Edit configuration only for advanced options

Prefer add, remove, mcp, and trust commands for normal mutations. Edit agents.toml directly for fields the CLI does not expose, then run install.

Example: use a named skill stored outside standard discovery directories.

[[skills]]
name = "review"
source = "acme/agent-skills"
path = "plugins/core/skills/review"
npx --yes @sentry/dotagents@latest install

Read references/config-schema.md for exact fields used by skills, hooks, subagents, MCP servers, trust, and agent targets.

Choose the correct lifecycle command

  • add: declare and immediately install new skills.
  • install: fetch or refresh dependencies from agents.toml, prune stale managed skills, and regenerate runtime configuration.
  • sync: repair local state without fetching remote dependency updates.
  • list: inspect declared and wildcard-expanded skill status; use --json when structured output helps.
  • doctor: diagnose configuration and generated-state problems; use --fix only for supported repairs.

There is no update command. Use install when the user asks to update skills.

npx --yes @sentry/dotagents@latest install
npx --yes @sentry/dotagents@latest sync
npx --yes @sentry/dotagents@latest list --json
npx --yes @sentry/dotagents@latest doctor

Remove skills through dotagents

npx --yes @sentry/dotagents@latest remove find-bugs

If the skill comes from a wildcard, use the offered exclusion flow so future installs do not restore it. Use -y only when the user has clearly approved the removal. Never delete .agents/skills/<name> or edit agents.lock manually.

Respect trust policy

When a source is rejected, explain the required trust rule. Add it only with user approval.

npx --yes @sentry/dotagents@latest trust add getsentry
npx --yes @sentry/dotagents@latest trust add external-org/specific-repo
npx --yes @sentry/dotagents@latest trust add git.corp.example.com

Never switch to allow_all = true merely to bypass an error.

Discover syntax without side effects

Use help output before unfamiliar commands. Help must not execute command behavior.

npx --yes @sentry/dotagents@latest add --help
npx --yes @sentry/dotagents@latest mcp add --help
npx --yes @sentry/dotagents@latest trust list --help

Read references/cli-reference.md for the full command surface.

Never do these

  • Never manually copy managed skills into .claude/skills, .cursor/skills, .codex/skills, or similar runtime directories.
  • Never manually edit agents.lock or generated agent configuration.
  • Never describe sync as fetching or updating remote skills.
  • Never add trust rules or weaken trust without explicit user intent.

來自 sentry 的更多技能

generate-frontend-forms
sentry
使用 Sentry 新表單系統建立表單的指南。適用於實作表單、表單欄位、驗證或自動儲存功能時使用。
official
sentry-snapshots-cocoa
sentry
完整的 Sentry Snapshots 設定,適用於 Apple/Cocoa 專案。當被要求「設定 SnapshotPreviews」、「設定 Apple 快照測試」、「上傳 Apple 快照至…」時使用。
official
architecture-review
sentry
員工級別的程式碼庫健康檢查。找出單體模組、靜默失敗、型別安全漏洞、測試覆蓋缺口,以及LLM友善性問題。
official
linear-type-labeler
sentry
根據每個問題的標題與描述內容,從 Sentry 工作區的標籤分類法中分類 Linear 問題,並套用對應的類型標籤。
official
sentry-flutter-sdk
sentry
完整的 Sentry SDK 設定,適用於 Flutter 和 Dart。當被要求「為 Flutter 加入 Sentry」、「安裝 sentry_flutter」、「在 Dart 中設定 Sentry」或設定錯誤…時使用。
official
sentry-svelte-sdk
sentry
完整的 Sentry SDK 設定,適用於 Svelte 和 SvelteKit。當被要求「將 Sentry 加入 Svelte」、「將 Sentry 加入 SvelteKit」、「安裝 @sentry/sveltekit」或進行設定時使用…
official
vercel-react-best-practices
sentry
來自 Vercel Engineering 的 React 與 Next.js 效能優化指南。此技能應在撰寫、審查或重構 React/Next.js… 時使用。
official
sentry-tanstack-start-sdk
sentry
完整的 Sentry SDK 設定,適用於 TanStack Start React。當被要求「將 Sentry 加入 TanStack Start」、「安裝 @sentry/tanstackstart-react」或設定錯誤…時使用。
official