intake-report

Extract structured details from bug reports and create beads issues.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kirvin/agent-dev-harness --skill intake-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intake-report
Source: https://github.com/kirvin/agent-dev-harness/tree/main/plugins/kf/skills/intake-report
Command: npx skills add https://github.com/kirvin/agent-dev-harness --skill intake-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The intake-report skill resolves the issue of inconsistent and incomplete bug reports by automating the extraction of structured details from pasted error logs or verbal descriptions, creating a beads issue, and guiding the fix process.

Core Features & Use Cases

  • Structured Bug Report Extraction: Extracts details such as affected component, reported and expected behaviors, reproduction steps, and severity from various input sources.
  • Automated Issue Creation: Creates a beads issue with the extracted details to ensure traceability and to anchor the report to the fix.
  • Fix Workflow Guidance: Provides a clear protocol for developers to follow from claiming an issue to closing it with findings, enhancing productivity and consistency.

Quick Start

Paste your error log into the chat, and the intake-report skill will create a new beads issue for you.

Frequently Asked Questions about intake-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically extract structured details from a bug report?

Automated bug report intake extracts affected component, reported behavior, expected behavior, reproduction steps, and severity from pasted error logs or verbal descriptions, then creates a corresponding issue for traceability.

What is the best way to create a traceable issue from an error log in chat?

Paste your error log directly into the chat and the skill automatically extracts the structured details and creates a beads issue, anchoring the bug report to a documented fix.

Can I use automated intake for bug reports reported conversationally by developers?

Yes, automated intake works in environments where developers report bugs directly via conversation, extracting structured data from verbal descriptions and creating a beads issue to ensure the report leads to a documented fix.

Does automated issue creation provide guidance for the bug fix workflow?

Yes, after creating a beads issue, the skill provides a clear protocol guiding developers from claiming the issue through closing it with findings, enhancing productivity and consistency across the fix workflow.

What problem does structured data extraction from bug reports solve?

Structured data extraction resolves the issue of inconsistent and incomplete bug reports by automatically pulling affected component, severity, and reproduction steps from pasted error logs, ensuring every report is complete and traceable.

When do I need automated intake for issue tracking?

You need automated intake when bug reports are inconsistent or incomplete, and you want to ensure every reported issue is extracted into structured data, created in a tracking system, and anchored to a documented fix.