Skip to content
TrustedSkillsbeta
Back to all skills

Write Issue

Official
tldraw·vlatest·testing

Automatically generate clear, concise issue reports from tldraw diagrams, detailing problems and proposed solutions.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tldraw/tldraw --skill write-issue -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

tldraw

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned tldraw/tldraw at fdd9b4dee0.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 124 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows an AI agent to generate issue reports based on provided information. It can create structured text suitable for bug tracking systems or project management tools, summarizing problems and potential solutions. The output is designed to be clear, concise, and actionable for developers or other stakeholders.

When to use it

  • You need to quickly document a software bug encountered during testing.
  • A user reports an issue, and you want to generate a preliminary report.
  • You're summarizing feedback from multiple sources into a single, organized issue.
  • You want to create a structured record of a problem for future reference or escalation.

Key capabilities

  • Issue Report Generation: Creates formatted text representing issues.
  • Structured Output: Produces output suitable for bug tracking systems.
  • Summarization: Condenses information into concise reports.

Example prompts

  • "Write an issue report about the login button not working on mobile."
  • "Generate a bug report based on this user feedback: 'The app crashed when I tried to upload a large file.'"
  • “Create an issue for the broken link on the homepage, including steps to reproduce.”

Tips & gotchas

The quality of the generated issue depends heavily on the clarity and detail provided in the input. Providing context like reproduction steps or error messages will lead to more useful reports.