Use when monitor and analyze skill effectiveness in real-time. Track
Scanned 9/8/2026
Install to Claude Code
npx -y skills add oyi77/1ai-skills --skill skill-performance-monitor --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Skill Performance Monitor?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oyi77-skill-performance-monitor)More formats (shields.io, HTML) on the badges page.
---
name: skill-performance-monitor
description: Use when monitor and analyze skill effectiveness in real-time. Track
usage, success rates, response quality, and user satisfaction for continuous optimization.
Use when monitoring and analyze skill effectiveness in real-time. track usage, success.
domain: core
author: oyi77
license: Apache-2.0
subdomain: core-platform
tags:
- infrastructure
- memory
- monitor
- performance
- self-improvement
- skill
version: 1.0.0
category: core
---
persona:
name: "Brendan Gregg"
title: "The Performance Engineering Expert - Master of Metrics"
expertise: ['Performance Monitoring', 'Metrics', 'Observability', 'Analytics']
philosophy: "If you can't measure it, you can't improve it."
credentials: ['Netflix Senior Performance Engineer', "Author of 'Systems Performance'", 'Created performance methodologies']
principles: ['Measure what matters', 'Alert on symptoms', 'Analyze root causes', 'Optimize iteratively']
# Skill Performance Monitor
## Anti-Rationalization Table
| Rationalization | Reality |
|---|---|
| "I'll figure it out as I go" | A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |
| "I already know this topic" | Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |
| "This doesn't apply to my situation" | The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |
| "One more tool will fix it" | Adding complexity rarely solves process gaps. Master the core workflow first. |
## When to Use
**Trigger phrases:**
- "skill performance monitor"
- "Help me with skill performance monitor"
**Use cases:**
- When the task matches this skill's domain expertise
**When NOT to use:**
- For tasks outside this skill's scope
## Overview
Monitor skill performance in real-time. Track usage patterns, success rates, response quality, and user satisfaction. Use data-driven insights to optimize skill selection and improve overall system effectiveness.
**Purpose**: Real-time skill analytics
**Target**: All 1ai-skills
**Output**: Optimization recommendations
---
## Core Functions
- Primary operation execution with input validation
- Error detection and automatic recovery
- Output formatting and quality assurance
- Integration hooks for downstream consumers
### 1. Usage Tracking
```
Track:
- How often each skill is used
- When skills are selected
- Success/failure of skill tasks
- Time to complete tasks
```
### 2. Quality Metrics
```
Measure:
- Response accuracy
- User satisfaction scores
- Task completion rates
- Error rates
```
### 3. Pattern Analysis
```
Identify:
- Peak usage times
- Popular skill combinations
- Failed skill matches
- Improvement opportunities
```
### 4. Optimization
```
Recommend:
- Better skill keywords
- New skill integrations
- Workflow improvements
- Training data
```
---
## Implementation
1. Initialize the skill context with required configuration
2. Load any dependencies or connected services
3. Execute the primary operation
4. Handle errors gracefully with fallback strategies
5. Return structured results for consumption
### Task Logger
```typescript
class SkillPerformanceMonitor {
async logTask(task) {
const log = {
taskId: uuid(),
timestamp: Date.now(),
userRequest: task.input,
matchedSkill: task.skill,
success: task.success,
duration: task.endTime - task.startTime,
feedback: task.userFeedback, // 1-5 stars
error: task.error
};
await this.saveToDatabase(log);
}
}
```
### Analytics Engine
```typescript
async function analyzePerformance(skillName) {
const logs = await getSkillLogs(skillName);
const metrics = {
usage: logs.length,
successRate: logs.filter(l => l.success).length / logs.length,
avgDuration: logs.reduce((a, b) => a + b.duration, 0) / logs.length,
userRating: logs.reduce((a, b) => a + b.feedback, 0) / logs.filter(l => l.feedback).length,
errors: logs.filter(l => l.error).map(l => l.error)
};
return metrics;
}
```
### Optimization Recommendations
```typescript
async function getRecommendations() {
const skills = await getAllSkills();
const recommendations = [];
for (const skill of skills) {
const metrics = await analyzePerformance(skill.name);
// Check for issues
if (metrics.successRate < 0.7) {
recommendations.push({
type: 'fix',
skill: skill.name,
issue: `Low success rate: ${(metrics.successRate * 100).toFixed(1)}%`,
action: 'Improve skill prompts or keywords'
});
}
if (metrics.usage === 0) {
recommendations.push({
type: 'remove',
skill: skill.name,
issue: 'Unused skill',
action: 'Consider removing or promoting'
});
}
if (metrics.userRating && metrics.userRating < 3) {
recommendations.push({
type: 'improve',
skill: skill.name,
issue: `Low rating: ${metrics.userRating.toFixed(1)}/5`,
action: 'Review and enhance responses'
});
}
}
return recommendations;
}
```
---
## Metrics Dashboard
This section covers metrics dashboard for the skill-performance-monitor skill.
Key operations include input validation, core processing, and output verification.
Refer to the skill overview for detailed usage instructions.
### Per-Skill Metrics
| Metric | Good | Warning | Critical |
|--------|------|---------|----------|
| Success Rate | >90% | 70-90% | <70% |
| Avg Duration | <30s | 30-60s | >60s |
| User Rating | >4 | 3-4 | <3 |
| Usage/Week | >10 | 1-10 | 0 |
### System Metrics
| Metric | Target |
|--------|--------|
| Overall Success Rate | >85% |
| Average Response Time | <30s |
| User Satisfaction | >4/5 |
| Skill Match Rate | >90% |
---
## Analytics Views
This section covers analytics views for the skill-performance-monitor skill.
Key operations include input validation, core processing, and output verification.
Refer to the skill overview for detailed usage instructions.
### Skill Leaderboard
```typescript
async function getLeaderboard() {
const skills = await getAllSkills();
const rankings = await Promise.all(
skills.map(async s => ({
skill: s.name,
score: await calculateScore(s)
}))
);
return rankings.sort((a, b) => b.score - a.score);
}
```
### Trend Analysis
```typescript
async function getTrends(days = 7) {
const logs = await getLogsSince(days);
return {
mostUsed: countBy(logs, 'skill').top(5),
mostSuccessful: filterBy(logs, 'success').top(5),
trending: calculateTrend(logs),
issues: detectAnomalies(logs)
};
}
```
---
## Auto-Optimization
This section covers auto-optimization for the skill-performance-monitor skill.
Key operations include input validation, core processing, and output verification.
Refer to the skill overview for detailed usage instructions.
### Triggered Actions
```typescript
const autoActions = {
// If success rate drops below threshold
lowSuccess: {
threshold: 0.7,
action: 'alert',
notify: true
},
// If skill unused for extended period
unused: {
threshold: 30 * 24 * 60 * 60 * 1000, // 30 days
action: 'recommend',
suggestion: 'Consider deprecating or promoting'
},
// If error rate spikes
errorSpike: {
threshold: 0.2,
action: 'fix',
autoApply: false
}
};
```
### Learning Integration
```typescript
async function improveFromFeedback(feedback) {
// Learn from user corrections
if (feedback.correctedSkill) {
await addToKeywordMapping(
feedback.userRequest,
feedback.correctedSkill
);
}
// Learn from success
if (feedback.success && feedback.confident) {
await addToTrainingData(feedback);
}
}
```
---
## Reporting
This section covers reporting for the skill-performance-monitor skill.
Key operations include input validation, core processing, and output verification.
Refer to the skill overview for detailed usage instructions.
### Daily Report
```typescript
async function generateDailyReport() {
const stats = await getTodayStats();
return `
## Daily Skill Performance Report
**Date**: ${new Date().toDateString()}
### Usage
- Total tasks: ${stats.total}
- Successful: ${stats.success} (${stats.successRate}%)
- Failed: ${stats.failed}
### Top Skills
${stats.topSkills.map(s => `- ${s.name}: ${s.usage} uses`).join('\n')}
### Issues
${stats.issues.map(i => `- ${i.skill}: ${i.issue}`).join('\n') || 'None'}
### Recommendations
${stats.recommendations.map(r => `- ${r}`).join('\n') || 'None'}
`;
}
```
---
## Integration
- Connects with existing toolchain via standard interfaces
- Supports webhook-based event notifications
- Compatible with CI/CD pipelines for automated workflows
- Provides structured output for downstream consumption
### With Runtime-Self-Improvement
```
Monitor:
- Track skill performance
- Detect improvements
- Feed back to self-improvement
Loop:
1. Monitor → 2. Analyze → 3. Improve → 4. Monitor
```
### With Auto-Git-Committer
```
On optimization:
1. Apply improvements
2. Track new metrics
3. Commit changes
4. Monitor impact
```
### With Heartbeat
```
Periodic checks:
1. Get current metrics
2. Compare to baseline
3. Alert on anomalies
4. Recommend improvements
```
---
## Best Practices
This section covers best practices for the skill-performance-monitor skill.
Key operations include input validation, core processing, and output verification.
Refer to the skill overview for detailed usage instructions.
### Do's
✅ Track everything initially
✅ Review metrics daily
✅ Act on warnings
✅ Keep historical data
✅ Share insights with user
### Don'ts
❌ Don't over-optimize
❌ Don't remove skills without backup
❌ Don't ignore low usage
❌ Don't rely only on metrics
---
## Version History
- **v1.0** (2026-02-27) - Initial creation
---
## When NOT to Use
- When monitoring collects data subject to employee privacy regulations
- When performance metrics are used for compensation decisions
- When the task is too trivial to warrant this skill
- When a more appropriate skill exists
## Common Rationalizations
| Rationalization | Reality |
|---|---|
| "I'll do this later" | Explain why this excuse is wrong for this skill |
| "This is simple, skip steps" | Even simple tasks benefit from process |
## Red Flags
- Monitoring collects metrics without actionable alerting thresholds
- Agent does not distinguish between leading and lagging indicators
- Watch for shortcuts and skipped steps
## Verification
After completing this skill, confirm:
- [ ] Alerting thresholds are actionable, not just informational
- [ ] Leading indicators are distinguished from lagging indicators
- [ ] All required outputs generated
- [ ] Success criteria met
## Related Skills
- [runtime-self-improvement](../runtime-self-improvement/SKILL.md) - Apply improvements
- [auto-git-commiter](../auto-git-commiter/SKILL.md) - Commit changes
- [self-improving](../self-improving/SKILL.md) - Learn and improve
## Process
1. Analyze the task requirements
2. Apply domain expertise
3. Verify output quality
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!