Read the migration guide before making changes:
Works with
Read the migration guide before making changes:
elastic-apm-agent.jar, elasticapm.properties, all ELASTIC_APM_* env vars,
and any co.elastic.apm Maven/Gradle dependencieselastic-otel-javaagent.jar (download from
Maven Central, not a Maven/Gradle
compile dependency)-javaagent:/path/to/elastic-otel-javaagent.jar or
JAVA_TOOL_OPTIONS="-javaagent:/path/to/elastic-otel-javaagent.jar" — without this the agent does nothingOTEL_SERVICE_NAME (replaces ELASTIC_APM_SERVICE_NAME)OTEL_EXPORTER_OTLP_ENDPOINT — must be the managed OTLP endpoint or EDOT Collector URL. Do NOT reuse the
old ELASTIC_APM_SERVER_URL value. Never use an APM Server URL (no apm-server, no :8200, no
/intake/v2/events)OTEL_EXPORTER_OTLP_HEADERS — "Authorization=ApiKey <key>" or "Authorization=Bearer <token>" (replaces
ELASTIC_APM_SECRET_TOKEN / API_KEY)OTEL_TRACES_EXPORTER, OTEL_METRICS_EXPORTER, or OTEL_LOGS_EXPORTER — the defaults are already
correctSee the EDOT Java migration guide for complete examples.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionobservability-edot-java-migrateExecute the skills CLI command in your project's root directory to begin installation:
Fetches observability-edot-java-migrate from elastic/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate observability-edot-java-migrate. Access via /observability-edot-java-migrate in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
296
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
296
stars
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
github/awesome-copilot
affaan-m/everything-claude-code
jwynia/agent-skills
mindrally/skills
kostja94/marketing-skills
wispbit-ai/skills
observability-edot-java-migrate fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend observability-edot-java-migrate for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for observability-edot-java-migrate matched our evaluation — installs cleanly and behaves as described in the markdown.
observability-edot-java-migrate reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: observability-edot-java-migrate is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend observability-edot-java-migrate for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added observability-edot-java-migrate from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in observability-edot-java-migrate — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
observability-edot-java-migrate fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in observability-edot-java-migrate — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 37