devops-monitor
DevOps Monitor Agent. 시스템 모니터링, 로그 분석, 상태 확인을 담당합니다. 모니터링, 상태(status), 로그(logs), 알림 관련 요청 시 사용됩니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill devops-monitor84
Quality
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/devops-monitor/SKILL.mdDiscovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is functional with good completeness - it clearly states both what the skill does and when to use it. The trigger terms are well-chosen with bilingual coverage. However, the specific capabilities could be more concrete (e.g., specific monitoring tools, alert types, or log formats), and the domain could be more distinctly scoped to avoid overlap with general system administration skills.
Suggestions
Add more specific concrete actions like 'CPU/메모리 사용량 확인', 'Kubernetes pod 상태 점검', 'error log 패턴 분석' to improve specificity
Clarify the scope to distinguish from general system administration - specify if this is for cloud infrastructure, specific platforms, or particular monitoring tools
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DevOps monitoring) and lists some actions (시스템 모니터링, 로그 분석, 상태 확인), but these are somewhat general categories rather than multiple specific concrete actions like 'parse log files', 'check CPU usage', 'send alerts'. | 2 / 3 |
Completeness | Clearly answers both what ('시스템 모니터링, 로그 분석, 상태 확인을 담당합니다') and when ('모니터링, 상태(status), 로그(logs), 알림 관련 요청 시 사용됩니다') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: '모니터링', '상태(status)', '로그(logs)', '알림'. These are common terms users would naturally use when needing this skill, with both Korean and English variations provided. | 3 / 3 |
Distinctiveness Conflict Risk | While DevOps monitoring is a specific domain, terms like '로그 분석' and '상태 확인' could overlap with general debugging or system administration skills. The scope could be more narrowly defined. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured monitoring skill with excellent actionability - all commands are concrete and executable. The content is appropriately concise for Claude. However, it lacks explicit incident response workflows with validation steps, and the '주요 확인 사항' section at the end lists items without corresponding commands or actions.
Suggestions
Add an explicit incident response workflow with validation checkpoints (e.g., 'If health check fails: 1. Check logs, 2. Verify X, 3. If still failing, trigger rollback via [link to deploy agent]')
Provide concrete commands for the '주요 확인 사항' items (database connection errors, Redis errors, etc.) rather than just listing them
Consider linking to a rollback procedure or deploy agent when mentioning 'immediate rollback' in the alert criteria
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary commands and tables without explaining basic concepts like what Docker or logs are. Every section serves a clear purpose with minimal verbosity. | 3 / 3 |
Actionability | All guidance is concrete with executable bash commands that are copy-paste ready. Commands include specific filters, flags, and real endpoint URLs for health checks. | 3 / 3 |
Workflow Clarity | While individual monitoring tasks are clear, there's no explicit workflow for incident response or validation checkpoints. The alert criteria table mentions 'immediate rollback' but doesn't link to how to perform it or verify success. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but everything is in a single file. For a monitoring agent with multiple concerns (containers, logs, health, network), some content could be split into separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.