Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Writing and maintaining GitHub issues · tldraw | DecimalAI

productivityby tldraw

Writing and maintaining GitHub issues

tldraw/write-issue

Source tldraw/tldraw ↗License NOASSERTION

Reference standards for writing and maintaining GitHub issues in the tldraw repository. Use as supporting guidance when another skill or workflow needs issue title, body, type, label, or triage standards.

SkillScore91Maintained

Automatic

Project Management pack

Last verified 8/7/2026

What it changes

Passed 21 of 23 test cases with the skill, and 10 of 23 without it.

Without skill43%

With skill91%

Checks it passed that the model alone missed

The issue title uses sentence case.
The issue applies at most two labels.
The designated issue type is Example.

and 12 more in the full report

11 fixed10 passed either way2 still failing0 broke

Pass-rate lift: +48 pp
Tokens: +31%
Agent turns: 0%
Response time: -56%

Model gemini-3.6-flashMeasured 8/7/2026v121 of 23 cases passed with skill

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/tldraw-write-issue/SKILL.md https://app.decimal.ai/s/tldraw-write-issue/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add tldraw-write-issue, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/tldraw-write-issue/ and pins it in .decimal/skills.lock

decimalai skills add tldraw-write-issue

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/tldraw-write-issue/SKILL.md https://app.decimal.ai/s/tldraw-write-issue/SKILL.md

Raw file: /s/tldraw-write-issue/SKILL.md ↗ · machine-readable summary at /s/tldraw-write-issue.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 11

Prompt

We need to log a request for a new SDK code example showing custom shape creation in tldraw/tldraw. Which GitHub issue type should be assigned?

What was checked, without and with the skill
Checked	Without skill	With skill
The designated issue type is Example.	Missed	Passed

case-09 · gemini-3.6-flash · 8/7/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md118 linessingle file

Writing and maintaining GitHub issues

Standards for issues in tldraw/tldraw.

Title standards

Sentence case - Capitalize only the first word and proper nouns
No type prefixes - Use GitHub issue types, not Bug:, Feature:, [Bug], etc.
Imperative mood for enhancements - "Add padding option" not "Adding padding option"
Descriptive for bugs - Describe the symptom: "Arrow bindings break with rotated shapes"
Specific - Readable without opening the issue body

Good titles

Arrow bindings break with rotated shapes
Add padding option to zoomToFit method
Pinch zoom resets selection on Safari

Bad titles

Bug: arrow bug (prefix, vague)
[Feature] Add new feature (prefix, vague)
Not working (vague)

Title cleanup transformations

Remove prefixes: Bug: X → X
Fix capitalization: Add Padding Option → Add padding option
Use imperative: Adding feature X → Add feature X
Be specific: Problem → [Describe the actual problem]
Translate non-English titles to English

Issue types

Set via the GitHub GraphQL API after creating the issue (the --type flag is not reliably supported):

Type	Use for
`Bug`	Something isn't working as expected
`Feature`	New capability or improvement

Track record

Benchmark

21 / 23

test cases passed, vs 10 / 23 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

tldraw / tldraw

skills/write-issue/SKILL.md

View on GitHub ↗

License NOASSERTIONImported 8/3/2026Version v1

Other skills for the same job

Published skills whose descriptions closely match this one, with their headline benchmark lift.

tldraw/write-prReference standards for writing pull request titles and descriptions in the tldraw repository. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.Close match+43 pp pass-rate lift

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Writing and maintaining GitHub issues

Title standards

Good titles

Bad titles

Title cleanup transformations

Issue types

Track record

Benchmark

Adoption

SkillSafety

Source

Other skills for the same job

Related skills