Bug Intake

Organization

greenfield-inc

bug-intake

Use when the person reports broken behaviour or starts a session to file a bug. Reproduces and reports. Never fixes.

Overview

Publisher	greenfield-inc
Repository	`Pane`
Skill name	`bug-intake`
Stars	529
Forks	227
Bundled files	1
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by greenfield-inc on GitHub. Read the source before you install it.

Installation

Install the Bug Intake AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/greenfield-inc/Pane/tree/main/main/src/services/paneChatBundle/skills/bug-intake
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/greenfield-inc/Pane/tree/main/main/src/services/paneChatBundle/skills/bug-intake

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/greenfield-inc/Pane.git /tmp/Pane
mkdir -p .claude/skills
cp -r /tmp/Pane/main/src/services/paneChatBundle/skills/bug-intake .claude/skills/bug-intake

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bug Intake in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bug Intake on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bug Intake is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Bug intake

The goal is a report someone else can act on. The first move is reproduction, not theory.

Steps

Restate the symptom in one sentence and confirm it with the person. Get the environment, the account or record involved, and when it started.
Reproduce it.
- If it needs the running app, reproduce it with the verify-app skill, yourself or through a subagent given the steps to attempt, and collect screenshots, console output, and network failures.
- Otherwise give a fresh-context subagent one question at a time to answer with the gather-evidence skill: find the failing test, collect logs, trace the code path, list touched files. Give it the question and a fresh context, not this conversation.
Interpret the evidence yourself. Classify the failure early: compile, logic, race, state, integration, environment, or interface. Write three to five ranked hypotheses before reading deeply, then test them against the code and its recent history. Compare a broken path with a working one when you can. Drop a theory once the evidence rules it out, and leave choosing the fix to whoever takes the report. If only diagnostic logging would settle it, say exactly what you would add and ask first.
Write the success definition: the bug is gone when what is observably true.
Choose a route:
- direct-to-implementation: obvious locus, contained change, tests exist. The report can serve as the whole task for an implementation session.
- options-first: unclear locus, or fixing it forces a design choice. It goes to a planning session.
- cannot-reproduce: say what was tried and what evidence would help. Stay in intake.
File the report wherever the person tracks work (a GitHub issue, Linear, or another tracker). With no tracker, save it as index.html in a bundle of its own in the format at references/bug-report.md, rendered with the page house standard, then stop.

Banned

Fixes, patches, "quick" changes, refactors
Writing a plan
Presenting a hypothesis as the confirmed cause without evidence

If the person then says "fix it"

Hand it on. For direct-to-implementation, tell them to start an implementation session with the report as its source. For options-first, tell them to take the report to a planning session.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/bug-report.md1 KB

Frequently asked questions

What does the Bug Intake AI skill do?

Use when the person reports broken behaviour or starts a session to file a bug. Reproduces and reports. Never fixes.

Why use Bug Intake on TypingMind?

Because you install it once and use it with any model. Bug Intake is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bug Intake in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/greenfield-inc/Pane/tree/main/main/src/services/paneChatBundle/skills/bug-intake. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Bug Intake?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bug Intake?

As many as you like. As long as a model supports skills, you can use Bug Intake with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bug Intake AI skill free?

It is published on GitHub by greenfield-inc. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Debugging

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…

Openclaw Live Updater

openclaw

OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Bug intake

Steps

Banned

If the person then says "fix it"

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now