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
Apple/Cocoa 프로젝트를 위한 전체 Sentry Snapshots 설정입니다. "SnapshotPreviews 설정", "Apple 스냅샷 테스트 설정", "Apple 스냅샷 업로드" 요청 시 사용하세요.
official
architecture-review
sentry
직원 수준의 코드베이스 건강 검토. 모놀리식 모듈, 무음 실패, 타입 안전성 격차, 테스트 커버리지 구멍, LLM 친화성 문제를 찾습니다.
official
linear-type-labeler
sentry
Linear 이슈를 분류하고, 각 이슈의 제목과 설명 내용을 기반으로 Sentry 워크스페이스의 레이블 분류 체계에서 Type 레이블을 적용합니다.
official
sentry-flutter-sdk
sentry
Flutter 및 Dart를 위한 완전한 Sentry SDK 설정입니다. "Flutter에 Sentry 추가", "sentry_flutter 설치", "Dart에서 Sentry 설정" 또는 오류 구성을 요청받았을 때 사용하세요.
official
sentry-svelte-sdk
sentry
Svelte 및 SvelteKit을 위한 완전한 Sentry SDK 설정입니다. "Svelte에 Sentry 추가", "SvelteKit에 Sentry 추가", "@sentry/sveltekit 설치" 또는 구성 요청 시 사용하세요.
official
vercel-react-best-practices
sentry
Vercel Engineering의 React 및 Next.js 성능 최적화 가이드라인입니다. 이 스킬은 React/Next.js 코드를 작성, 검토 또는 리팩토링할 때 사용해야 합니다.
official
sentry-tanstack-start-sdk
sentry
TanStack Start React용 전체 Sentry SDK 설정. "TanStack Start에 Sentry 추가", "@sentry/tanstackstart-react 설치" 또는 오류 구성 요청 시 사용…
official