CommunityCoding & Developmentgithub.com

Mining Field Diagnosis

Integrates on-site mine records, monitoring changes, and applicable standards to compare likely causes, identify key evidence gaps, and propose review paths that can distinguish interpretations. Suitable for preliminary field issue assessment, cause investigation, standard clause verification, and disposal strategy discussions.

What is Mining Field Diagnosis?

This AI agent skill, named 'Mining Field Diagnosis', helps developers and users systematically analyze on-site mining problems by moving from vague speculation to evidence-based investigation. It is particularly useful for field engineers and safety inspectors who need to quickly identify possible causes of incidents, compare competing explanations against on-site conditions, and verify compliance with regulatory standards. The skill supports platforms like Claude Code, Cursor, or Codex and operates by first reading relevant inputs (e.g., phenomenon descriptions, monitoring records, equipment status), then applying a structured workflow: distinguishing verified facts from statements and instrument clues, comparing candidate causes, verifying standard versions and applicability, and finally proposing the most valuable review directions. It also provides optional resources (references/methods.md and assets/diagnosis-note.md) for deeper analysis and structured documentation, ensuring transparency about uncertainties and prioritizing immediate safety actions over delayed investigation.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/79109/agent-skills-test/tree/HEAD/skill/mining-field-diagnosis

Installed? Explore more Coding & Development skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

What does Mining Field Diagnosis do?

Focuses the investigation on "what could be the cause, how to judge it, and what to check next," transforming vague guesses about field issues into evidence-based investigation directions.

Core Capabilities

  • Compare competing explanations: Analyze multiple possible causes based on on-site conditions, retaining supporting and opposing evidence.
  • Map facts to standards: Check standard versions, scope of application, and actual evidence, highlighting non-compliance or missing conditions.
  • Prioritize key issues: Select the review actions that best distinguish between candidate causes, reducing aimless repetitive checks.

Getting Started

Read the phenomenon description, time and location, excavation or support conditions, monitoring records, equipment status, and measures already taken. Determine whether the user needs cause analysis, standard clause verification, or disposal strategy discussion; directly analyze parts with sufficient evidence, and ask targeted questions for critical gaps.

Immediate obvious dangers should be handled by on-site personnel and professionals following current emergency procedures, and disposal cannot be delayed while waiting for cause investigation or full standard verification.

Workflow

  1. First, distinguish between verified facts, personnel statements, and instrument clues.
  2. Compare candidate causes based on the problem mechanism, seeking observations that can distinguish explanations.
  3. When standard verification is needed, check the version, effective time, and applicable conditions, then match with on-site facts.
  4. Propose the most valuable review directions, preserving uncertainties in cause and compliance judgments.

Use Resources as Needed

  • For method selection, boundary judgment, or complex situations: Read references/methods.md.
  • For quickly organizing deliverables, copy and tailor assets/diagnosis-note.md; this is an optional starting point, not a fixed output format.

Deliverables

First, explain the judgments currently supported, then present the main candidate causes, key evidence, and priority review directions. When standards are involved, include necessary clause correspondences; do not force compliance checklists for tasks not involving standards.

Conclusions should be easy for professionals to review and do not replace on-site approval, acceptance, or resumption decisions. If the final cause is not determined, clearly express the uncertainty and the next steps that can advance the judgment.

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

Related Skills