Read the setup guide before making changes:
Works with
Read the setup guide before making changes:
Elastic.OpenTelemetry and OpenTelemetry.Instrumentation.AspNetCore (for ASP.NET Core apps)builder.AddElasticOpenTelemetry() on the IHostApplicationBuilder (in Program.cs
or equivalent). Without this, no telemetry is collectedOTEL_SERVICE_NAMEOTEL_EXPORTER_OTLP_ENDPOINT — must be the managed OTLP endpoint or EDOT Collector URL. 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>"OTEL_TRACES_EXPORTER, OTEL_METRICS_EXPORTER, or OTEL_LOGS_EXPORTER — the defaults are already
correctTracerProvider or MeterProvider — AddElasticOpenTelemetry() handles everythingElastic.Apm.*) and EDOT on the same applicationSee the EDOT .NET setup 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-dotnet-instrumentExecute the skills CLI command in your project's root directory to begin installation:
Fetches observability-edot-dotnet-instrument 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-dotnet-instrument. Access via /observability-edot-dotnet-instrument 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
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
296
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
296
stars
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
observability-edot-dotnet-instrument reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added observability-edot-dotnet-instrument from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for observability-edot-dotnet-instrument matched our evaluation — installs cleanly and behaves as described in the markdown.
observability-edot-dotnet-instrument fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for observability-edot-dotnet-instrument matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: observability-edot-dotnet-instrument is focused, and the summary matches what you get after install.
observability-edot-dotnet-instrument reduced setup friction for our internal harness; good balance of opinion and flexibility.
observability-edot-dotnet-instrument has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for observability-edot-dotnet-instrument matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in observability-edot-dotnet-instrument — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 61