[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DPYYHS08PCAZH98G6B6BT1":3,"skill-same:01M7DPYYHS08PCAZH98G6B6BT1":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":46},"01M7DPYYHS08PCAZH98G6B6BT1","sentry-elixir-sdk",null,"Full Sentry SDK setup for Elixir. Use when asked to \"add Sentry to Elixir\", \"install sentry for Elixir\", or configure error monitoring, tracing, logging, or crons for Elixir, Phoenix, or Plug applications. Supports Phoenix, Plug, LiveView, Oban, and Quantum.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsentry-elixir-sdk\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sentry-elixir-sdk\ndescription: Full Sentry SDK setup for Elixir. Use when asked to \"add Sentry to Elixir\", \"install sentry for Elixir\", or configure error monitoring, tracing, logging, or crons for Elixir, Phoenix, or Plug applications. Supports Phoenix, Plug, LiveView, Oban, and Quantum.\nlicense: Apache-2.0\ncategory: sdk-setup\nparent: sentry-sdk-setup\ndisable-model-invocation: true\n---\n\n> [All Skills](..\u002F..\u002FSKILL_TREE.md) > [SDK Setup](..\u002Fsentry-sdk-setup\u002FSKILL.md) > Elixir SDK\n\n# Sentry Elixir SDK\n\nOpinionated wizard that scans your Elixir project and guides you through complete Sentry setup.\n\n## Invoke This Skill When\n\n- User asks to \"add Sentry to Elixir\" or \"set up Sentry\" in an Elixir or Phoenix app\n- User wants error monitoring, tracing, logging, or crons in Elixir or Phoenix\n- User mentions `sentry` hex package, `getsentry\u002Fsentry-elixir`, or Elixir Sentry SDK\n- User wants to monitor exceptions, Plug errors, LiveView errors, or scheduled jobs\n\n> **Note:** SDK versions and APIs below reflect Sentry docs at time of writing (sentry v13.2.0, requires Elixir ~> 1.13).\n> Always verify against [docs.sentry.io\u002Fplatforms\u002Felixir\u002F](https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Felixir\u002F) before implementing.\n\n---\n\n## Phase 1: Detect\n\nRun these commands to understand the project before making any recommendations:\n\n```bash\n# Check existing Sentry dependency\ngrep -i sentry mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect Elixir version\ncat .tool-versions 2>\u002Fdev\u002Fnull | grep elixir\ngrep \"elixir:\" mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect Phoenix or Plug\ngrep -E '\"phoenix\"|\"plug\"' mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect Phoenix LiveView\ngrep \"phoenix_live_view\" mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect Oban (job queue \u002F crons)\ngrep \"oban\" mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect Quantum (cron scheduler)\ngrep \"quantum\" mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect OpenTelemetry usage\ngrep \"opentelemetry\" mix.exs 2>\u002Fdev\u002Fnull\n\n# Check for companion frontend\nls assets\u002F frontend\u002F web\u002F client\u002F 2>\u002Fdev\u002Fnull\n```\n\n**What to note:**\n\n| Signal | Impact |\n|--------|--------|\n| `sentry` already in `mix.exs`? | Skip install; go to Phase 2 (configure features) |\n| Phoenix detected? | Add `Sentry.PlugCapture`, `Sentry.PlugContext`, optionally `Sentry.LiveViewHook` |\n| LiveView detected? | Add `Sentry.LiveViewHook` to the `live_view` macro in `my_app_web.ex` |\n| Oban detected? | Recommend Crons + error capture via Oban integration |\n| Quantum detected? | Recommend Crons via Quantum integration |\n| OpenTelemetry already present? | Tracing setup only needs `Sentry.OpenTelemetry.*` config |\n| Frontend directory found? | Trigger Phase 4 cross-link suggestion |\n\n---\n\n## Phase 2: Recommend\n\nBased on what you found, present a concrete recommendation. Don't ask open-ended questions — lead with a proposal:\n\n**Recommended (core coverage):**\n- ✅ **Error Monitoring** — always; captures exceptions and crash reports\n- ✅ **Logging** — `Sentry.LoggerHandler` forwards crash reports and error logs to Sentry\n- ✅ **Tracing** — if Phoenix, Plug, or Ecto detected (via OpenTelemetry)\n\n**Optional (enhanced observability):**\n- ⚡ **Crons** — detect silent failures in scheduled jobs (Oban, Quantum, or manual GenServer)\n- ⚡ **Sentry Logs** — forward structured logs to Sentry Logs Protocol (sentry v12.0.0+)\n\n**Recommendation logic:**\n\n| Feature | Recommend when... |\n|---------|------------------|\n| Error Monitoring | **Always** — non-negotiable baseline |\n| Logging | **Always** — `LoggerHandler` captures crashes that aren't explicit `capture_exception` calls |\n| Tracing | Phoenix, Plug, Ecto, or OpenTelemetry imports detected |\n| Crons | Oban, Quantum, or periodic `GenServer`\u002F`Task` patterns detected |\n| Sentry Logs | sentry v12.0.0+ in use and structured log search is needed |\n\nPropose: *\"I recommend setting up Error Monitoring + Logging [+ Tracing if Phoenix\u002FEcto detected]. Want me to also add Crons or Sentry Logs?\"*\n\n---\n\n## Phase 3: Guide\n\n### Option 1: Igniter Installer (Recommended)\n\n> **You need to run this yourself** — the Igniter installer requires interactive terminal input that the agent can't handle. Copy-paste into your terminal:\n>\n> ```bash\n> mix igniter.install sentry\n> ```\n>\n> Available since sentry v11.0.0. It auto-configures `config\u002Fconfig.exs`, `config\u002Fprod.exs`, `config\u002Fruntime.exs`, and `lib\u002Fmy_app\u002Fapplication.ex`.\n>\n> **Once it finishes, come back and skip to [Verification](#verification).**\n\nIf the user skips the Igniter installer, proceed with Option 2 (Manual Setup) below.\n\n---\n\n### Option 2: Manual Setup\n\n#### Install\n\nAdd to `mix.exs` dependencies:\n\n```elixir\n# mix.exs\ndefp deps do\n  [\n    {:sentry, \"~> 13.0\"},\n    {:finch, \"~> 0.21\"}\n    # Add jason if using Elixir \u003C 1.18:\n    # {:jason, \"~> 1.4\"},\n  ]\nend\n```\n\n```bash\nmix deps.get\n```\n\n#### Configure\n\n```elixir\n# config\u002Fconfig.exs\nconfig :sentry,\n  dsn: System.get_env(\"SENTRY_DSN\"),\n  environment_name: config_env(),\n  enable_source_code_context: true,\n  root_source_code_paths: [File.cwd!()],\n  in_app_otp_apps: [:my_app]\n```\n\nFor runtime configuration (recommended for DSN and release):\n\n```elixir\n# config\u002Fruntime.exs\nimport Config\n\nconfig :sentry,\n  dsn: System.fetch_env!(\"SENTRY_DSN\"),\n  release: System.get_env(\"SENTRY_RELEASE\", \"my-app@#{Application.spec(:my_app, :vsn)}\")\n```\n\n#### Quick Start — Recommended Init Config\n\nThis config enables the most features with sensible defaults:\n\n```elixir\n# config\u002Fconfig.exs\nconfig :sentry,\n  dsn: System.get_env(\"SENTRY_DSN\"),\n  environment_name: config_env(),\n  enable_source_code_context: true,\n  root_source_code_paths: [File.cwd!()],\n  in_app_otp_apps: [:my_app],\n  # Logger handler config — captures crash reports\n  logger: [\n    {:handler, :sentry_handler, Sentry.LoggerHandler, %{\n      config: %{\n        metadata: [:request_id],\n        capture_log_messages: true,\n        level: :error\n      }\n    }}\n  ]\n```\n\n#### Activate Logger Handler\n\nAdd `Logger.add_handlers\u002F1` in `Application.start\u002F2`:\n\n```elixir\n# lib\u002Fmy_app\u002Fapplication.ex\ndef start(_type, _args) do\n  Logger.add_handlers(:my_app)   # activates the :sentry_handler configured above\n\n  children = [\n    MyAppWeb.Endpoint\n    # ... other children\n  ]\n\n  Supervisor.start_link(children, strategy: :one_for_one)\nend\n```\n\n#### Phoenix Integration\n\n**`lib\u002Fmy_app_web\u002Fendpoint.ex`**\n\n```elixir\ndefmodule MyAppWeb.Endpoint do\n  use Sentry.PlugCapture          # Add ABOVE use Phoenix.Endpoint (Cowboy adapter only)\n  use Phoenix.Endpoint, otp_app: :my_app\n\n  # ...\n\n  plug Plug.Parsers,\n    parsers: [:urlencoded, :multipart, :json],\n    pass: [\"*\u002F*\"],\n    json_decoder: Phoenix.json_library()\n\n  plug Sentry.PlugContext          # Add BELOW Plug.Parsers\n  # ...\nend\n```\n\n> **Note:** `Sentry.PlugCapture` is only needed for the **Cowboy** adapter. Phoenix 1.7+ defaults to **Bandit**, where `PlugCapture` is harmless but unnecessary. `Sentry.PlugContext` is always recommended — it enriches events with HTTP request data.\n\n**LiveView errors — `lib\u002Fmy_app_web.ex`**\n\n```elixir\ndef live_view do\n  quote do\n    use Phoenix.LiveView\n\n    on_mount Sentry.LiveViewHook   # captures errors in mount\u002Fhandle_event\u002Fhandle_info\n  end\nend\n```\n\n#### Plain Plug Application\n\n```elixir\ndefmodule MyApp.Router do\n  use Plug.Router\n  use Sentry.PlugCapture          # Cowboy only\n\n  plug Plug.Parsers, parsers: [:urlencoded, :multipart]\n  plug Sentry.PlugContext\n  # ...\nend\n```\n\n### For Each Agreed Feature\n\nWalk through features one at a time. Load the reference file for each, follow its steps, and verify before moving to the next:\n\n| Feature | Reference file | Load when... |\n|---------|---------------|-------------|\n| Error Monitoring | `${SKILL_ROOT}\u002Freferences\u002Ferror-monitoring.md` | Always (baseline) |\n| Tracing | `${SKILL_ROOT}\u002Freferences\u002Ftracing.md` | Phoenix \u002F Ecto \u002F OpenTelemetry detected |\n| Logging | `${SKILL_ROOT}\u002Freferences\u002Flogging.md` | `LoggerHandler` or Sentry Logs setup |\n| Crons | `${SKILL_ROOT}\u002Freferences\u002Fcrons.md` | Oban, Quantum, or periodic jobs detected |\n\nFor each feature: `Read ${SKILL_ROOT}\u002Freferences\u002F\u003Cfeature>.md`, follow steps exactly, verify it works.\n\n---\n\n## Configuration Reference\n\n### Key Config Options\n\n| Option | Type | Default | Purpose |\n|--------|------|---------|---------|\n| `:dsn` | `string \\| nil` | `nil` | SDK disabled if nil; env: `SENTRY_DSN` |\n| `:environment_name` | `atom \\| string` | `\"production\"` | e.g., `:prod`; env: `SENTRY_ENVIRONMENT` |\n| `:release` | `string \\| nil` | `nil` | e.g., `\"my-app@1.0.0\"`; env: `SENTRY_RELEASE` |\n| `:sample_rate` | `float` | `1.0` | Error event sample rate (0.0–1.0) |\n| `:enable_source_code_context` | `boolean` | `false` | Include source lines around errors |\n| `:root_source_code_paths` | `[path]` | `[]` | Required when source context is enabled |\n| `:in_app_otp_apps` | `[atom]` | `[]` | OTP apps whose modules are \"in-app\" in stacktraces |\n| `:before_send` | `(event -> event \\| nil) \\| {m, f}` | `nil` | Hook to mutate or drop error events |\n| `:after_send_event` | `(event, result -> any) \\| {m, f}` | `nil` | Hook called after event is sent |\n| `:filter` | `module` | `Sentry.DefaultEventFilter` | Module implementing `Sentry.EventFilter` |\n| `:max_breadcrumbs` | `integer` | `100` | Max breadcrumbs per process |\n| `:max_stacktrace_arg_length` | `integer` | `10000` | Max length (in graphemes) of each inspected function argument in stacktrace vars (v13.2.0+) |\n| `:dedup_events` | `boolean` | `true` | Deduplicate identical events within ~30 seconds |\n| `:tags` | `map` | `%{}` | Global tags sent with every event |\n| `:traces_sample_rate` | `float \\| nil` | `nil` | Non-nil enables tracing (requires OTel setup) |\n| `:traces_sampler` | `fn \\| {m, f} \\| nil` | `nil` | Custom per-transaction sampling |\n| `:enable_logs` | `boolean` | `false` | Enable Sentry Logs Protocol (v12.0.0+) |\n| `:scrubber` | `keyword` | `[]` | Scrubber config (v13.1.1+); keys: `:conn_private_allow_list` (list of atoms kept from `Plug.Conn.private`) |\n| `:test_mode` | `boolean` | `false` | Capture events in-memory for testing |\n\n### Default PII Guidance\n\nMost Sentry SDKs expose a send-default-PII option. As of sentry v12, the Elixir SDK does not expose a `send_default_pii` config option in its documented option list or current config schema, so do **not** add a non-existent option. For richer user context, use `Sentry.PlugContext` and explicitly set allowed fields with `Sentry.Context.set_user_context\u002F1`, then scrub with `:before_send` if needed. If a future Elixir SDK release adds `send_default_pii`, recommend setting it.\n\n**Automatic PII Scrubbing:** As of v13.1.0, stacktrace frame variables and `FunctionClauseError`\u002F`Phoenix.ActionClauseError` arguments are automatically scrubbed for sensitive data using the same scrubber rules as HTTP request data. Use `:scrubber` config to customize which `Plug.Conn.private` keys are retained.\n\n### Environment Variables\n\n| Variable | Maps to | Purpose |\n|----------|---------|---------|\n| `SENTRY_DSN` | `:dsn` | Data Source Name |\n| `SENTRY_RELEASE` | `:release` | App version (e.g., `my-app@1.0.0`) |\n| `SENTRY_ENVIRONMENT` | `:environment_name` | Deployment environment |\n\n---\n\n## Verification\n\nTest that Sentry is receiving events:\n\n```bash\n# Send a test event from your project\nMIX_ENV=dev mix sentry.send_test_event\n```\n\nOr add a temporary call in a controller action:\n\n```elixir\n# Temporary test — remove after confirming\ndef index(conn, _params) do\n  Sentry.capture_message(\"Sentry Elixir SDK test event\")\n  text(conn, \"sent\")\nend\n```\n\nCheck the Sentry dashboard within a few seconds. If nothing appears:\n1. Set `config :sentry, log_level: :debug` for verbose SDK output\n2. Verify `SENTRY_DSN` is set and the project exists\n3. Confirm `:environment_name` is not set to a value Sentry filters in your alert rules\n\n---\n\n## Phase 4: Cross-Link\n\nAfter completing Elixir setup, check for a companion frontend missing Sentry coverage:\n\n```bash\nls assets\u002F frontend\u002F web\u002F client\u002F ui\u002F 2>\u002Fdev\u002Fnull\ncat assets\u002Fpackage.json frontend\u002Fpackage.json 2>\u002Fdev\u002Fnull | grep -E '\"react\"|\"svelte\"|\"vue\"|\"next\"'\n```\n\nIf a frontend directory exists without Sentry configured, suggest the matching skill:\n\n| Frontend detected | Suggest skill |\n|-------------------|--------------|\n| React \u002F Next.js | `sentry-react-sdk` or `sentry-nextjs-sdk` |\n| Svelte \u002F SvelteKit | `sentry-svelte-sdk` |\n| Vue | See [docs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fguides\u002Fvue\u002F](https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fguides\u002Fvue\u002F) |\n| Other JS\u002FTS | `sentry-browser-sdk` |\n\nConnecting Phoenix backend and JavaScript frontend with linked Sentry projects enables **distributed tracing** — stack traces that span the browser, Phoenix HTTP server, and downstream services in a single trace view.\n\n---\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| Events not appearing | Verify `SENTRY_DSN` is set; run `mix sentry.send_test_event`; set `log_level: :debug` |\n| Missing stack traces on captured exceptions | Pass `stacktrace: __STACKTRACE__` in the `rescue` block: `Sentry.capture_exception(e, stacktrace: __STACKTRACE__)` |\n| `PlugCapture` not working on Bandit | `Sentry.PlugCapture` is Cowboy-only; with Bandit errors surface via `LoggerHandler` |\n| Source code context missing in production | Run `mix sentry.package_source_code` before building your OTP release |\n| Context not appearing on async events | `Sentry.Context.*` is process-scoped; pass values explicitly or propagate Logger metadata across processes |\n| Oban integration not reporting crons | Requires Oban v2.17.6+ or Oban Pro; cron jobs must have `\"cron\" => true` in job meta |\n| Duplicate events from Cowboy\u002FBandit crashes | Set `excluded_domains: [:cowboy, :bandit]` in `LoggerHandler` config (both excluded by default as of v13.1.0) |\n| `finch` not starting | Ensure `{:finch, \"~> 0.21\"}` is in deps; Finch is the default HTTP client since v12.0.0 |\n| JSON encoding error | Add `{:jason, \"~> 1.4\"}` and set `json_library: Jason` for Elixir \u003C 1.18 |\n","> [All Skills](..\u002F..\u002FSKILL_TREE.md) > [SDK Setup](..\u002Fsentry-sdk-setup\u002FSKILL.md) > Elixir SDK\n\n# Sentry Elixir SDK\n\nOpinionated wizard that scans your Elixir project and guides you through complete Sentry setup.\n\n## Invoke This Skill When\n\n- User asks to \"add Sentry to Elixir\" or \"set up Sentry\" in an Elixir or Phoenix app\n- User wants error monitoring, tracing, logging, or crons in Elixir or Phoenix\n- User mentions `sentry` hex package, `getsentry\u002Fsentry-elixir`, or Elixir Sentry SDK\n- User wants to monitor exceptions, Plug errors, LiveView errors, or scheduled jobs\n\n> **Note:** SDK versions and APIs below reflect Sentry docs at time of writing (sentry v13.2.0, requires Elixir ~> 1.13).\n> Always verify against [docs.sentry.io\u002Fplatforms\u002Felixir\u002F](https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Felixir\u002F) before implementing.\n\n---\n\n## Phase 1: Detect\n\nRun these commands to understand the project before making any recommendations:\n\n```bash\n# Check existing Sentry dependency\ngrep -i sentry mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect Elixir version\ncat .tool-versions 2>\u002Fdev\u002Fnull | grep elixir\ngrep \"elixir:\" mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect Phoenix or Plug\ngrep -E '\"phoenix\"|\"plug\"' mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect Phoenix LiveView\ngrep \"phoenix_live_view\" mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect Oban (job queue \u002F crons)\ngrep \"oban\" mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect Quantum (cron scheduler)\ngrep \"quantum\" mix.exs 2>\u002Fdev\u002Fnull\n\n# Detect OpenTelemetry usage\ngrep \"opentelemetry\" mix.exs 2>\u002Fdev\u002Fnull\n\n# Check for companion frontend\nls assets\u002F frontend\u002F web\u002F client\u002F 2>\u002Fdev\u002Fnull\n```\n\n**What to note:**\n\n| Signal | Impact |\n|--------|--------|\n| `sentry` already in `mix.exs`? | Skip install; go to Phase 2 (configure features) |\n| Phoenix detected? | Add `Sentry.PlugCapture`, `Sentry.PlugContext`, optionally `Sentry.LiveViewHook` |\n| LiveView detected? | Add `Sentry.LiveViewHook` to the `live_view` macro in `my_app_web.ex` |\n| Oban detected? | Recommend Crons + error capture via Oban integration |\n| Quantum detected? | Recommend Crons via Quantum integration |\n| OpenTelemetry already present? | Tracing setup only needs `Sentry.OpenTelemetry.*` config |\n| Frontend directory found? | Trigger Phase 4 cross-link suggestion |\n\n---\n\n## Phase 2: Recommend\n\nBased on what you found, present a concrete recommendation. Don't ask open-ended questions — lead with a proposal:\n\n**Recommended (core coverage):**\n- ✅ **Error Monitoring** — always; captures exceptions and crash reports\n- ✅ **Logging** — `Sentry.LoggerHandler` forwards crash reports and error logs to Sentry\n- ✅ **Tracing** — if Phoenix, Plug, or Ecto detected (via OpenTelemetry)\n\n**Optional (enhanced observability):**\n- ⚡ **Crons** — detect silent failures in scheduled jobs (Oban, Quantum, or manual GenServer)\n- ⚡ **Sentry Logs** — forward structured logs to Sentry Logs Protocol (sentry v12.0.0+)\n\n**Recommendation logic:**\n\n| Feature | Recommend when... |\n|---------|------------------|\n| Error Monitoring | **Always** — non-negotiable baseline |\n| Logging | **Always** — `LoggerHandler` captures crashes that aren't explicit `capture_exception` calls |\n| Tracing | Phoenix, Plug, Ecto, or OpenTelemetry imports detected |\n| Crons | Oban, Quantum, or periodic `GenServer`\u002F`Task` patterns detected |\n| Sentry Logs | sentry v12.0.0+ in use and structured log search is needed |\n\nPropose: *\"I recommend setting up Error Monitoring + Logging [+ Tracing if Phoenix\u002FEcto detected]. Want me to also add Crons or Sentry Logs?\"*\n\n---\n\n## Phase 3: Guide\n\n### Option 1: Igniter Installer (Recommended)\n\n> **You need to run this yourself** — the Igniter installer requires interactive terminal input that the agent can't handle. Copy-paste into your terminal:\n>\n> ```bash\n> mix igniter.install sentry\n> ```\n>\n> Available since sentry v11.0.0. It auto-configures `config\u002Fconfig.exs`, `config\u002Fprod.exs`, `config\u002Fruntime.exs`, and `lib\u002Fmy_app\u002Fapplication.ex`.\n>\n> **Once it finishes, come back and skip to [Verification](#verification).**\n\nIf the user skips the Igniter installer, proceed with Option 2 (Manual Setup) below.\n\n---\n\n### Option 2: Manual Setup\n\n#### Install\n\nAdd to `mix.exs` dependencies:\n\n```elixir\n# mix.exs\ndefp deps do\n  [\n    {:sentry, \"~> 13.0\"},\n    {:finch, \"~> 0.21\"}\n    # Add jason if using Elixir \u003C 1.18:\n    # {:jason, \"~> 1.4\"},\n  ]\nend\n```\n\n```bash\nmix deps.get\n```\n\n#### Configure\n\n```elixir\n# config\u002Fconfig.exs\nconfig :sentry,\n  dsn: System.get_env(\"SENTRY_DSN\"),\n  environment_name: config_env(),\n  enable_source_code_context: true,\n  root_source_code_paths: [File.cwd!()],\n  in_app_otp_apps: [:my_app]\n```\n\nFor runtime configuration (recommended for DSN and release):\n\n```elixir\n# config\u002Fruntime.exs\nimport Config\n\nconfig :sentry,\n  dsn: System.fetch_env!(\"SENTRY_DSN\"),\n  release: System.get_env(\"SENTRY_RELEASE\", \"my-app@#{Application.spec(:my_app, :vsn)}\")\n```\n\n#### Quick Start — Recommended Init Config\n\nThis config enables the most features with sensible defaults:\n\n```elixir\n# config\u002Fconfig.exs\nconfig :sentry,\n  dsn: System.get_env(\"SENTRY_DSN\"),\n  environment_name: config_env(),\n  enable_source_code_context: true,\n  root_source_code_paths: [File.cwd!()],\n  in_app_otp_apps: [:my_app],\n  # Logger handler config — captures crash reports\n  logger: [\n    {:handler, :sentry_handler, Sentry.LoggerHandler, %{\n      config: %{\n        metadata: [:request_id],\n        capture_log_messages: true,\n        level: :error\n      }\n    }}\n  ]\n```\n\n#### Activate Logger Handler\n\nAdd `Logger.add_handlers\u002F1` in `Application.start\u002F2`:\n\n```elixir\n# lib\u002Fmy_app\u002Fapplication.ex\ndef start(_type, _args) do\n  Logger.add_handlers(:my_app)   # activates the :sentry_handler configured above\n\n  children = [\n    MyAppWeb.Endpoint\n    # ... other children\n  ]\n\n  Supervisor.start_link(children, strategy: :one_for_one)\nend\n```\n\n#### Phoenix Integration\n\n**`lib\u002Fmy_app_web\u002Fendpoint.ex`**\n\n```elixir\ndefmodule MyAppWeb.Endpoint do\n  use Sentry.PlugCapture          # Add ABOVE use Phoenix.Endpoint (Cowboy adapter only)\n  use Phoenix.Endpoint, otp_app: :my_app\n\n  # ...\n\n  plug Plug.Parsers,\n    parsers: [:urlencoded, :multipart, :json],\n    pass: [\"*\u002F*\"],\n    json_decoder: Phoenix.json_library()\n\n  plug Sentry.PlugContext          # Add BELOW Plug.Parsers\n  # ...\nend\n```\n\n> **Note:** `Sentry.PlugCapture` is only needed for the **Cowboy** adapter. Phoenix 1.7+ defaults to **Bandit**, where `PlugCapture` is harmless but unnecessary. `Sentry.PlugContext` is always recommended — it enriches events with HTTP request data.\n\n**LiveView errors — `lib\u002Fmy_app_web.ex`**\n\n```elixir\ndef live_view do\n  quote do\n    use Phoenix.LiveView\n\n    on_mount Sentry.LiveViewHook   # captures errors in mount\u002Fhandle_event\u002Fhandle_info\n  end\nend\n```\n\n#### Plain Plug Application\n\n```elixir\ndefmodule MyApp.Router do\n  use Plug.Router\n  use Sentry.PlugCapture          # Cowboy only\n\n  plug Plug.Parsers, parsers: [:urlencoded, :multipart]\n  plug Sentry.PlugContext\n  # ...\nend\n```\n\n### For Each Agreed Feature\n\nWalk through features one at a time. Load the reference file for each, follow its steps, and verify before moving to the next:\n\n| Feature | Reference file | Load when... |\n|---------|---------------|-------------|\n| Error Monitoring | `${SKILL_ROOT}\u002Freferences\u002Ferror-monitoring.md` | Always (baseline) |\n| Tracing | `${SKILL_ROOT}\u002Freferences\u002Ftracing.md` | Phoenix \u002F Ecto \u002F OpenTelemetry detected |\n| Logging | `${SKILL_ROOT}\u002Freferences\u002Flogging.md` | `LoggerHandler` or Sentry Logs setup |\n| Crons | `${SKILL_ROOT}\u002Freferences\u002Fcrons.md` | Oban, Quantum, or periodic jobs detected |\n\nFor each feature: `Read ${SKILL_ROOT}\u002Freferences\u002F\u003Cfeature>.md`, follow steps exactly, verify it works.\n\n---\n\n## Configuration Reference\n\n### Key Config Options\n\n| Option | Type | Default | Purpose |\n|--------|------|---------|---------|\n| `:dsn` | `string \\| nil` | `nil` | SDK disabled if nil; env: `SENTRY_DSN` |\n| `:environment_name` | `atom \\| string` | `\"production\"` | e.g., `:prod`; env: `SENTRY_ENVIRONMENT` |\n| `:release` | `string \\| nil` | `nil` | e.g., `\"my-app@1.0.0\"`; env: `SENTRY_RELEASE` |\n| `:sample_rate` | `float` | `1.0` | Error event sample rate (0.0–1.0) |\n| `:enable_source_code_context` | `boolean` | `false` | Include source lines around errors |\n| `:root_source_code_paths` | `[path]` | `[]` | Required when source context is enabled |\n| `:in_app_otp_apps` | `[atom]` | `[]` | OTP apps whose modules are \"in-app\" in stacktraces |\n| `:before_send` | `(event -> event \\| nil) \\| {m, f}` | `nil` | Hook to mutate or drop error events |\n| `:after_send_event` | `(event, result -> any) \\| {m, f}` | `nil` | Hook called after event is sent |\n| `:filter` | `module` | `Sentry.DefaultEventFilter` | Module implementing `Sentry.EventFilter` |\n| `:max_breadcrumbs` | `integer` | `100` | Max breadcrumbs per process |\n| `:max_stacktrace_arg_length` | `integer` | `10000` | Max length (in graphemes) of each inspected function argument in stacktrace vars (v13.2.0+) |\n| `:dedup_events` | `boolean` | `true` | Deduplicate identical events within ~30 seconds |\n| `:tags` | `map` | `%{}` | Global tags sent with every event |\n| `:traces_sample_rate` | `float \\| nil` | `nil` | Non-nil enables tracing (requires OTel setup) |\n| `:traces_sampler` | `fn \\| {m, f} \\| nil` | `nil` | Custom per-transaction sampling |\n| `:enable_logs` | `boolean` | `false` | Enable Sentry Logs Protocol (v12.0.0+) |\n| `:scrubber` | `keyword` | `[]` | Scrubber config (v13.1.1+); keys: `:conn_private_allow_list` (list of atoms kept from `Plug.Conn.private`) |\n| `:test_mode` | `boolean` | `false` | Capture events in-memory for testing |\n\n### Default PII Guidance\n\nMost Sentry SDKs expose a send-default-PII option. As of sentry v12, the Elixir SDK does not expose a `send_default_pii` config option in its documented option list or current config schema, so do **not** add a non-existent option. For richer user context, use `Sentry.PlugContext` and explicitly set allowed fields with `Sentry.Context.set_user_context\u002F1`, then scrub with `:before_send` if needed. If a future Elixir SDK release adds `send_default_pii`, recommend setting it.\n\n**Automatic PII Scrubbing:** As of v13.1.0, stacktrace frame variables and `FunctionClauseError`\u002F`Phoenix.ActionClauseError` arguments are automatically scrubbed for sensitive data using the same scrubber rules as HTTP request data. Use `:scrubber` config to customize which `Plug.Conn.private` keys are retained.\n\n### Environment Variables\n\n| Variable | Maps to | Purpose |\n|----------|---------|---------|\n| `SENTRY_DSN` | `:dsn` | Data Source Name |\n| `SENTRY_RELEASE` | `:release` | App version (e.g., `my-app@1.0.0`) |\n| `SENTRY_ENVIRONMENT` | `:environment_name` | Deployment environment |\n\n---\n\n## Verification\n\nTest that Sentry is receiving events:\n\n```bash\n# Send a test event from your project\nMIX_ENV=dev mix sentry.send_test_event\n```\n\nOr add a temporary call in a controller action:\n\n```elixir\n# Temporary test — remove after confirming\ndef index(conn, _params) do\n  Sentry.capture_message(\"Sentry Elixir SDK test event\")\n  text(conn, \"sent\")\nend\n```\n\nCheck the Sentry dashboard within a few seconds. If nothing appears:\n1. Set `config :sentry, log_level: :debug` for verbose SDK output\n2. Verify `SENTRY_DSN` is set and the project exists\n3. Confirm `:environment_name` is not set to a value Sentry filters in your alert rules\n\n---\n\n## Phase 4: Cross-Link\n\nAfter completing Elixir setup, check for a companion frontend missing Sentry coverage:\n\n```bash\nls assets\u002F frontend\u002F web\u002F client\u002F ui\u002F 2>\u002Fdev\u002Fnull\ncat assets\u002Fpackage.json frontend\u002Fpackage.json 2>\u002Fdev\u002Fnull | grep -E '\"react\"|\"svelte\"|\"vue\"|\"next\"'\n```\n\nIf a frontend directory exists without Sentry configured, suggest the matching skill:\n\n| Frontend detected | Suggest skill |\n|-------------------|--------------|\n| React \u002F Next.js | `sentry-react-sdk` or `sentry-nextjs-sdk` |\n| Svelte \u002F SvelteKit | `sentry-svelte-sdk` |\n| Vue | See [docs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fguides\u002Fvue\u002F](https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fguides\u002Fvue\u002F) |\n| Other JS\u002FTS | `sentry-browser-sdk` |\n\nConnecting Phoenix backend and JavaScript frontend with linked Sentry projects enables **distributed tracing** — stack traces that span the browser, Phoenix HTTP server, and downstream services in a single trace view.\n\n---\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| Events not appearing | Verify `SENTRY_DSN` is set; run `mix sentry.send_test_event`; set `log_level: :debug` |\n| Missing stack traces on captured exceptions | Pass `stacktrace: __STACKTRACE__` in the `rescue` block: `Sentry.capture_exception(e, stacktrace: __STACKTRACE__)` |\n| `PlugCapture` not working on Bandit | `Sentry.PlugCapture` is Cowboy-only; with Bandit errors surface via `LoggerHandler` |\n| Source code context missing in production | Run `mix sentry.package_source_code` before building your OTP release |\n| Context not appearing on async events | `Sentry.Context.*` is process-scoped; pass values explicitly or propagate Logger metadata across processes |\n| Oban integration not reporting crons | Requires Oban v2.17.6+ or Oban Pro; cron jobs must have `\"cron\" => true` in job meta |\n| Duplicate events from Cowboy\u002FBandit crashes | Set `excluded_domains: [:cowboy, :bandit]` in `LoggerHandler` config (both excluded by default as of v13.1.0) |\n| `finch` not starting | Ensure `{:finch, \"~> 0.21\"}` is in deps; Finch is the default HTTP client since v12.0.0 |\n| JSON encoding error | Add `{:jason, \"~> 1.4\"}` and set `json_library: Jason` for Elixir \u003C 1.18 |\n",{"name":5,"parent":24,"license":15,"category":25,"description":7,"disable-model-invocation":26},"sentry-sdk-setup","sdk-setup",true,"main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fsentry-elixir-sdk",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":26},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill sentry-elixir-sdk",{"tool":40,"command":41},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill sentry-elixir-sdk",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill sentry-elixir-sdk","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsentry-elixir-sdk\u002FSKILL.md",[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fcrons.md","REFERENCE","参考文档",9865,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsentry-elixir-sdk\u002Freferences\u002Fcrons.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Ferror-monitoring.md",9533,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsentry-elixir-sdk\u002Freferences\u002Ferror-monitoring.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Flogging.md",8002,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsentry-elixir-sdk\u002Freferences\u002Flogging.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Ftracing.md",7169,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsentry-elixir-sdk\u002Freferences\u002Ftracing.md",[66,74,81,88,95,102],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]