linear-issues-write
Create and Update Linear Issues
Manual issue entry slows project workflows and introduces inconsistent fields. This skill creates and updates Linear issues through documented command-line options.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "linear-issues-write" from https://skillstore.io/skills/bind-linear-issues-write.md and its manifest at https://skillstore.io/api/skills/bind-linear-issues-write/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "linear-issues-write". Create a high-priority Engineering issue titled "Fix login timeout" with the Bug label.
Expected outcome:
Created an Engineering issue titled "Fix login timeout" with high priority and the Bug label.
Using "linear-issues-write". Move ENG-123 to In Progress, assign Taylor, and add the Urgent label.
Expected outcome:
Updated ENG-123 to In Progress, assigned Taylor, and added the Urgent label.
Using "linear-issues-write". Unassign ENG-456 and remove it from its project.
Expected outcome:
Updated ENG-456 with no assignee and no project.
Security Audit
Medium RiskAll 37 static findings are false positives caused by Markdown formatting, a documentation link, or documented credential prerequisites. However, the package references issue-writing executables that are absent from the audited files, so their command handling, network behavior, and credential use cannot be verified.
Confirmed security concerns (1)
Risk Factors
🔑 Env variables (3)
⚙️ External commands (29)
🌐 Network access (1)
📁 Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/bind-linear-issues-write/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bind-linear-issues-write?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bind-linear-issues-write?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bind-linear-issues-write/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bind-linear-issues-write.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Bind. (2026). linear-issues-write security audit report (audit version 9) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/bind-linear-issues-write/audits/9BibTeX citation
@techreport{bind-bind-linear-issues-write-2026,
author = {Bind},
title = {linear-issues-write security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/bind-linear-issues-write/audits/9},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "linear-issues-write security audit report (audit version 9)"
version: "1.0.0"
type: report
authors:
- name: "Bind"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/bind-linear-issues-write/audits/9"
identifiers:
- type: other
value: "skillstore:bind-linear-issues-write:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Capture Engineering Work
Create prioritized issues with labels, assignees, and project context from development discussions.
Maintain Sprint Status
Update issue status, priority, ownership, and labels as sprint work changes.
Automate Issue Intake
Generate consistent Linear issues from operational requests and return machine-readable results.
Try These Prompts
Create a Linear issue titled "[title]" for the [team] team. Show the planned fields before writing.
Create a Linear issue for [team] with title [title], description [description], priority [0-4], labels [labels], assignee [name], and project [project].
Update Linear issue [issue-id] to status [status], assign it to [name], set priority [0-4], and add labels [labels]. Confirm the target issue first.
Prepare commands to update these Linear issues: [issue list and changes]. Validate every identifier, show each proposed mutation, and execute only after approval.
Best Practices
- Review the issue identifier and proposed fields before every write operation.
- Use the minimum Linear API permissions required for issue management.
- Use machine-readable output when another tool must consume the result.
Avoid
- Do not store or paste the Linear API key in prompts, issue text, or command output.
- Do not perform broad updates without reviewing every target issue and field change.
- Do not replace all labels when the intent is only to add labels.