linear-projects-write
Create and Update Linear Projects from the CLI
Managing Linear projects through the web interface is slow when you work in the terminal or automate workflows. This skill lets you create and update projects with simple commands, so you can manage project data directly from scripts and the command line.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "linear-projects-write" from https://skillstore.io/skills/bind-linear-projects-write.md and its manifest at https://skillstore.io/api/skills/bind-linear-projects-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-projects-write". Create a new Linear project named "Website Redesign" for the Engineering team.
Expected outcome:
Created project "Website Redesign" assigned to the Engineering team. The project is set to the planned status and has no lead or target date yet.
Using "linear-projects-write". Update the Linear project named "Website Redesign" to set its status to completed.
Expected outcome:
Updated project "Website Redesign". Its status is now completed. No other fields were changed.
Security Audit
SafeThis skill provides two documented CLI tools for creating and updating Linear projects through the official Linear SDK. The static analyzer produced 37 findings, but nearly all are false positives: the 29 'Ruby/shell backtick execution' hits are Markdown code fences and inline-code backticks in the SKILL.md documentation, not code that executes commands; the network hit is a hardcoded link to the bun.sh documentation site; and the environment and sensitive-file findings refer to the legitimate, well-documented LINEAR_API_KEY that the tool requires to authenticate with Linear. The API key is read from the environment or a project .env file per standard practice and is not exfiltrated or logged. No prompt injection, data exfiltration, or business-logic abuse was observed.
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-projects-write/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bind-linear-projects-write?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bind-linear-projects-write?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bind-linear-projects-write/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bind-linear-projects-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-projects-write security audit report (audit version 9) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/bind-linear-projects-write/audits/9BibTeX citation
@techreport{bind-bind-linear-projects-write-2026,
author = {Bind},
title = {linear-projects-write security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/bind-linear-projects-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-projects-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-projects-write/audits/9"
identifiers:
- type: other
value: "skillstore:bind-linear-projects-write:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Kick off a new initiative
A team lead creates a new project for an upcoming initiative, assigning it to the correct teams and setting the lead and target date in one command.
Automate project setup in scripts
A developer adds project creation to a provisioning script so that each new client engagement gets a standard Linear project without manual clicks.
Bulk status and date updates
An operations manager updates the status and target dates of several projects at the end of a planning cycle from a shell loop instead of the web app.
Try These Prompts
Create a new Linear project named "Website Redesign" for the Engineering team.
Create a Linear project named "Q1 Launch" for the Engineering and Product teams, with a target date of 2025-03-01 and priority high.
Update the Linear project named "Website Redesign" to set its status to completed.
Update the Linear project "Q1 Launch" to set the lead to "James Monroe" and a new target date of 2025-04-15, and return the result as JSON so I can log it.
Best Practices
- Store the LINEAR_API_KEY in a git-ignored .env file or the environment so it is never committed to source control.
- Prefer the project UUID over a name when updating in scripts, because names can match more than one project.
- Use the --json flag when the output feeds another program, and read the fields you need from the returned data.
Avoid
- Do not paste the API key directly into commands or commit it to a shared repository.
- Do not rely on a short partial name match for a critical update, since it may select the wrong project.
- Do not expect this skill to manage issues, cycles, or comments; it handles projects only.