Independent reviews. IonBin has no partnerships with the tools on this page and was not paid for these listings. Our evaluations are our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Source reviewedProject managementExplored

OpenAI / skills/.curated/linear/SKILL.md

Linear

A step-by-step routine for working in Linear through its MCP server: read first, then create or update, then summarize.

Read upstream skill GitHub repository Add to comparison

Source reviewed · reviewed · Named sources were inspected. No runtime results are established by this label.

01 / Task fit

Where it may help.

These are intended uses indicated by the upstream material. They are not measured outcomes.

  • Issue triage and status reports in Linear
  • Agents that should read before they write

What it is

The Linear skill tells an agent how to use Linear's MCP server for issues, projects, cycles, comments and documents. It sets a fixed order: clarify the goal, read the relevant issues, make changes in batches, then report what changed and what's left. It lists the MCP tools by area and gives example routines such as bug triage and sprint planning.

Why you might use it

Use it when an agent manages Linear for you and you want reads before writes and an explanation before bulk changes. Pair it with a read-only connection while you review, and switch to write access only for changes you approve.

Put it in context.

Illustrative requests and outputs to review. These examples are separate from the recorded evaluation below.

Triage new bugs

Example request

List this week's unlabeled bugs in the Platform team, suggest a priority and label for each, and wait for my approval before changing anything.

What to look for. A table of suggested priorities and labels, followed by updates only after approval.

Before you rely on it. The skill's own routines include applying changes. Ask for approval explicitly, or use Linear's read-only endpoint.

Write a cycle summary

Example request

Summarize the last completed cycle: what shipped, what moved to the next cycle and any blocked issues.

What to look for. A short report built from Linear data, with issue links.

Before you rely on it. Summaries are only as current as the issues. Stale statuses lead to a stale report.

02 / Setup & access

What it asks of your environment.

Requirements

  • A Linear workspace and the Linear MCP server connected over OAuth. The setup steps are Codex-specific.
  • Access to the teams and projects involved.

Permissions & data access

  • Reads issues, projects, cycles, comments and documents the account can see.
  • Creates and updates issues, projects, labels and comments when asked.
Check the host, too.

Instructions alone do not enforce a sandbox. The agent host, connected tools and approvals determine what the skill can actually read, change or send.

03 / Things to check

Security concerns & practical limits.

These concerns follow from the reviewed sources. They describe possible exposure or required review; they are not confirmed vulnerabilities.

Review before use

Bulk changes can touch many issues

Routines such as smart labeling and workload balancing can change many issues at once. The skill says to explain grouping first; still approve each batch.

Limits and nuances

  • Source review of SKILL.md and the per-skill license only. No Linear workspace was connected and no issue was read or changed.
  • No triage-quality or planning result is claimed.

04 / Review record

What we checked. What’s still open.

Source reviewed

Recorded review scope

  • skills/.curated/linear/SKILL.md
  • skills/.curated/linear/LICENSE.txt
Not verified

Not tested or established

  • Source review of SKILL.md and the per-skill license only. No Linear workspace was connected and no issue was read or changed.
  • No triage-quality or planning result is claimed.
Review date
Source revision
49f948faa9258a0c61caceaf225e179651397431
Our relationship
Explored. Investigated through the recorded review. No use or replication is claimed.

Upstream content can change after review. A repository revision identifies source scope; it does not prove that every script, dependency or runtime behavior was tested. How freshness is handled.

Recorded evaluation / Source review

Results with their limits attached.

Completed within scope

Completed 4 bounded source checks on the pinned entrypoint and license. No skill workflow was executed.

Passed
4
Failed
0
Total recorded
4

These counts refer to the cases in this report. They are not a benchmark against other skills. A source review does not establish runtime behavior.

Read the evidence report

The report provides the case definitions, observations and baseline scope. Missing baselines or untested behaviors remain limitations.

Recorded environment

  • Pinned public UTF-8 sources fetched from raw.githubusercontent.com at the recorded commit and hashed with SHA-256.
  • Linux; Python 3.13.5 source-condition check. No account, credentials, private documents or live business data.
Recorded commands (2)

Commands document this evaluation. They are not setup instructions for your environment.

Read each pinned file listed in sourceManifest.
python3 r6_skills.py: check each recorded source condition and reconcile report counts.

Findings from this evaluation

Needs attention

Bulk changes can touch many issues

Routines such as smart labeling and workload balancing can change many issues at once. The skill says to explain grouping first; still approve each batch.

Observation

Read-first order

The workflow reads to build context before creating or updating anything.

Evaluation limitations

  • Source review of SKILL.md and the per-skill license only. No Linear workspace was connected and no issue was read or changed.
  • No triage-quality or planning result is claimed.

05 / Reuse & discovery

License, attribution & popularity.

Apache-2.0

Apache-2.0 license text inspected at this revision. Keep the license and any NOTICE when redistributing covered files. The services and accounts the skill uses have their own terms.

Why it is in this collection

GitHub displayed 28,155 stars for the openai/skills repository on the observation date. Repository-wide; not individual skill usage, quality or safety.

28,155 repository stars

Scope
Entire openai/skills repository, not this individual skill
Observed
Time window
Snapshot observed 2026-10-19
Discovery source ↗

Popularity and inclusion do not establish quality, compatibility or security. Counts belong to their named metric and date; they are not a current ranking.

06 / Follow the evidence

Go to the original.

  1. Pinned skill instructions github.com
  2. Pinned license github.com
  3. Repository (dated star count) github.com

IonBin’s source notes are independent assessments. Upstream authors retain their work and attribution. This page does not install or execute the skill.