Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/lingtai-issue-report
Protocol router for reporting bugs, stale info, missing capabilities, or design issues you spot in any LingTai skill, capability, preset, or system behavior. Enter through this router, then load the one nested reference you need — evidence-checklist (when to report, what evidence to collect, secret hygiene), report-template (the report body/title structure), or filing-flow (human consent, the gh CLI path, and the paste-ready fallback). You always assemble a structured report and ask the human fo
Passed 18 of 22 test cases with the skill, and 12 of 22 without it.
and 4 more in the full report
6 fixed12 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
The draft report for a LingTai issue is written and approved. I am ready to evaluate submission methods and execute the filing flow. Which reference file path governs this step?
| Checked | Without skill | With skill |
|---|---|---|
| Directs the user to reference/filing-flow/SKILL.md. | Missed | Passed |
The instructions your model reads when the skill loads.
This is a reference router. You use the LingTai system as a real user all day — its skills, capabilities, and procedures — so you are uniquely positioned to notice problems humans miss. When you notice something wrong, surface it. This skill is the protocol: enter through this router, pick the one nested reference matching where you are in the report lifecycle, and read that leaf for the full procedure.
Two rules hold across every path and every leaf:
gh is authenticated and you have a shell, per-issue consent is non-negotiable. If they decline, drop it — no nagging, no auto-retry.GH_TOKEN stays in the env of the single command that needs it. Redact before you quote.The nested references elaborate these; they never weaken them.
- name: issue-report-evidence-checklist
location: reference/evidence-checklist/SKILL.md
description: When an observation is worth reporting (and when it isn't), what evidence to capture verbatim, and how to keep secrets out of the report.
- name: issue-report-report-template
location: reference/report-template/SKILL.md
description: The report skeleton — subject/title, the structured body sections, sending it via mail to your parent and the human, and which repo to target.
- name: issue-report-filing-flow
location: reference/filing-flow/SKILL.md
description: The filing decision — human consent boundary, the read-only gh probe, Path A (direct gh filing) and Path B (paste-ready handoff), token hygiene, and proactive surfacing.
You will usually move through all three in order, but read one leaf at a time — don't pull the whole protocol into context at once.
| Where you are | Read | What it covers |
|---|---|---|
| Just noticed something | reference/evidence-checklist/SKILL.md | Whether it's report-worthy, the evidence to capture before it's gone, scrubbing secrets |
| Ready to write it up | reference/report-template/SKILL.md | The body/title structure, and mailing it to your parent and the human |
| Time to file | reference/filing-flow/SKILL.md | The read-only gh probe, the human's permission, then Path A filing or Path B handoff |
Found a bug or issue? If you encounter any problems with this skill, load the
lingtai-issue-reportskill and follow its instructions to report it.
test cases passed, vs 12 / 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.