Agent skill
investigate-issues
Investigates identified issues in a LearningAgent session by reading the transcript, determining root causes, and updating issue files with investigation reports.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/investigate-issues
SKILL.md
Investigate Issues
Research identified issues from a LearningAgent session to determine their root causes.
Arguments
$ARGUMENTS is the path to the session log folder (e.g., .deepwork/tmp/agent_sessions/<session_id>/<agent_id>/).
Context
Session log folder structure:
!cat learning_agents/doc/learning_log_folder_structure.md 2>/dev/null
Agent used: !cat $ARGUMENTS/agent_used 2>/dev/null || echo "unknown"
Identified issues to investigate:
!grep -l 'status: identified' $ARGUMENTS/*.issue.yml 2>/dev/null || echo "(none)"
Additional investigation guidelines:
!learning_agents/scripts/cat_agent_guideline.sh $ARGUMENTS issue_investigation
Current Agent State
-------- CURRENT KNOWLEDGE OF AGENT --------
!learning_agents/scripts/generate_agent_instructions_for_session.sh $ARGUMENTS
------ END CURRENT KNOWLEDGE OF AGENT-------
Procedure
If no identified issues are listed above, report that and stop.
Refer back to the conversation_transcript.jsonl file as needed in this process.
Step 1: Investigate Each Issue
For each issue file with status identified:
- Read the issue file to understand what went wrong
- Search the transcript for relevant sections — grep for keywords from
issue_descriptionor locate lines nearseen_at_timestamps - Determine root cause using this taxonomy:
- Knowledge gap: Missing or incomplete content in
core-knowledge.md - Missing documentation: A topic file does not exist or lacks needed detail
- Incorrect instruction: An existing instruction leads the agent to wrong behavior
- Missing runtime context: Information that should have been injected at runtime was absent
- Knowledge gap: Missing or incomplete content in
Step 2: Update Issue Files
For each investigated issue, use Edit to update the issue file:
- Change
status: identifiedtostatus: investigated - Add the
investigation_reportfield:
status: investigated
investigation_report: |
<Root cause analysis with specific transcript line numbers as evidence.
Explain what knowledge gap or instruction deficiency caused the issue.>
Step 3: Summary
Simply say "Session log folder done."
Guardrails
- Do NOT modify the agent's knowledge base — that is the incorporate step's job
- Do NOT change the
issue_description— only add theinvestigation_report - Do NOT skip issues — investigate every
identifiedissue - Be specific about evidence — reference transcript line numbers
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?