Run any Skill in Manus with one click

$pwd:

issue

Name: Issue
Author: tldraw

// Create and research a GitHub issue in the tldraw repository from a user description. Use when the user invokes issue, asks to create an issue, report a bug, file a feature request, or add research to a new issue.

Run Skill in Manus

$ git log --oneline --stat

stars:47,209

forks:3,233

updated:April 27, 2026 at 14:22

SKILL.md

readonly

name	issue
description	Create and research a GitHub issue in the tldraw repository from a user description. Use when the user invokes issue, asks to create an issue, report a bug, file a feature request, or add research to a new issue.

Issue

Create a GitHub issue on tldraw/tldraw from a user description, then research it.

Use ../write-issue/SKILL.md as the standards reference for issue titles, bodies, types, labels, and triage conventions.

Workflow

Gather context:
- User's issue description.
- Current branch: git branch --show-current.
- Recent issues: gh issue list --repo tldraw/tldraw --limit 5 --json number,title --jq '.[] | "#\(.number) \(.title)"'.
Do a quick codebase investigation:
- Search for relevant files, functions, or patterns mentioned in the description.
- Identify likely affected packages, apps, or examples.
- Note obvious causes, related issues, or existing code paths.
For visual bugs, identify a reproduction target when possible:
- Examples app: localhost:5420 from yarn dev.
- tldraw.com app: localhost:3000 from yarn dev-app.
- Docs site: localhost:3001 from yarn dev-docs.
- If screenshots are useful but not feasible locally, ask the user for screenshots and specific reproduction details.
Write the issue title and body using ../write-issue/SKILL.md.
Create the issue:

gh issue create --repo tldraw/tldraw --title "..." --body "..."

Set the issue type through GitHub GraphQL when possible, since gh issue create --type is not reliable across versions.
Assign a milestone only when there is a clear fit:
- Improve developer resources for examples, documentation, comments, starter kits, and npm create tldraw.
- Improve automations for GitHub Actions, review bots, CI/CD, and automation work.
Share the issue URL with the user immediately after creation.
Do deeper research after creation:
- Identify relevant files and line numbers.
- Explain the root cause for bugs.
- Summarize architecture context and related code.
- Note edge cases, testing needs, and likely implementation risks.
Add the research as an issue comment:

gh issue comment <issue-number> --repo tldraw/tldraw --body "..."

Rules

Always create the issue before doing deep research so the user can track it.
Follow ../write-issue/SKILL.md for all issue content standards.
Do not include AI attribution in issue titles, bodies, comments, or metadata.

related-skills.json

same repository

tldraw-migrate.md

from "tldraw/tldraw"

Migrate a project to a newer version of the tldraw SDK. Use when upgrading tldraw packages, fixing TypeScript errors after a tldraw upgrade, or when the user mentions tldraw migration.

2026-05-2147.2k

write-pr.md

from "tldraw/tldraw"

Reference 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.

2026-05-2147.2k

write-release-notes.md

from "tldraw/tldraw"

Writing release notes articles for tldraw SDK releases. Use when creating new release documentation, drafting release notes from scratch, or reviewing release note quality. Provides guidance on structure, voice, and content for release files in `apps/docs/content/releases/`.

2026-05-0647.2k

pr-walkthrough.md

from "tldraw/tldraw"

Create a narrated video walkthrough of a pull request with code slides and audio narration. Use when asked to create a PR walkthrough, PR video, or walkthrough video.

2026-04-2847.2k

clean-copy.md

from "tldraw/tldraw"

Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when asked to make a clean copy branch, clean up commit history by replaying work, or rebuild a branch as reviewable commits.

2026-04-2747.2k

commit-changes.md

from "tldraw/tldraw"

Create a git commit for the current changes. Use when asked to commit changes, make a commit, generate a commit message, or commit the current worktree with optional user-provided context.

2026-04-2747.2k

package.json

"author": "tldraw"

"repository": "tldraw/tldraw"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

Issue

Create a GitHub issue on tldraw/tldraw from a user description, then research it.

Use ../write-issue/SKILL.md as the standards reference for issue titles, bodies, types, labels, and triage conventions.

Workflow

Gather context:

User's issue description.
Current branch: git branch --show-current.
Recent issues: gh issue list --repo tldraw/tldraw --limit 5 --json number,title --jq '.[] | "#\(.number) \(.title)"'.

Do a quick codebase investigation:

Search for relevant files, functions, or patterns mentioned in the description.
Identify likely affected packages, apps, or examples.
Note obvious causes, related issues, or existing code paths.

For visual bugs, identify a reproduction target when possible:

Examples app: localhost:5420 from yarn dev.
tldraw.com app: localhost:3000 from yarn dev-app.
Docs site: localhost:3001 from yarn dev-docs.
If screenshots are useful but not feasible locally, ask the user for screenshots and specific reproduction details.

Write the issue title and body using ../write-issue/SKILL.md.

Create the issue:

gh issue create --repo tldraw/tldraw --title "..." --body "..."

Set the issue type through GitHub GraphQL when possible, since gh issue create --type is not reliable across versions.

Assign a milestone only when there is a clear fit:

Improve developer resources for examples, documentation, comments, starter kits, and npm create tldraw.
Improve automations for GitHub Actions, review bots, CI/CD, and automation work.

Share the issue URL with the user immediately after creation.

Do deeper research after creation:

Identify relevant files and line numbers.
Explain the root cause for bugs.
Summarize architecture context and related code.
Note edge cases, testing needs, and likely implementation risks.

Add the research as an issue comment:

gh issue comment <issue-number> --repo tldraw/tldraw --body "..."

Rules

Always create the issue before doing deep research so the user can track it.

Follow ../write-issue/SKILL.md for all issue content standards.

Do not include AI attribution in issue titles, bodies, comments, or metadata.

issue

Issue

Workflow

Rules

More from this repository

More from this repository

Issue

Workflow

Rules