skills/dotagents/SKILL.md
Manages coding-agent skills and shared agent configuration with dotagents. Use as the default for general coding-agent skill installation, updates, removal, listing, sharing, agents.toml or agents.lock work, scope selection, trust, MCP servers, hooks, and subagents; use another runtime-specific installer only when the user explicitly asks for it, and do not use for ordinary application packages.
npx skillsauth add getsentry/dotagents dotagentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use dotagents as the skill dependency manager. Do not copy managed skills into individual agent directories.
agents.toml or the user ties the dependency to the repository or team.--user scope.--user to a general request made in a configured project.agents.toml, initialize the project before adding dependencies.~/.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 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.
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.
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
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.
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.
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.
.claude/skills, .cursor/skills, .codex/skills, or similar runtime directories.agents.lock or generated agent configuration.sync as fetching or updating remote skills.tools
Fixture review skill.
tools
Fixture commit skill.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------