Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/issue-report-report-template
Nested lingtai-issue-report reference for the report skeleton — subject/title format, the structured body sections (what's wrong, where, reproduction, expected vs actual, severity, suggested fix), and how to send it via LingTai email or the human's active channel. Read this when you are ready to assemble the report.
Passed 17 of 22 test cases with the skill, and 8 of 22 without it.
and 9 more in the full report
10 fixed7 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to file a report about a data corruption bug in the storage worker component. Many engineers usually title these 'Bug: Storage failure'. Create the email subject line following our internal standard.
| Checked | Without skill | With skill |
|---|---|---|
| The subject line starts with [Issue Report] followed by a one-line summary | Missed | Passed |
The instructions your model reads when the skill loads.
This is a nested lingtai-issue-report reference: the canonical structure for an issue report — subject/title, body sections, and how to deliver it through the right channel before any filing decision.
Send the report as a mail message with a clear subject and a structured body. Use this skeleton:
Subject: [Issue Report] <one-line summary>
## What's wrong
<concise statement of the problem — one paragraph>
## Where
- Component: <skill name / capability name / preset name / procedure section>
- File or URL (if known): <path or URL>
## Reproduction
<exact steps you took, exact tool calls, exact responses you got. Include
verbatim error messages, status codes, or contradictory text.>
## What you expected
<what the docs/skill led you to expect>
## What actually happened
<what you observed instead>
## Severity
<one of: blocking | major | minor | cosmetic>
- blocking — agents cannot complete the affected workflow at all
- major — a documented feature is broken or absent; workaround exists but costs time
- minor — incorrect detail; doesn't break workflows but misleads new agents
- cosmetic — typo, formatting, broken link in a doc
## Suggested fix (optional)
<if you have a concrete suggestion, include it. otherwise omit this section.>
Keep the section headers verbatim — they double as the GitHub-flavored markdown issue body later, and GFM renders them cleanly. The title used for filing is your Subject line minus the [Issue Report] prefix.
test cases passed, vs 8 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.