Comprehensive monitoring, logging, metrics, tracing, and performance testing implementation for production systems.
Works with
Covers structured logging (Pino/JSON), Prometheus metrics (counters, histograms, gauges), and OpenTelemetry distributed tracing with span instrumentation
Includes Prometheus alerting rule configuration, RED/USE dashboard design patterns, and health check endpoint setup
Provides load testing with k6 and Artillery, application profiling for CPU/memory bottlenecks, and cap
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmonitoring-expertExecute the skills CLI command in your project's root directory to begin installation:
Fetches monitoring-expert from jeffallan/claude-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 monitoring-expert. Access via /monitoring-expert 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
7.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
7.9K
stars
Observability and performance specialist implementing comprehensive monitoring, alerting, tracing, and performance testing systems.
import pino from 'pino';
const logger = pino({ level: 'info' });
// Good — structured fields, includes correlation ID
logger.info({ requestId: req.id, userId: req.user.id, durationMs: elapsed }, 'order.created');
// Bad — string interpolation, no correlation
console.log(`Order created for user ${userId}`);
import { Counter, Histogram, register } from 'prom-client';
const httpRequests = new Counter({
name: 'http_requests_total',
help: 'Total HTTP requests',
labelNames: ['method', 'route', 'status'],
});
const httpDuration = new Histogram({
name: 'http_request_duration_seconds',
help: 'HTTP request latency',
labelNames: ['method', 'route'],
buckets: [0.05, 0.1, 0.3, 0.5, 1, 2, 5],
});
// Instrument a route
app.use((req, res, next) => {
const end = httpDuration.startTimer({ method: req.method, route: req.path });
res.on('finish', () => {
httpRequests.inc({ method: req.method, route: req.path, status: res.statusCode });
end();
});
next();
});
// Expose scrape endpoint
app.get('/metrics', async (req, res) => {
res.set('Content-Type', register.contentType);
res.end(await register.metrics());
});
import { NodeSDK } from '@opentelemetry/sdk-node';
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http';
import { trace } from '@opentelemetry/api';
const sdk = new NodeSDK({
traceExporter: new OTLPTraceExporter({ url: 'http://jaeger:4318/v1/traces' }),
});
sdk.start();
// Manual span around a critical operation
const tracer = trace.getTracer('order-service');
async function processOrder(orderId) {
const span = tracer.startSpan('order.process');
span.setAttribute('order.id', orderId);
try {
const result = await db.saveOrder(orderId);
span.setStatus({ code: SpanStatusCode.OK });
return result;
} catch (err) {
span.recordException(err);
span.setStatus({ code: SpanStatusCode.ERROR });
throw err;
} finally {
span.end();
}
}
groups:
- name: api.rules
rules:
- alert: HighErrorRate
expr: |
rate(http_requests_total{status=~"5.."}[5m])
/ rate(http_requests_total[5m]) > 0.05
for: 2m
labels:
severity: critical
annotations:
summary: "Error rate above 5% on {{ $labels.route }}"
import http from 'k6/http';
import { check, sleep } from 'k6';
export const options = {
stages: [
{ duration: '1m', target: 50 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.
erichowens/some_claude_skills
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
I recommend monitoring-expert for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for monitoring-expert matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: monitoring-expert is focused, and the summary matches what you get after install.
Useful defaults in monitoring-expert — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added monitoring-expert from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
monitoring-expert is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
monitoring-expert reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: monitoring-expert is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for monitoring-expert matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend monitoring-expert for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 36