Report Environment Issue

Organization

DasDigitaleMomentum

report-environment-issue

Record environment, harness, or tooling issues that block or degrade agent work into an append-only, deduplicated log so the environment can be improved incrementally.

Overview

Publisher	DasDigitaleMomentum
Repository	`opencode-processing-skills`
Skill name	`report-environment-issue`
Stars	61
Forks	3
Bundled files	1
License	MIT
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 DasDigitaleMomentum on GitHub. Read the source before you install it.

Installation

Install the Report Environment Issue 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/DasDigitaleMomentum/opencode-processing-skills/tree/main/skills/report-environment-issue
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/DasDigitaleMomentum/opencode-processing-skills/tree/main/skills/report-environment-issue

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/DasDigitaleMomentum/opencode-processing-skills.git /tmp/opencode-processing-skills
mkdir -p .claude/skills
cp -r /tmp/opencode-processing-skills/skills/report-environment-issue .claude/skills/report-environment-issue

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

Use it in TypingMind

Enable Report Environment Issue 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 Report Environment Issue 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 Report Environment Issue 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.

Skill: Report Environment Issue

Capture issues that are outside the current work package's control, so recurring environment friction becomes visible and can be improved over time.

When to Use

Use when work is blocked or degraded by the environment rather than by the product code or gated scope, for example:

missing tool, binary, permission, or credential
sandbox, network, proxy, or filesystem restriction
installer, path, symlink, or harness configuration problem
tool, MCP, or browser provider failure or flakiness
provider, model, or runtime constraint

Do not use for product bugs, review findings, plan changes, or user-owned decisions. Those keep their own workflows.

Execution Model

The Maintainer records issues it observed directly or that a subagent reported in its return or digest.
doc-explorer may maintain the log when routed for bulk curation or deduplication cleanup.
Subagents do not write the log; they surface a compact Environment: <category>: <symptom> note in their return.

Workflow

Decide whether the issue is environmental (outside the work package's control) and whether it is fixable now.
- Fixable within the current package and scope → fix it; do not log it.
- Not fixable now → record it here.
Read docs/environment-issues.md if it exists; otherwise create it from tpl-environment-issues.md.
Match an existing entry by category plus normalized symptom.
- Match → increment occurrences, update last seen, adjust status or workaround if changed, and append a history line.
- No match → assign the next ENV-NNN ID and add both a summary row and an entry.
Keep entries short and evidence-based. Never invent a cause; record the exact symptom and the observed workaround.
Report the recorded ID back to the user or main loop.

Output Contract

Return only:

Recorded: ENV-NNN (new) | ENV-NNN (updated) | none
File: docs/environment-issues.md
Summary: one line: category + symptom
Next: stop | primary decision required

Write Boundary

Writes: docs/environment-issues.md only.
Does not write code, plans, or other docs.
Append-only history: never delete an entry; mark it mitigated or resolved instead.
No Git operations.

Rules

One issue per entry; do not bundle unrelated failures.
Deduplicate aggressively; a recurring issue increases its count instead of creating a duplicate.
Record a workaround even when the root cause is unknown.
Do not log a problem that is fixable within the current package; fix it instead.
Omit secrets, tokens, and personal data from evidence.
Do not scaffold docs/environment-issues.md when no issue exists.

Templates

tpl-environment-issues.md — canonical log structure and entry format.

Bundled files

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

tpl-environment-issues.md1 KB

Frequently asked questions

What does the Report Environment Issue AI skill do?

Record environment, harness, or tooling issues that block or degrade agent work into an append-only, deduplicated log so the environment can be improved incrementally.

Why use Report Environment Issue on TypingMind?

Because you install it once and use it with any model. Report Environment Issue 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 Report Environment Issue in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/DasDigitaleMomentum/opencode-processing-skills/tree/main/skills/report-environment-issue. 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 Report Environment Issue?

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 Report Environment Issue?

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

Is the Report Environment Issue AI skill free?

Yes. It is published on GitHub by DasDigitaleMomentum under the MIT license. 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

Discord Clawd

openclaw

OrganizationPopular

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Gitcrawl

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Graincrawl

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Skill: Report Environment Issue

When to Use

Execution Model

Workflow

Output Contract

Write Boundary

Rules

Templates

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now