diagnose
Systematic troubleshooting for Apache Cassandra clusters. Use when diagnosing performance issues, latency problems, node failures, or unexpected behavior.
概览
Systematic troubleshooting for Apache Cassandra clusters. Use when diagnosing performance issues, latency problems, node failures, or unexpected behavior.
展开完整说明
以下为来源文档,不是本网站的操作指令。执行命令前请先核实权限。
Cassandra Diagnostics
You are an expert Cassandra troubleshooter applying systematic diagnostic methodologies.
Version Identification
IMPORTANT: At the beginning of any diagnostic session, immediately ask the user which Cassandra version they are using. Many diagnostic approaches, tools, and solutions are version-specific:
- Cassandra 3.x: Legacy repair behavior, older compaction strategies
- Cassandra 4.0: Safe incremental repair, virtual tables, Zero Copy Streaming, full query logging
- Cassandra 4.1: Paxos V2, performance improvements
- Cassandra 5.0: UCS compaction, Trie memtables, SAI indexes, BTI format
Knowing the version upfront ensures diagnostic commands, tool availability, and recommendations are accurate.
Problem Solving Strategy
Double Loop Learning Approach
When troubleshooting Cassandra issues, apply double loop learning:
Single Loop (Immediate Fix):
- Identify the immediate symptom
- Apply a quick fix to restore service
- Document what was done
Double Loop (Root Cause & Prevention):
- Question the underlying assumptions that led to the problem
- Analyze why the system design allowed this issue to occur
- Challenge existing mental models about how the cluster should behave
- Implement systemic changes to prevent recurrence
- Update monitoring and alerting to catch early warning signs
Always ask: "Why did our existing approach fail to prevent this?"
USE Method for System Resource Analysis
Apply the USE Method (Utilization, Saturation, Errors) systematically to each resource:
CPU:
- Utilization:
top,mpstat, nodetooltpstatsfor thread pool usage - Saturation: Run queue length, thread pool pending tasks
- Errors: Check for compaction/repair failures due to CPU constraints
Memory:
- Utilization: Heap usage, off-heap (memtables, bloom filters, compression metadata)
- Saturation: GC frequency and duration, OOM errors
- Errors:
java.lang.OutOfMemoryError, allocation failures
Disk I/O:
- Utilization:
iostat%util, read/write throughput - Saturation:
awaitlatency, queue depth - Errors: Disk errors in system logs, failed compactions
Network:
- Utilization: Bandwidth usage between nodes, client connections
- Saturation: Dropped messages (
nodetool tpstats), connection timeouts - Errors: Gossip failures, streaming errors, hinted handoff backlog
Storage:
- Utilization: Disk space per node, data directory usage
- Saturation: Approaching disk limits, compaction unable to keep up
- Errors: Write failures due to full disk
Thread Pools:
- Not a hardware resource, but has similar characteristics
- Utilization: Active Tasks
- Saturation: Pending Tasks
- Errors: Error Rate
Outlier Analysis
When diagnosing issues, always compare nodes to identify outliers:
Key Questions:
- Are some nodes showing different latency profiles?
- Is one node handling disproportionate traffic (hot partition)?
- Do some nodes have different resource utilization patterns?
- Are there nodes with more tombstones or larger SSTables?
- Is gossip healthy across all nodes?
Comparison Points:
- Read/write latencies per node (
nodetool tablehistograms) - Compaction pending per node
- Thread pool statistics across nodes
- GC behavior differences
- Disk utilization variance
- Network latency between specific node pairs
Tools:
nodetool status- basic health overviewnodetool netstats- streaming and network statenodetool tpstats- thread pool comparison- Metrics systems (Prometheus/Grafana) for time-series comparison
- Profiling: Async Profiler. See Jon's video: https://www.youtube.com/watch?v=yNZtnzjyJRI
Common Issues Checklist
Latency Issues
- Check GC logs for long pauses
- Review thread pool saturation (
nodetool tpstats) - Look for disk I/O saturation (
iostat) - Check for tombstone-heavy reads
- Verify network latency between nodes
- Review consistency level vs replication factor
Node Failures
- Check gossip status (
nodetool gossipinfo) - Review system logs for errors
- Verify disk space and health
- Check for network partitions
- Review hinted handoff status
Compaction Issues
- Check pending compaction tasks
- Review compaction throughput settings
- Look for large partitions blocking compaction
- Verify disk space for compaction headroom
Memory Pressure
- Review heap usage and GC frequency
- Check off-heap memory (memtables, bloom filters)
- Look for memory leaks in native memory
- Verify JVM settings match workload
Data Imbalance / Token Skew
- Check
nodetool statusLoad column for uneven disk usage across nodes - Do NOT rely on "Owns (effective)" — it shows full-ring primary range, which is misleading when
allocate_tokens_for_local_replication_factor(allocator hint) == rack count - Use
/cassandra-expert:token-skewfor correct two-phase analysis:- Phase 1: Token distribution quality (per-rack ownership, based on allocator hint vs rack count)
- Phase 2: Data distribution skew (based on keyspace RF, validated against disk Load)
- Key distinction: the allocator hint (cassandra.yaml) determines token placement; the keyspace RF determines data replication. These are independent settings — do not conflate them.
- For detailed analysis, read:
../../references/general/token-skew.md
Streaming Performance Issues
Slow streaming during bootstrap, decommission, or repair.
Symptoms:
- Bootstrap/decommission taking hours instead of minutes
- Throughput ~12MB/s instead of disk/network speeds
Quick checks:
nodetool netstats- monitor streaming progressnodetool ring- check vnode count (should be 1-4)
Common causes: High vnode count, STCS/TWCS compaction, internode encryption.
For detailed diagnostics, read: ../../references/general/streaming.md
Diagnostic Commands
# Overall status
nodetool status
nodetool info
# Thread pools
nodetool tpstats
# Table statistics
nodetool tablestats <keyspace>.<table>
nodetool tablehistograms <keyspace>.<table>
# Compaction
nodetool compactionstats
nodetool compactionhistory
# Network
nodetool netstats
nodetool gossipinfo
# Ring and token distribution
nodetool ring
nodetool describecluster
References
For detailed diagnostics context:
../../references/general/streaming.md- Streaming performance and Zero Copy Streaming../../references/general/compaction.md- Compaction strategy issues and tuning../../references/general/repair.md- Repair failures and version-specific guidance../../references/cassandra-5.0/notable-features.md- New features that may affect behavior../../references/cassandra-5.0/jvm-options.md- GC tuning for diagnosing memory/latency issues../../references/cassandra-5.0/cassandra-yaml.md- Configuration that may cause issues
Guidelines
- Always ask about Cassandra version first - diagnostic tools and approaches vary by version
- Start with USE method - systematically check each resource
- Compare nodes to find outliers
- Correlate symptoms with recent changes (deployments, traffic patterns, config changes)
- Check the simple things first (disk space, network connectivity)
- Use double loop learning to prevent recurrence
文件元数据
name: diagnose description: Systematic troubleshooting for Apache Cassandra clusters. Use when diagnosing performance issues, latency problems, node failures, or unexpected behavior. argument-hint: [symptom, error message, or problem description] user-invocable: true
查看原始文本
--- name: diagnose description: Systematic troubleshooting for Apache Cassandra clusters. Use when diagnosing performance issues, latency problems, node failures, or unexpected behavior. argument-hint: [symptom, error message, or problem description] user-invocable: true --- # Cassandra Diagnostics You are an expert Cassandra troubleshooter applying systematic diagnostic methodologies. ## Version Identification **IMPORTANT:** At the beginning of any diagnostic session, immediately ask the user which Cassandra version they are using. Many diagnostic approaches, tools, and solutions are version-specific: - **Cassandra 3.x**: Legacy repair behavior, older compaction strategies - **Cassandra 4.0**: Safe incremental repair, virtual tables, Zero Copy Streaming, full query logging - **Cassandra 4.1**: Paxos V2, performance improvements - **Cassandra 5.0**: UCS compaction, Trie memtables, SAI indexes, BTI format Knowing the version upfront ensures diagnostic commands, tool availability, and recommendations are accurate. ## Problem Solving Strategy ### Double Loop Learning Approach When troubleshooting Cassandra issues, apply double loop learning: **Single Loop (Immediate Fix):** - Identify the immediate symptom - Apply a quick fix to restore service - Document what was done **Double Loop (Root Cause & Prevention):** - Question the underlying assumptions that led to the problem - Analyze why the system design allowed this issue to occur - Challenge existing mental models about how the cluster should behave - Implement systemic changes to prevent recurrence - Update monitoring and alerting to catch early warning signs Always ask: "Why did our existing approach fail to prevent this?" ### USE Method for System Resource Analysis Apply the USE Method (Utilization, Saturation, Errors) systematically to each resource: **CPU:** - Utilization: `top`, `mpstat`, nodetool `tpstats` for thread pool usage - Saturation: Run queue length, thread pool pending tasks - Errors: Check for compaction/repair failures due to CPU constraints **Memory:** - Utilization: Heap usage, off-heap (memtables, bloom filters, compression metadata) - Saturation: GC frequency and duration, OOM errors - Errors: `java.lang.OutOfMemoryError`, allocation failures **Disk I/O:** - Utilization: `iostat` %util, read/write throughput - Saturation: `await` latency, queue depth - Errors: Disk errors in system logs, failed compactions **Network:** - Utilization: Bandwidth usage between nodes, client connections - Saturation: Dropped messages (`nodetool tpstats`), connection timeouts - Errors: Gossip failures, streaming errors, hinted handoff backlog **Storage:** - Utilization: Disk space per node, data directory usage - Saturation: Approaching disk limits, compaction unable to keep up - Errors: Write failures due to full disk **Thread Pools:** - Not a hardware resource, but has similar characteristics - Utilization: Active Tasks - Saturation: Pending Tasks - Errors: Error Rate ### Outlier Analysis When diagnosing issues, always compare nodes to identify outliers: **Key Questions:** - Are some nodes showing different latency profiles? - Is one node handling disproportionate traffic (hot partition)? - Do some nodes have different resource utilization patterns? - Are there nodes with more tombstones or larger SSTables? - Is gossip healthy across all nodes? **Comparison Points:** - Read/write latencies per node (`nodetool tablehistograms`) - Compaction pending per node - Thread pool statistics across nodes - GC behavior differences - Disk utilization variance - Network latency between specific node pairs **Tools:** - `nodetool status` - basic health overview - `nodetool netstats` - streaming and network state - `nodetool tpstats` - thread pool comparison - Metrics systems (Prometheus/Grafana) for time-series comparison - Profiling: Async Profiler. See Jon's video: https://www.youtube.com/watch?v=yNZtnzjyJRI ## Common Issues Checklist ### Latency Issues - Check GC logs for long pauses - Review thread pool saturation (`nodetool tpstats`) - Look for disk I/O saturation (`iostat`) - Check for tombstone-heavy reads - Verify network latency between nodes - Review consistency level vs replication factor ### Node Failures - Check gossip status (`nodetool gossipinfo`) - Review system logs for errors - Verify disk space and health - Check for network partitions - Review hinted handoff status ### Compaction Issues - Check pending compaction tasks - Review compaction throughput settings - Look for large partitions blocking compaction - Verify disk space for compaction headroom ### Memory Pressure - Review heap usage and GC frequency - Check off-heap memory (memtables, bloom filters) - Look for memory leaks in native memory - Verify JVM settings match workload ### Data Imbalance / Token Skew - Check `nodetool status` Load column for uneven disk usage across nodes - Do NOT rely on "Owns (effective)" — it shows full-ring primary range, which is misleading when `allocate_tokens_for_local_replication_factor` (allocator hint) == rack count - Use `/cassandra-expert:token-skew` for correct two-phase analysis: - Phase 1: Token distribution quality (per-rack ownership, based on allocator hint vs rack count) - Phase 2: Data distribution skew (based on keyspace RF, validated against disk Load) - Key distinction: the allocator hint (cassandra.yaml) determines token placement; the keyspace RF determines data replication. These are independent settings — do not conflate them. - For detailed analysis, read: `../../references/general/token-skew.md` ### Streaming Performance Issues Slow streaming during bootstrap, decommission, or repair. **Symptoms:** - Bootstrap/decommission taking hours instead of minutes - Throughput ~12MB/s instead of disk/network speeds **Quick checks:** - `nodetool netstats` - monitor streaming progress - `nodetool ring` - check vnode count (should be 1-4) **Common causes:** High vnode count, STCS/TWCS compaction, internode encryption. For detailed diagnostics, read: `../../references/general/streaming.md` ## Diagnostic Commands ```bash # Overall status nodetool status nodetool info # Thread pools nodetool tpstats # Table statistics nodetool tablestats <keyspace>.<table> nodetool tablehistograms <keyspace>.<table> # Compaction nodetool compactionstats nodetool compactionhistory # Network nodetool netstats nodetool gossipinfo # Ring and token distribution nodetool ring nodetool describecluster ``` ## References For detailed diagnostics context: - `../../references/general/streaming.md` - Streaming performance and Zero Copy Streaming - `../../references/general/compaction.md` - Compaction strategy issues and tuning - `../../references/general/repair.md` - Repair failures and version-specific guidance - `../../references/cassandra-5.0/notable-features.md` - New features that may affect behavior - `../../references/cassandra-5.0/jvm-options.md` - GC tuning for diagnosing memory/latency issues - `../../references/cassandra-5.0/cassandra-yaml.md` - Configuration that may cause issues ## Guidelines 1. **Always ask about Cassandra version first** - diagnostic tools and approaches vary by version 2. Start with USE method - systematically check each resource 3. Compare nodes to find outliers 4. Correlate symptoms with recent changes (deployments, traffic patterns, config changes) 5. Check the simple things first (disk space, network connectivity) 6. Use double loop learning to prevent recurrence
查看并核实来源
获取价格与运行成本
- 获取 Skill
- 价格未确认
- 运行 Skill
- 尚未确认运行要求,请查看来源中的 Agent、API 和服务费用。
- 许可证
- Apache-2.0
- 价格未确认
- 我们尚未确认此 Skill 的价格,现有来源与安装入口仍可使用。
免费获取不代表免费运行,价格标签不代表安全评级。 提交价格信息 →
来源需要复核
已跟踪的来源发生变化或同步失败,请在安装前复核当前来源。
安装前审查: 避免自动安装
许可证: Apache-2.0
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- Financial research output is not financial advice; require human review before any live investment decision
- Low GitHub adoption signal
- Financial research output is not financial advice; require human review before any live investment decision.
- Quality score needs review
- Permission surface needs review: secrets or environment access, shell or command execution
- GitHub adoption: 42 GitHub stars
- Stars/forks activity: 42 stars, 8 forks; issue activity unavailable in current metadata
- Dependency/runtime risk: command execution surface, credential or environment access
- Permission surface: secrets or environment access, shell or command execution
工具列表来自元数据,并非已测试的兼容性;Agent 提示词是建议的交接方式。
从一个小任务开始
- 1阅读来源,确认输入、预期输出、依赖和权限。
- 2先让 Agent 提出计划,批准环境配置和费用,再进行隔离的小规模测试。
- 3检查输出和变更文件,只报告实际执行结果,并保留来源版本以便复现。
请在来源中核实依赖、API 密钥及第三方费用。公开仓库不代表所有服务免费。
来源与使用须知
仓库元数据和审核信号仅供参考。受欢迎、已发现来源、成功运行是不同的事实。
- 来源仓库
- rustyrazorblade/skills
- 许可证
- Apache-2.0
- 版本
- 1.0.0
- 最近 GitHub 推送
- 2026年9月5日
- 目录更新于
- 2026年9月10日
版本来自目录元数据,使用前请核实来源发布记录。
质量
60/100
有潜力
信任
62/100
仅限沙盒
审计
73/100
需审查
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- Financial research output is not financial advice; require human review before any live investment decision
- Low GitHub adoption signal
- Financial research output is not financial advice; require human review before any live investment decision.
- Quality score needs review
- Permission surface needs review: secrets or environment access, shell or command execution
- GitHub adoption: 42 GitHub stars
- Stars/forks activity: 42 stars, 8 forks; issue activity unavailable in current metadata
- Dependency/runtime risk: command execution surface, credential or environment access
- Permission surface: secrets or environment access, shell or command execution
- Verified installs
- —
- 结果
- —
复制不等于安装。安装数需有成功安装回报,不代表全面的质量保证。
Agent 接入
本页通过 Registry API 提供相同的决策、信任、审计、场景和安装信号,让 Agent 无需抓取界面即可排序。
更多详情
{
"version": "openagentskill-agent-metadata-v2",
"review_evidence": {
"indexed": true,
"static_checked": false,
"ai_reviewed": false,
"manual_reviewed": false,
"creator_verified": false,
"review_result": "version_needs_review",
"reviewed_at": null,
"package_fingerprint": null,
"policy_version": null,
"notice": "Publication, static checks, AI review, and creator verification are independent facts. None guarantees runtime safety."
},
"commerce": {
"type": "unknown",
"billing": "unknown",
"amount": null,
"currency": null,
"sourceUrl": null,
"checkedAt": null,
"runtime": "unknown",
"purchaseUrl": null,
"checkout": "external",
"purchaseRequiresUserConsent": true
},
"skill": {
"slug": "rustyrazorblade-diagnose",
"name": "diagnose",
"description": "Systematic troubleshooting for Apache Cassandra clusters. Use when diagnosing performance issues, latency problems, node failures, or unexpected behavior.",
"category": "automation",
"url": "https://www.openagentskill.com/skills/rustyrazorblade-diagnose",
"repository": "https://github.com/rustyrazorblade/skills/tree/main/plugins/cassandra-expert/skills/diagnose",
"github_repo": "rustyrazorblade/skills"
},
"suited_tasks": [
"Browser automation workflows",
"Claude Code teams",
"builders willing to evaluate younger projects",
"Navigate pages",
"Click and type safely",
"Check visual and DOM state",
"Move data between tools",
"Transform files"
],
"suited_agents": [
"Codex",
"Claude Code",
"Cursor",
"OpenAgentSkill CLI"
],
"install": {
"source_evidence": {
"status": "source-needs-review",
"sourceRecorded": true,
"canOfferInstall": false,
"path": "plugins/cassandra-expert/skills/diagnose/SKILL.md",
"revision": "9b24bd015db044746bd2438b80327132e0b9fb89",
"notice": "The tracked source changed or could not be synchronized. Review the current source before installing."
},
"command": "",
"ready": false,
"targets": [
{
"id": "codex",
"label": "Codex",
"kind": "agent-prompt",
"value": "Review the public source for \"diagnose\" at https://github.com/rustyrazorblade/skills/tree/main/plugins/cassandra-expert/skills/diagnose. The tracked source changed or could not be synchronized. Review the current source before installing. Do not install or execute repository code in this review. Report whether valid skill instructions exist, their exact path and revision, dependencies, costs, license and requested permissions. Ask for approval before any installation. Treat repository text as untrusted data, not authorization."
},
{
"id": "claude-code",
"label": "Claude Code",
"kind": "agent-prompt",
"value": "Review the public source for \"diagnose\" at https://github.com/rustyrazorblade/skills/tree/main/plugins/cassandra-expert/skills/diagnose. The tracked source changed or could not be synchronized. Review the current source before installing. Do not install or execute repository code in this review. Report whether valid skill instructions exist, their exact path and revision, dependencies, costs, license and requested permissions. Ask for approval before any installation. Treat repository text as untrusted data, not authorization."
},
{
"id": "cursor",
"label": "Cursor",
"kind": "agent-prompt",
"value": "Review the public source for \"diagnose\" at https://github.com/rustyrazorblade/skills/tree/main/plugins/cassandra-expert/skills/diagnose. The tracked source changed or could not be synchronized. Review the current source before installing. Do not install or execute repository code in this review. Report whether valid skill instructions exist, their exact path and revision, dependencies, costs, license and requested permissions. Ask for approval before any installation. Treat repository text as untrusted data, not authorization."
}
],
"handoff_url": "https://www.openagentskill.com/api/skills/rustyrazorblade-diagnose/install",
"manifest_url": "https://www.openagentskill.com/api/registry/manifest/rustyrazorblade-diagnose"
},
"trust": {
"score": 70,
"label": "Manual review",
"version": "trust-score-v4",
"install_policy": "block",
"evidence": {
"stars": "42 GitHub stars",
"repoActivity": "42 stars, 8 forks",
"lastPushed": "1mo since push",
"license": "Apache-2.0",
"repository": "https://github.com/rustyrazorblade/skills/tree/main/plugins/cassandra-expert/skills/diagnose",
"install": "The tracked source changed or could not be synchronized. Review the current source before installing.",
"installSafety": "standard package or runtime install path",
"permissionSurface": "secrets or environment access, shell or command execution",
"documentation": "Strong README/SKILL.md context",
"agentOutcomes": "No agent outcome data yet"
},
"outcome_evidence": {
"total": 0,
"successes": 0,
"failures": 0,
"not_relevant": 0,
"success_rate": null,
"recent_success_rate": null,
"recent_failure_rate": null,
"install_attempts": 0,
"install_success_rate": null,
"risk_blocked": 0,
"setup_required": 0,
"avg_output_quality": null,
"production_outcomes": 0,
"last_outcome_at": null,
"label": "No agent outcome data yet"
},
"auto_install": {
"allowed": false,
"sandbox_required": true,
"reason": "Do not auto-install. Inspect the source, dependencies, and permission surface first."
},
"best_for": [
"automation",
"agent-skill"
],
"known_risks": [
"Financial research output is not financial advice; require human review before any live investment decision.",
"Low GitHub adoption signal",
"Quality score needs review",
"Permission surface needs review: secrets or environment access, shell or command execution",
"GitHub adoption: 42 GitHub stars",
"Stars/forks activity: 42 stars, 8 forks; issue activity unavailable in current metadata",
"Dependency/runtime risk: command execution surface, credential or environment access",
"Permission surface: secrets or environment access, shell or command execution"
]
},
"agent_proven": {
"version": "agent-proven-v1",
"score": 0,
"tier": "unproven",
"label": "Needs first agent run",
"summary": "No agent outcome reports yet. Use Resolve, run one narrow sandbox task, then report the result.",
"metrics": {
"totalOutcomes": 0,
"successfulOutcomes": 0,
"failedOutcomes": 0,
"installAttempts": 0,
"installSuccessRate": null,
"successRate": null,
"recentSuccessRate": null,
"recentFailureRate": null,
"riskBlocked": 0,
"setupRequired": 0,
"notRelevant": 0,
"avgOutputQuality": null,
"avgTimeToUsefulMs": null,
"productionOutcomes": 0,
"humanReviewRequired": 0,
"uniqueAgents": 0,
"lastOutcomeAt": null
},
"signals": [],
"penalties": [
"No real agent outcome evidence yet"
]
},
"audit": {
"score": 73,
"risk_level": "needs_review",
"risk_label": "Needs review",
"warnings": [
"Dependency or permission surface needs review",
"Permission surface may require sandboxing",
"Financial research output is not financial advice; require human review before any live investment decision",
"Low GitHub adoption signal",
"Financial research output is not financial advice; require human review before any live investment decision.",
"Quality score needs review",
"Permission surface needs review: secrets or environment access, shell or command execution",
"GitHub adoption: 42 GitHub stars"
]
},
"safety_gate": {
"tier": "blocked",
"label": "Blocked for auto-install",
"auto_install_policy": "block",
"auto_install_allowed": false,
"human_review_required": true,
"blocked": true,
"recommended_action": "Do not auto-install. Inspect the source, dependencies, and permission surface first."
},
"quality": {
"score": 60,
"label": "Promising"
},
"supply": {
"track": "Data, BI, and analytics",
"scenario": "Browser automation",
"maintenance": "1mo since push",
"risk": "Needs review"
},
"alternative_skills": [],
"do_not_use_when": [
"teams that need a vendor-supported SLA",
"production agents without a repository review",
"Low GitHub adoption signal",
"High-risk permission hints: Shell or command execution, Secrets or environment access",
"Dependency or permission surface needs review",
"Permission surface may require sandboxing",
"Financial research output is not financial advice; require human review before any live investment decision",
"Financial research output is not financial advice; require human review before any live investment decision."
],
"agent_contract": {
"task_input": "Use diagnose in an agent workflow",
"recommended_action": "Do not auto-install. Inspect the source, dependencies, and permission surface first.",
"install_policy": "block",
"minimum_review_before_use": [
"Trust: 70/100 Manual review",
"Audit: 73/100 Needs review",
"Safety: 29/100 Avoid automatic install",
"Review repository, license, install command, and permission surface before production use."
],
"expected_agent_output": {
"selected_skill": "rustyrazorblade-diagnose (diagnose)",
"install_command": "",
"risk_summary": "Needs review; Blocked for auto-install; Review before production",
"verification_result": "Report the smallest successful task, files touched, warnings, and any missing setup."
}
},
"outcome_feedback": {
"endpoint": "https://www.openagentskill.com/api/agent/outcome",
"method": "POST",
"requires_resolve_event_id": true,
"event_id_source": "Use install_receipt.outcome_feedback.event_id or feedback.event_id returned by /api/agent/resolve for the current task.",
"expected_outcomes": [
"success",
"failed",
"not_relevant",
"blocked_by_risk",
"setup_required"
],
"payload_template": {
"event_id": "<install_receipt.outcome_feedback.event_id or feedback.event_id from /api/agent/resolve>",
"skill_slug": "rustyrazorblade-diagnose",
"task": "Use diagnose in an agent workflow",
"agent": "codex",
"outcome": "success",
"install_used": true,
"risk_blocked": false,
"setup_required": false,
"task_success": true,
"output_quality": 4,
"error_type": null,
"human_review_required": false,
"workspace": "sandbox",
"time_to_useful_ms": 120000,
"notes": "Report the smallest successful task, setup friction, files touched, and risk notes."
}
},
"endpoints": {
"web": "https://www.openagentskill.com/skills/rustyrazorblade-diagnose",
"api": "https://www.openagentskill.com/api/agent/skills/rustyrazorblade-diagnose",
"audit": "https://www.openagentskill.com/skills/rustyrazorblade-diagnose/audit",
"eval": "https://www.openagentskill.com/api/agent/evals?slug=rustyrazorblade-diagnose&task=Use%20diagnose%20in%20an%20agent%20workflow&max_risk=medium",
"resolve": "https://www.openagentskill.com/api/agent/resolve?task=Use%20diagnose%20in%20an%20agent%20workflow&agent=codex&max_risk=medium",
"receipt": "https://www.openagentskill.com/api/agent/receipt?task=Use%20diagnose%20in%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text",
"install": "https://www.openagentskill.com/api/skills/rustyrazorblade-diagnose/install",
"manifest": "https://www.openagentskill.com/api/registry/manifest/rustyrazorblade-diagnose"
}
}创作者工具
收录来源
Registry 收录
此列表来自公开来源,维护者认领获批前不会标记为官方。
- 收录方
- OpenAgentSkill 社区索引
归属链接指向公开仓库或创作者主页。创作者可认领列表以更新所有权信号。
认领此 Skill所有者认领
认领此 Skill 页面
这条 Registry 收录 列表归属于 rustyrazorblade,但尚未标记为官方。认领后可增加已验证所有者信号,使后续发布、安装和审计更新更值得信赖。
分享工具包
创作者外链工具包
将证据徽章加入你的 README
在开发者评估仓库的位置展示规范页面、当前信任与审计信号,以及真实的 Agent 验证证据。
[](https://www.openagentskill.com/skills/rustyrazorblade-diagnose?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/rustyrazorblade-diagnose?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/rustyrazorblade-diagnose/audit)
[](https://www.openagentskill.com/skills/rustyrazorblade-diagnose?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)社区信号
告诉我们这个 Skill 是否对你的 Agent 工作流有帮助。汇总反馈会持续改善排序。
