Configure Sentry's structured logging feature.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsentry-setup-loggingExecute the skills CLI command in your project's root directory to begin installation:
Fetches sentry-setup-logging from getsentry/sentry-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 sentry-setup-logging. Access via /sentry-setup-logging 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
19
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
19
stars
Configure Sentry's structured logging feature.
Sentry.logger or sentry_sdk.loggerImportant: The SDK versions, API names, and code samples below are examples. Always verify against docs.sentry.io before implementing, as APIs and minimum versions may have changed.
| Platform | Min SDK | Enable Flag | Logger API |
|---|---|---|---|
| JavaScript | 9.41.0+ | enableLogs: true |
Sentry.logger.* |
| Python | 2.35.0+ | enable_logs=True |
sentry_sdk.logger.* |
| Ruby | 5.24.0+ | config.enable_logs = true |
Sentry.logger.* |
grep -E '"@sentry/(nextjs|react|node|browser)"' package.json
Sentry.init({
dsn: "YOUR_DSN",
enableLogs: true,
});
integrations: [
Sentry.consoleLoggingIntegration({ levels: ["warn", "error"] }),
],
Sentry.logger.info("User logged in", { userId: "123" });
Sentry.logger.error("Payment failed", { orderId: "456", amount: 99.99 });
// Template literals (creates searchable attributes)
Sentry.logger.info(Sentry.logger.fmt`User ${userId} purchased ${productName}`);
| Library | Integration | Min SDK |
|---|---|---|
| Consola | Sentry.createConsolaReporter() |
10.12.0+ |
| Console capture | Sentry.consoleLoggingIntegration() |
10.13.0+ |
pip show sentry-sdk | grep Version
sentry_sdk.init(
dsn="YOUR_DSN",
enable_logs=True,
)
from sentry_sdk.integrations.logging import LoggingIntegration
integrations=[LoggingIntegration(sentry_logs_level=logging.INFO)]
from sentry_sdk import logger as sentry_logger
sentry_logger.info("User logged in: {user_id}", user_id="123")
sentry_logger.error("Payment failed", order_id="456", amount=99.99)
from sentry_sdk.integrations.loguru import LoguruIntegration
integrations=[LoguruIntegration(sentry_logs_level=LoggingLevels.INFO.value)]
bundle show sentry-ruby
Sentry.init do |config|
config.dsn = "YOUR_DSN"
config.enable_logs = true
config.enabled_patches << :logger # Optional: capture stdlib Logger
end
Sentry.logger.info("User logged in")
Sentry.logger.error("Payment failed. Order: %{order_id}", order_id: "456")
beforeSendLog: (log) => log.level === "info" ? null : log,
def before_send_log(log, hint):
return None if log["severity_text"] == "info" else log
After enabling logs, emit a test log and check the Sentry Logs dashboard (Explore > Logs):
Sentry.logger.info("Sentry logging test");
| Issue | Solution |
|---|---|
| Logs not appearing | Verify SDK version, check enableLogs/enable_logs is set |
| Too many logs | Use beforeSendLog to filter, reduce captured levels |
| Console not captured | Add consoleLoggingIntegration to integrations array |
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
Useful defaults in sentry-setup-logging — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
sentry-setup-logging is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added sentry-setup-logging from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
sentry-setup-logging fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: sentry-setup-logging is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend sentry-setup-logging for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
sentry-setup-logging reduced setup friction for our internal harness; good balance of opinion and flexibility.
sentry-setup-logging has been reliable in day-to-day use. Documentation quality is above average for community skills.
sentry-setup-logging has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in sentry-setup-logging — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 27