[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DQ11WAE2ZG34AS1MHZ3KGD":3,"skill-same:01M7DQ11WAE2ZG34AS1MHZ3KGD":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7DQ11WAE2ZG34AS1MHZ3KGD","sentry-otel-exporter-setup",null,"Configure the OpenTelemetry Collector with Sentry Exporter for multi-project routing and automatic project creation. Use when setting up OTel with Sentry, configuring collector pipelines for traces and logs, or routing telemetry from multiple services to Sentry projects.","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-otel-exporter-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sentry-otel-exporter-setup\ndescription: Configure the OpenTelemetry Collector with Sentry Exporter for multi-project routing and automatic project creation. Use when setting up OTel with Sentry, configuring collector pipelines for traces and logs, or routing telemetry from multiple services to Sentry projects.\nlicense: Apache-2.0\n---\n# Sentry OTel Exporter Setup\n\n**Terminology**: Always capitalize “Sentry Exporter” when referring to the exporter\ncomponent.\n\nConfigure the OpenTelemetry Collector to send traces and logs to Sentry using the Sentry\nExporter.\n\n## Setup Overview\n\nCopy this checklist to track your progress:\n\n```\nOTel Exporter Setup:\n- [ ] Step 1: Check for existing configuration\n- [ ] Step 2: Check collector version and install if needed\n- [ ] Step 3: Configure project creation settings\n- [ ] Step 4: Write collector config\n- [ ] Step 5: Add environment variable placeholders\n- [ ] Step 6: Run the collector\n- [ ] Step 7: Verify setup\n- [ ] Step 8: Enable trace connectedness with OTLPIntegration (Python\u002FRuby\u002FNode.js)\n```\n\n## Step 1: Check for Existing Configuration\n\nSearch for existing OpenTelemetry Collector configs by looking for YAML files containing\n`receivers:`. Also check for files named `otel-collector-config.*`,\n`collector-config.*`, or `otelcol.*`.\n\n**If an existing config is found**: Ask the user which approach they want:\n- **Modify existing config**: Add Sentry Exporter to the existing file (recommended to\n  avoid duplicates)\n- **Create separate config**: Keep existing config unchanged and create a new one for\n  testing\n\n**Wait for the user’s answer and record their choice before proceeding to Step 2.** The\nrest of the workflow depends on this decision.\n\n**If no config exists**: Note that you’ll create a new `collector-config.yaml` in Step\n4, then proceed to Step 2.\n\n## Step 2: Check Collector Version\n\nThe Sentry Exporter requires **otelcol-contrib v0.145.0 or later**.\n\n### Check for existing collector\n\n1. Run `which otelcol-contrib` to check if it’s on PATH, or check for\n   `.\u002Fotelcol-contrib` in the project\n2. If found, run the appropriate version command and parse the version number\n3. **Record the collector path** (e.g., `otelcol-contrib` if on PATH, or\n   `.\u002Fotelcol-contrib` if local) for use in later steps\n\n| Existing Version | Action |\n| --- | --- |\n| ≥ 0.145.0 | Skip to Step 3 — existing collector is compatible |\n| \u003C 0.145.0 | Proceed with installation below |\n| Not installed | Proceed with installation below |\n\n### Installation\n\nAsk the user how they want to run the collector:\n- **Binary**: Download from GitHub releases.\n  No Docker required.\n- **Docker**: Run as a container.\n  Requires Docker installed.\n\n### Binary Installation\n\nFetch the latest release version from GitHub:\n```bash\ncurl -s https:\u002F\u002Fapi.github.com\u002Frepos\u002Fopen-telemetry\u002Fopentelemetry-collector-releases\u002Freleases\u002Flatest | grep '\"tag_name\"' | cut -d'\"' -f4\n```\n\n**Important**: The GitHub API returns versions with a `v` prefix (e.g., `v0.145.0`). The\ndownload URL path requires the full tag with `v` prefix, but the filename and Docker\ntags use the numeric version without the prefix (e.g., `0.145.0`).\n\nDetect the user’s platform and download the binary:\n\n1. Run `uname -s` and `uname -m` to detect OS and architecture\n2. Map to release values:\n   - Darwin + arm64 → `darwin_arm64`\n   - Darwin + x86_64 → `darwin_amd64`\n   - Linux + x86_64 → `linux_amd64`\n   - Linux + aarch64 → `linux_arm64`\n3. Download and extract:\n```bash\ncurl -LO https:\u002F\u002Fgithub.com\u002Fopen-telemetry\u002Fopentelemetry-collector-releases\u002Freleases\u002Fdownload\u002Fv\u003Cnumeric_version>\u002Fotelcol-contrib_\u003Cnumeric_version>_\u003Cos>_\u003Carch>.tar.gz\ntar -xzf otelcol-contrib_\u003Cnumeric_version>_\u003Cos>_\u003Carch>.tar.gz\nchmod +x otelcol-contrib\n```\n\nExample: For version `v0.145.0`, the URL uses `v0.145.0` in the path but `0.145.0` in\nthe filename.\n\nPerform these steps for the user—do not just show them the commands.\n\n4. **Ask the user** if they want to delete the downloaded tarball to save disk space\n   (~50MB):\n   - **Yes, delete it**: Remove the tarball\n   - **No, keep it**: Leave the tarball in place\n\n**Wait for the user’s response.** Only delete if they explicitly choose to:\n```bash\nrm otelcol-contrib_\u003Cnumeric_version>_\u003Cos>_\u003Carch>.tar.gz\n```\n\n### Docker Installation\n\n1. Verify Docker is installed by running `docker --version`\n2. Fetch the latest release tag from GitHub (same as above)\n3. Pull the image using the numeric version (without `v` prefix):\n```bash\ndocker pull otel\u002Fopentelemetry-collector-contrib:\u003Cnumeric_version>\n```\n\nExample: For GitHub tag `v0.145.0`, use\n`docker pull otel\u002Fopentelemetry-collector-contrib:0.145.0`.\n\nThe `docker run` command comes later in Step 6 after the config is created.\n\n## Step 3: Configure Sentry Project Creation\n\nAsk the user whether to enable automatic Sentry project creation.\nDo not recommend either option:\n- **Yes**: Projects created from service.name.\n  Requires at least one team in your Sentry org.\n  All new projects are assigned to the first team found.\n  Initial data may be dropped during creation.\n- **No**: Projects must exist in Sentry before telemetry arrives.\n\n**Wait for the user’s answer before proceeding to Step 4.**\n\n**If user chooses Yes**: Warn them that the exporter will scan all projects and use the\nfirst team it finds.\nAll auto-created projects will be assigned to that team.\nIf they don’t have any teams yet, they should create one in Sentry first.\n\n## Step 4: Write Collector Config\n\n**Use the decision from Step 1** - if the user chose to modify an existing config, edit\nthat file. If they chose to create a separate config, create a new file.\n**Record the config file path** for use in Steps 5 and 6.\n\nFetch the latest configuration from the Sentry Exporter documentation:\n\n- **Example config** (use as template):\n  `https:\u002F\u002Fraw.githubusercontent.com\u002Fopen-telemetry\u002Fopentelemetry-collector-contrib\u002Fmain\u002Fexporter\u002Fsentryexporter\u002Fdocs\u002Fexample-config.yaml`\n- **Full spec** (all available options):\n  `https:\u002F\u002Fraw.githubusercontent.com\u002Fopen-telemetry\u002Fopentelemetry-collector-contrib\u002Fmain\u002Fexporter\u002Fsentryexporter\u002Fdocs\u002Fspec.md`\n\nUse WebFetch to retrieve the example config as a starting template.\nReference the spec if the user needs advanced options not shown in the example.\n\n### If editing an existing config (per Step 1 decision)\n\nAdd the `sentry` exporter to the `exporters:` section and include it in the appropriate\npipelines (`traces`, `logs`). Do not remove or modify other exporters unless the user\nrequests it.\n\n### If creating a new config (per Step 1 decision)\n\nCreate `collector-config.yaml` based on the fetched example.\nEnsure credentials use environment variable references (`${env:SENTRY_ORG_SLUG}`,\n`${env:SENTRY_AUTH_TOKEN}`).\n\nIf user chose auto-create in Step 3, add `auto_create_projects: true` to the sentry\nexporter.\n\n### Add Debug Exporter (Recommended)\n\nFor troubleshooting during setup, add a `debug` exporter with `verbosity: detailed` to\nthe pipelines. This logs all telemetry to console.\nRemove it once setup is verified.\n\n## Step 5: Add Environment Variable Placeholders\n\nThe Sentry Exporter requires two environment variables.\nYou will add placeholder values that the user fills in themselves—never actual\ncredentials.\n\n**Language constraint**: NEVER say “add credentials”, “add environment variables”, or\n“add the token” without explicitly stating these are **placeholders**. Always clarify\nthe user fills them in later.\n\nDO NOT say:\n- “Let me add the environment variables”\n- “I’ll add the credentials to your .env”\n- “Adding the Sentry auth token”\n\nSAY INSTEAD:\n- “I’ll add placeholder environment variables for you to fill in”\n- “Adding placeholder values—you’ll replace these with your actual credentials”\n- “I’ll set up the env var keys with placeholder values”\n\nSearch for existing `.env` files in the project using glob `**\u002F.env`. **Always ask the\nuser which file to use**—do not infer from context or guess based on open files.\n\nPresent the discovered options:\n- **[path to discovered .env file]**: Add to existing file (list each discovered path)\n- **Create new at root**: Create .env in project root\n\n**Wait for the user’s explicit selection.** Do not proceed until they choose.\nRecord the env file path for use in Steps 5 (validation) and 6 (running).\n\nAdd these placeholder values to the chosen file:\n\n```bash\nSENTRY_ORG_SLUG=your-org-slug\nSENTRY_AUTH_TOKEN=your-token-here\n```\n\nAfter adding the placeholders, tell the user how to get their real values from Sentry:\n\n1. **Sentry org slug**: In Sentry, go to **Settings → Organization Settings →\n   Organization Slug**. This is also your subdomain (e.g., `myorg` in\n   `https:\u002F\u002Fmyorg.sentry.io`)\n2. **Sentry auth token**: Create an Internal Integration in Sentry:\n   - In Sentry, go to **Settings → Developer Settings → Custom Integrations**\n   - Click **Create New Integration** → Choose **Internal Integration**\n   - Set permissions:\n     - **Organization: Read** — required\n     - **Project: Read** — required\n     - **Project: Write** — required only if using `auto_create_projects`\n   - Save, then click **Create New Token** and copy it\n\nEnsure the chosen `.env` file is in `.gitignore`.\n\n### Wait for user to set credentials\n\nAfter explaining how to get the values, ask the user to confirm when they’ve updated the\n`.env` file:\n- **Yes, credentials are set**: Proceed to validate and run the collector\n- **Not yet**: I’ll wait while you update the .env file\n\nIf user selects “Not yet”, wait and ask again.\nDo not proceed to Step 6 until credentials are confirmed.\n\n### Validate config\n\nOnce credentials are set, validate the configuration using the appropriate method based\non the installation choice from Step 2.\n\n**Use the config file path from Step 1** (either the existing config you modified or the\nnew `collector-config.yaml`).\n\n#### Binary validation\n\nUse the collector path recorded in Step 2 (either `otelcol-contrib` if on PATH, or\n`.\u002Fotelcol-contrib` if local).\n\n**Load environment variables first**, then run validation:\n\n```bash\nset -a && source \"\u003Cenv_file>\" && set +a && \"\u003Ccollector_path>\" validate --config \"\u003Cconfig_file>\"\n```\n\n#### Docker validation\n\n**Note**: Docker volume mounts require absolute paths.\nIf `\u003Cconfig_file>` or `\u003Cenv_file>` are relative paths, prefix them with `$(pwd)\u002F`. If\nthey’re already absolute paths, use them directly.\n\n```bash\ndocker run --rm \\\n  -v \"\u003Cconfig_file>\":\u002Fetc\u002Fotelcol-contrib\u002Fconfig.yaml \\\n  --env-file \"\u003Cenv_file>\" \\\n  otel\u002Fopentelemetry-collector-contrib:\u003Cnumeric_version> \\\n  validate --config \u002Fetc\u002Fotelcol-contrib\u002Fconfig.yaml\n```\n\nUse the `.env` file path chosen in Step 5.\n\n**If validation fails:**\n1. Review the error message carefully\n2. Fix the issues in the config file\n3. Run validation again\n4. Repeat until validation passes\n\n**Once validation passes**, ask the user if they’re ready to run the collector:\n- **Yes, run it now**: Proceed to Step 6 and start the collector\n- **Not yet**: Wait. The user may want to review the config or prepare their environment\n  first.\n\n**Wait for the user’s confirmation before proceeding to Step 6.**\n\n## Step 6: Run the Collector\n\n**Only reach this step after the user confirms they’re ready to run the collector.**\n\n**Give the user the run command but do not execute it automatically.** The user will run\nit themselves.\n\nProvide the appropriate command based on the installation method chosen in Step 2.\n\n**Use the actual paths chosen earlier:**\n- **Config file**: From Step 1 (existing config or new `collector-config.yaml`)\n- **Env file**: From Step 5 (the `.env` file the user selected)\n- **Collector path**: From Step 2 (either `otelcol-contrib` if on PATH, or\n  `.\u002Fotelcol-contrib` if local)\n\n### Binary\n\n**Load environment variables first**, then run the collector:\n\n```bash\nset -a && source \"\u003Cenv_file>\" && set +a && \"\u003Ccollector_path>\" --config \"\u003Cconfig_file>\"\n```\n\n### Docker\n\n**Note**: Docker volume mounts require absolute paths.\nIf `\u003Cconfig_file>` or `\u003Cenv_file>` are relative paths, prefix them with `$(pwd)\u002F`. If\nthey’re already absolute paths, use them directly.\n\n**If re-running**: Stop and remove any existing container first:\n```bash\ndocker stop otel-collector 2>\u002Fdev\u002Fnull; docker rm otel-collector 2>\u002Fdev\u002Fnull\n```\n\n```bash\ndocker run -d \\\n  --name otel-collector \\\n  -p 4317:4317 \\\n  -p 4318:4318 \\\n  -p 13133:13133 \\\n  -v \"\u003Cconfig_file>\":\u002Fetc\u002Fotelcol-contrib\u002Fconfig.yaml \\\n  --env-file \"\u003Cenv_file>\" \\\n  otel\u002Fopentelemetry-collector-contrib:\u003Cnumeric_version>\n```\n\nUse the same numeric version (without `v` prefix) that was pulled in Step 2.\n\nAfter providing the command, tell the user to run it when they’re ready, then proceed to\nStep 7 for verification.\n\n## Step 7: Verify Setup\n\n1. Check collector logs for successful startup (no errors about invalid config or failed\n   connections)\n2. Look for log messages indicating connection to Sentry\n3. Send test telemetry from an instrumented service and verify it appears in Sentry\n\n**Success criteria:**\n- Collector starts without errors\n- Traces and\u002For logs appear in Sentry within 60 seconds of sending\n\nIf using Docker, check logs with `docker logs otel-collector`.\n\n## Step 8: Enable Trace Connectedness with OTLPIntegration\n\nIf the user’s application uses a Sentry SDK (Python, Ruby, or Node.js), recommend\nenabling the OTLPIntegration.\nThis ensures **trace connectedness** — linking OTel traces to Sentry errors, logs,\ncrons, and metrics — and sets up distributed tracing propagation automatically.\n\nWithout this step, traces sent through the collector appear in Sentry but are not\nconnected to other Sentry events (errors, logs) from the same service.\n\nAsk the user: **Does your application use the Sentry Python SDK, Sentry Ruby SDK, or\nSentry Node.js SDK?**\n\n- **Python**: Follow the Python setup below\n- **Ruby**: Follow the Ruby setup below\n- **Node.js**: Follow the Node.js setup below\n- **Neither \u002F Other SDK**: Skip this step.\n  Trace connectedness via OTLPIntegration is currently available for Python, Ruby, and\n  Node.js.\n\n### Python OTLPIntegration\n\nDocs: https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fpython\u002Fintegrations\u002Fotlp\u002F\n\n1. Install the extra:\n```bash\npip install \"sentry-sdk[opentelemetry-otlp]\"\n```\n\n2. Add the `OTLPIntegration` to the existing `sentry_sdk.init()` call, setting\n   `collector_url` to the collector’s OTLP traces endpoint:\n```python\nfrom sentry_sdk.integrations.otlp import OTLPIntegration\n\nsentry_sdk.init(\n    dsn=\"___PUBLIC_DSN___\",\n    integrations=[\n        OTLPIntegration(collector_url=\"http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces\"),\n    ],\n)\n```\n\nUse the collector’s actual OTLP HTTP endpoint.\nThe default is `http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces` if running locally.\n\n### Ruby OTLPIntegration\n\nDocs: https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fruby\u002Fintegrations\u002Fotlp\u002F\n\n1. Add gems to the Gemfile:\n```ruby\ngem \"sentry-opentelemetry\"\ngem \"opentelemetry-sdk\"\ngem \"opentelemetry-exporter-otlp\"\ngem \"opentelemetry-instrumentation-all\"\n```\n\n2. Run `bundle install`\n\n3. Configure OpenTelemetry instrumentation:\n```ruby\nOpenTelemetry::SDK.configure do |c|\n  c.use_all\nend\n```\n\n4. Enable OTLP in the existing `Sentry.init` block, setting `collector_url` to the\n   collector’s OTLP traces endpoint:\n```ruby\nSentry.init do |config|\n  config.dsn = \"___PUBLIC_DSN___\"\n  config.otlp.enabled = true\n  config.otlp.collector_url = \"http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces\"\nend\n```\n\nUse the collector’s actual OTLP HTTP endpoint.\nThe default is `http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces` if running locally.\n\n### Node.js OTLPIntegration\n\nDocs: https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fguides\u002Fnode\u002F\n\n1. Install the lightweight Sentry SDK and OpenTelemetry dependencies:\n```bash\nnpm install @sentry\u002Fnode-core @opentelemetry\u002Fapi @opentelemetry\u002Fsdk-trace-node @opentelemetry\u002Fsdk-trace-base\n```\n\n2. Create an instrument file (`instrument.mjs`) that sets up OTel and Sentry together:\n```javascript\nimport { NodeTracerProvider } from '@opentelemetry\u002Fsdk-trace-node';\nimport * as Sentry from '@sentry\u002Fnode-core\u002Flight';\nimport { otlpIntegration } from '@sentry\u002Fnode-core\u002Flight\u002Fotlp';\n\nconst provider = new NodeTracerProvider();\nprovider.register();\n\nSentry.init({\n  dsn: '___PUBLIC_DSN___',\n  integrations: [\n    otlpIntegration({\n      collectorUrl: 'http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces',\n    }),\n  ],\n});\n```\n\n3. Start your app with the `--import` flag:\n```bash\nnode --import .\u002Finstrument.mjs app.mjs\n```\n\nUse the collector’s actual OTLP HTTP endpoint.\nThe default is `http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces` if running locally.\n\n> **Do not set `tracesSampleRate`** when using `otlpIntegration` — OTel controls\n> sampling. Setting it would conflict with the OTLP path.\n\n## Troubleshooting\n\n| Error | Cause | Fix |\n| --- | --- | --- |\n| “failed to create project” | Missing Project:Write permission | Update Internal Integration permissions in Sentry |\n| “no team found” | No teams in org | Create a team in Sentry before enabling auto-create |\n| “invalid auth token” | Wrong token type or expired | Use Internal Integration token, not user auth token |\n| “connection refused” on 4317\u002F4318 | Collector not running or port conflict | Check collector logs and ensure ports are available |\n| Validation fails with env var errors | .env file not loaded or placeholders not replaced | Ensure real credentials are in .env and the file is sourced |\n| “container name already in use” | Previous container exists | Run `docker stop otel-collector && docker rm otel-collector` |\n","# Sentry OTel Exporter Setup\n\n**Terminology**: Always capitalize “Sentry Exporter” when referring to the exporter\ncomponent.\n\nConfigure the OpenTelemetry Collector to send traces and logs to Sentry using the Sentry\nExporter.\n\n## Setup Overview\n\nCopy this checklist to track your progress:\n\n```\nOTel Exporter Setup:\n- [ ] Step 1: Check for existing configuration\n- [ ] Step 2: Check collector version and install if needed\n- [ ] Step 3: Configure project creation settings\n- [ ] Step 4: Write collector config\n- [ ] Step 5: Add environment variable placeholders\n- [ ] Step 6: Run the collector\n- [ ] Step 7: Verify setup\n- [ ] Step 8: Enable trace connectedness with OTLPIntegration (Python\u002FRuby\u002FNode.js)\n```\n\n## Step 1: Check for Existing Configuration\n\nSearch for existing OpenTelemetry Collector configs by looking for YAML files containing\n`receivers:`. Also check for files named `otel-collector-config.*`,\n`collector-config.*`, or `otelcol.*`.\n\n**If an existing config is found**: Ask the user which approach they want:\n- **Modify existing config**: Add Sentry Exporter to the existing file (recommended to\n  avoid duplicates)\n- **Create separate config**: Keep existing config unchanged and create a new one for\n  testing\n\n**Wait for the user’s answer and record their choice before proceeding to Step 2.** The\nrest of the workflow depends on this decision.\n\n**If no config exists**: Note that you’ll create a new `collector-config.yaml` in Step\n4, then proceed to Step 2.\n\n## Step 2: Check Collector Version\n\nThe Sentry Exporter requires **otelcol-contrib v0.145.0 or later**.\n\n### Check for existing collector\n\n1. Run `which otelcol-contrib` to check if it’s on PATH, or check for\n   `.\u002Fotelcol-contrib` in the project\n2. If found, run the appropriate version command and parse the version number\n3. **Record the collector path** (e.g., `otelcol-contrib` if on PATH, or\n   `.\u002Fotelcol-contrib` if local) for use in later steps\n\n| Existing Version | Action |\n| --- | --- |\n| ≥ 0.145.0 | Skip to Step 3 — existing collector is compatible |\n| \u003C 0.145.0 | Proceed with installation below |\n| Not installed | Proceed with installation below |\n\n### Installation\n\nAsk the user how they want to run the collector:\n- **Binary**: Download from GitHub releases.\n  No Docker required.\n- **Docker**: Run as a container.\n  Requires Docker installed.\n\n### Binary Installation\n\nFetch the latest release version from GitHub:\n```bash\ncurl -s https:\u002F\u002Fapi.github.com\u002Frepos\u002Fopen-telemetry\u002Fopentelemetry-collector-releases\u002Freleases\u002Flatest | grep '\"tag_name\"' | cut -d'\"' -f4\n```\n\n**Important**: The GitHub API returns versions with a `v` prefix (e.g., `v0.145.0`). The\ndownload URL path requires the full tag with `v` prefix, but the filename and Docker\ntags use the numeric version without the prefix (e.g., `0.145.0`).\n\nDetect the user’s platform and download the binary:\n\n1. Run `uname -s` and `uname -m` to detect OS and architecture\n2. Map to release values:\n   - Darwin + arm64 → `darwin_arm64`\n   - Darwin + x86_64 → `darwin_amd64`\n   - Linux + x86_64 → `linux_amd64`\n   - Linux + aarch64 → `linux_arm64`\n3. Download and extract:\n```bash\ncurl -LO https:\u002F\u002Fgithub.com\u002Fopen-telemetry\u002Fopentelemetry-collector-releases\u002Freleases\u002Fdownload\u002Fv\u003Cnumeric_version>\u002Fotelcol-contrib_\u003Cnumeric_version>_\u003Cos>_\u003Carch>.tar.gz\ntar -xzf otelcol-contrib_\u003Cnumeric_version>_\u003Cos>_\u003Carch>.tar.gz\nchmod +x otelcol-contrib\n```\n\nExample: For version `v0.145.0`, the URL uses `v0.145.0` in the path but `0.145.0` in\nthe filename.\n\nPerform these steps for the user—do not just show them the commands.\n\n4. **Ask the user** if they want to delete the downloaded tarball to save disk space\n   (~50MB):\n   - **Yes, delete it**: Remove the tarball\n   - **No, keep it**: Leave the tarball in place\n\n**Wait for the user’s response.** Only delete if they explicitly choose to:\n```bash\nrm otelcol-contrib_\u003Cnumeric_version>_\u003Cos>_\u003Carch>.tar.gz\n```\n\n### Docker Installation\n\n1. Verify Docker is installed by running `docker --version`\n2. Fetch the latest release tag from GitHub (same as above)\n3. Pull the image using the numeric version (without `v` prefix):\n```bash\ndocker pull otel\u002Fopentelemetry-collector-contrib:\u003Cnumeric_version>\n```\n\nExample: For GitHub tag `v0.145.0`, use\n`docker pull otel\u002Fopentelemetry-collector-contrib:0.145.0`.\n\nThe `docker run` command comes later in Step 6 after the config is created.\n\n## Step 3: Configure Sentry Project Creation\n\nAsk the user whether to enable automatic Sentry project creation.\nDo not recommend either option:\n- **Yes**: Projects created from service.name.\n  Requires at least one team in your Sentry org.\n  All new projects are assigned to the first team found.\n  Initial data may be dropped during creation.\n- **No**: Projects must exist in Sentry before telemetry arrives.\n\n**Wait for the user’s answer before proceeding to Step 4.**\n\n**If user chooses Yes**: Warn them that the exporter will scan all projects and use the\nfirst team it finds.\nAll auto-created projects will be assigned to that team.\nIf they don’t have any teams yet, they should create one in Sentry first.\n\n## Step 4: Write Collector Config\n\n**Use the decision from Step 1** - if the user chose to modify an existing config, edit\nthat file. If they chose to create a separate config, create a new file.\n**Record the config file path** for use in Steps 5 and 6.\n\nFetch the latest configuration from the Sentry Exporter documentation:\n\n- **Example config** (use as template):\n  `https:\u002F\u002Fraw.githubusercontent.com\u002Fopen-telemetry\u002Fopentelemetry-collector-contrib\u002Fmain\u002Fexporter\u002Fsentryexporter\u002Fdocs\u002Fexample-config.yaml`\n- **Full spec** (all available options):\n  `https:\u002F\u002Fraw.githubusercontent.com\u002Fopen-telemetry\u002Fopentelemetry-collector-contrib\u002Fmain\u002Fexporter\u002Fsentryexporter\u002Fdocs\u002Fspec.md`\n\nUse WebFetch to retrieve the example config as a starting template.\nReference the spec if the user needs advanced options not shown in the example.\n\n### If editing an existing config (per Step 1 decision)\n\nAdd the `sentry` exporter to the `exporters:` section and include it in the appropriate\npipelines (`traces`, `logs`). Do not remove or modify other exporters unless the user\nrequests it.\n\n### If creating a new config (per Step 1 decision)\n\nCreate `collector-config.yaml` based on the fetched example.\nEnsure credentials use environment variable references (`${env:SENTRY_ORG_SLUG}`,\n`${env:SENTRY_AUTH_TOKEN}`).\n\nIf user chose auto-create in Step 3, add `auto_create_projects: true` to the sentry\nexporter.\n\n### Add Debug Exporter (Recommended)\n\nFor troubleshooting during setup, add a `debug` exporter with `verbosity: detailed` to\nthe pipelines. This logs all telemetry to console.\nRemove it once setup is verified.\n\n## Step 5: Add Environment Variable Placeholders\n\nThe Sentry Exporter requires two environment variables.\nYou will add placeholder values that the user fills in themselves—never actual\ncredentials.\n\n**Language constraint**: NEVER say “add credentials”, “add environment variables”, or\n“add the token” without explicitly stating these are **placeholders**. Always clarify\nthe user fills them in later.\n\nDO NOT say:\n- “Let me add the environment variables”\n- “I’ll add the credentials to your .env”\n- “Adding the Sentry auth token”\n\nSAY INSTEAD:\n- “I’ll add placeholder environment variables for you to fill in”\n- “Adding placeholder values—you’ll replace these with your actual credentials”\n- “I’ll set up the env var keys with placeholder values”\n\nSearch for existing `.env` files in the project using glob `**\u002F.env`. **Always ask the\nuser which file to use**—do not infer from context or guess based on open files.\n\nPresent the discovered options:\n- **[path to discovered .env file]**: Add to existing file (list each discovered path)\n- **Create new at root**: Create .env in project root\n\n**Wait for the user’s explicit selection.** Do not proceed until they choose.\nRecord the env file path for use in Steps 5 (validation) and 6 (running).\n\nAdd these placeholder values to the chosen file:\n\n```bash\nSENTRY_ORG_SLUG=your-org-slug\nSENTRY_AUTH_TOKEN=your-token-here\n```\n\nAfter adding the placeholders, tell the user how to get their real values from Sentry:\n\n1. **Sentry org slug**: In Sentry, go to **Settings → Organization Settings →\n   Organization Slug**. This is also your subdomain (e.g., `myorg` in\n   `https:\u002F\u002Fmyorg.sentry.io`)\n2. **Sentry auth token**: Create an Internal Integration in Sentry:\n   - In Sentry, go to **Settings → Developer Settings → Custom Integrations**\n   - Click **Create New Integration** → Choose **Internal Integration**\n   - Set permissions:\n     - **Organization: Read** — required\n     - **Project: Read** — required\n     - **Project: Write** — required only if using `auto_create_projects`\n   - Save, then click **Create New Token** and copy it\n\nEnsure the chosen `.env` file is in `.gitignore`.\n\n### Wait for user to set credentials\n\nAfter explaining how to get the values, ask the user to confirm when they’ve updated the\n`.env` file:\n- **Yes, credentials are set**: Proceed to validate and run the collector\n- **Not yet**: I’ll wait while you update the .env file\n\nIf user selects “Not yet”, wait and ask again.\nDo not proceed to Step 6 until credentials are confirmed.\n\n### Validate config\n\nOnce credentials are set, validate the configuration using the appropriate method based\non the installation choice from Step 2.\n\n**Use the config file path from Step 1** (either the existing config you modified or the\nnew `collector-config.yaml`).\n\n#### Binary validation\n\nUse the collector path recorded in Step 2 (either `otelcol-contrib` if on PATH, or\n`.\u002Fotelcol-contrib` if local).\n\n**Load environment variables first**, then run validation:\n\n```bash\nset -a && source \"\u003Cenv_file>\" && set +a && \"\u003Ccollector_path>\" validate --config \"\u003Cconfig_file>\"\n```\n\n#### Docker validation\n\n**Note**: Docker volume mounts require absolute paths.\nIf `\u003Cconfig_file>` or `\u003Cenv_file>` are relative paths, prefix them with `$(pwd)\u002F`. If\nthey’re already absolute paths, use them directly.\n\n```bash\ndocker run --rm \\\n  -v \"\u003Cconfig_file>\":\u002Fetc\u002Fotelcol-contrib\u002Fconfig.yaml \\\n  --env-file \"\u003Cenv_file>\" \\\n  otel\u002Fopentelemetry-collector-contrib:\u003Cnumeric_version> \\\n  validate --config \u002Fetc\u002Fotelcol-contrib\u002Fconfig.yaml\n```\n\nUse the `.env` file path chosen in Step 5.\n\n**If validation fails:**\n1. Review the error message carefully\n2. Fix the issues in the config file\n3. Run validation again\n4. Repeat until validation passes\n\n**Once validation passes**, ask the user if they’re ready to run the collector:\n- **Yes, run it now**: Proceed to Step 6 and start the collector\n- **Not yet**: Wait. The user may want to review the config or prepare their environment\n  first.\n\n**Wait for the user’s confirmation before proceeding to Step 6.**\n\n## Step 6: Run the Collector\n\n**Only reach this step after the user confirms they’re ready to run the collector.**\n\n**Give the user the run command but do not execute it automatically.** The user will run\nit themselves.\n\nProvide the appropriate command based on the installation method chosen in Step 2.\n\n**Use the actual paths chosen earlier:**\n- **Config file**: From Step 1 (existing config or new `collector-config.yaml`)\n- **Env file**: From Step 5 (the `.env` file the user selected)\n- **Collector path**: From Step 2 (either `otelcol-contrib` if on PATH, or\n  `.\u002Fotelcol-contrib` if local)\n\n### Binary\n\n**Load environment variables first**, then run the collector:\n\n```bash\nset -a && source \"\u003Cenv_file>\" && set +a && \"\u003Ccollector_path>\" --config \"\u003Cconfig_file>\"\n```\n\n### Docker\n\n**Note**: Docker volume mounts require absolute paths.\nIf `\u003Cconfig_file>` or `\u003Cenv_file>` are relative paths, prefix them with `$(pwd)\u002F`. If\nthey’re already absolute paths, use them directly.\n\n**If re-running**: Stop and remove any existing container first:\n```bash\ndocker stop otel-collector 2>\u002Fdev\u002Fnull; docker rm otel-collector 2>\u002Fdev\u002Fnull\n```\n\n```bash\ndocker run -d \\\n  --name otel-collector \\\n  -p 4317:4317 \\\n  -p 4318:4318 \\\n  -p 13133:13133 \\\n  -v \"\u003Cconfig_file>\":\u002Fetc\u002Fotelcol-contrib\u002Fconfig.yaml \\\n  --env-file \"\u003Cenv_file>\" \\\n  otel\u002Fopentelemetry-collector-contrib:\u003Cnumeric_version>\n```\n\nUse the same numeric version (without `v` prefix) that was pulled in Step 2.\n\nAfter providing the command, tell the user to run it when they’re ready, then proceed to\nStep 7 for verification.\n\n## Step 7: Verify Setup\n\n1. Check collector logs for successful startup (no errors about invalid config or failed\n   connections)\n2. Look for log messages indicating connection to Sentry\n3. Send test telemetry from an instrumented service and verify it appears in Sentry\n\n**Success criteria:**\n- Collector starts without errors\n- Traces and\u002For logs appear in Sentry within 60 seconds of sending\n\nIf using Docker, check logs with `docker logs otel-collector`.\n\n## Step 8: Enable Trace Connectedness with OTLPIntegration\n\nIf the user’s application uses a Sentry SDK (Python, Ruby, or Node.js), recommend\nenabling the OTLPIntegration.\nThis ensures **trace connectedness** — linking OTel traces to Sentry errors, logs,\ncrons, and metrics — and sets up distributed tracing propagation automatically.\n\nWithout this step, traces sent through the collector appear in Sentry but are not\nconnected to other Sentry events (errors, logs) from the same service.\n\nAsk the user: **Does your application use the Sentry Python SDK, Sentry Ruby SDK, or\nSentry Node.js SDK?**\n\n- **Python**: Follow the Python setup below\n- **Ruby**: Follow the Ruby setup below\n- **Node.js**: Follow the Node.js setup below\n- **Neither \u002F Other SDK**: Skip this step.\n  Trace connectedness via OTLPIntegration is currently available for Python, Ruby, and\n  Node.js.\n\n### Python OTLPIntegration\n\nDocs: https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fpython\u002Fintegrations\u002Fotlp\u002F\n\n1. Install the extra:\n```bash\npip install \"sentry-sdk[opentelemetry-otlp]\"\n```\n\n2. Add the `OTLPIntegration` to the existing `sentry_sdk.init()` call, setting\n   `collector_url` to the collector’s OTLP traces endpoint:\n```python\nfrom sentry_sdk.integrations.otlp import OTLPIntegration\n\nsentry_sdk.init(\n    dsn=\"___PUBLIC_DSN___\",\n    integrations=[\n        OTLPIntegration(collector_url=\"http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces\"),\n    ],\n)\n```\n\nUse the collector’s actual OTLP HTTP endpoint.\nThe default is `http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces` if running locally.\n\n### Ruby OTLPIntegration\n\nDocs: https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fruby\u002Fintegrations\u002Fotlp\u002F\n\n1. Add gems to the Gemfile:\n```ruby\ngem \"sentry-opentelemetry\"\ngem \"opentelemetry-sdk\"\ngem \"opentelemetry-exporter-otlp\"\ngem \"opentelemetry-instrumentation-all\"\n```\n\n2. Run `bundle install`\n\n3. Configure OpenTelemetry instrumentation:\n```ruby\nOpenTelemetry::SDK.configure do |c|\n  c.use_all\nend\n```\n\n4. Enable OTLP in the existing `Sentry.init` block, setting `collector_url` to the\n   collector’s OTLP traces endpoint:\n```ruby\nSentry.init do |config|\n  config.dsn = \"___PUBLIC_DSN___\"\n  config.otlp.enabled = true\n  config.otlp.collector_url = \"http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces\"\nend\n```\n\nUse the collector’s actual OTLP HTTP endpoint.\nThe default is `http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces` if running locally.\n\n### Node.js OTLPIntegration\n\nDocs: https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fguides\u002Fnode\u002F\n\n1. Install the lightweight Sentry SDK and OpenTelemetry dependencies:\n```bash\nnpm install @sentry\u002Fnode-core @opentelemetry\u002Fapi @opentelemetry\u002Fsdk-trace-node @opentelemetry\u002Fsdk-trace-base\n```\n\n2. Create an instrument file (`instrument.mjs`) that sets up OTel and Sentry together:\n```javascript\nimport { NodeTracerProvider } from '@opentelemetry\u002Fsdk-trace-node';\nimport * as Sentry from '@sentry\u002Fnode-core\u002Flight';\nimport { otlpIntegration } from '@sentry\u002Fnode-core\u002Flight\u002Fotlp';\n\nconst provider = new NodeTracerProvider();\nprovider.register();\n\nSentry.init({\n  dsn: '___PUBLIC_DSN___',\n  integrations: [\n    otlpIntegration({\n      collectorUrl: 'http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces',\n    }),\n  ],\n});\n```\n\n3. Start your app with the `--import` flag:\n```bash\nnode --import .\u002Finstrument.mjs app.mjs\n```\n\nUse the collector’s actual OTLP HTTP endpoint.\nThe default is `http:\u002F\u002Flocalhost:4318\u002Fv1\u002Ftraces` if running locally.\n\n> **Do not set `tracesSampleRate`** when using `otlpIntegration` — OTel controls\n> sampling. Setting it would conflict with the OTLP path.\n\n## Troubleshooting\n\n| Error | Cause | Fix |\n| --- | --- | --- |\n| “failed to create project” | Missing Project:Write permission | Update Internal Integration permissions in Sentry |\n| “no team found” | No teams in org | Create a team in Sentry before enabling auto-create |\n| “invalid auth token” | Wrong token type or expired | Use Internal Integration token, not user auth token |\n| “connection refused” on 4317\u002F4318 | Collector not running or port conflict | Check collector logs and ensure ports are available |\n| Validation fails with env var errors | .env file not loaded or placeholders not replaced | Ensure real credentials are in .env and the file is sourced |\n| “container name already in use” | Previous container exists | Run `docker stop otel-collector && docker rm otel-collector` |\n",{"name":5,"license":15,"description":7},"main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fsentry-otel-exporter-setup",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":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill sentry-otel-exporter-setup",{"tool":37,"command":38},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill sentry-otel-exporter-setup",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill sentry-otel-exporter-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsentry-otel-exporter-setup\u002FSKILL.md",true,[],[46,54,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":50,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":50,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":50,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":50,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":50,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":50,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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",[],[]]