agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/linear/SKILL.md

linear

Skill0 starsChanged 8 months agoMITView on GitHub

Use when the user wants to read, create, triage, or update issues, projects, labels, cycles, or team workflows in Linear; use the current host's Linear connector or MCP integration, read first for context, then batch the writes.

83 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-deep-links, helium-mcp and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ComposioHQSkill

    agent-deep-links

    Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

    Also in 3 projects that use this

  • ComposioHQSkill

    helium-mcp

    Search real-time news with bias scoring, get live stock/ETF/crypto data with AI analysis, ML options pricing, balanced news synthesis, and meme search via the Helium MCP server.

    Also in 3 projects that use this

  • petestewartSkill

    datadog-logs

    Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.

    Also in 3 projects that use this

  • OpenAISkill

    pull

    Also in 5 projects that use this

  • SentrySkill

    datadog

    Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.

    Also in 4 projects that use this

  • +7 more from ComposioHQ

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 79 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for Linear issue triage, project updates, sprint planning, workload review, and documentation-linked follow-up work.

    line 9
  2. Distinctive:

    Use the current host's Linear connector or MCP integration to read context before making changes.

    line 13
  3. Distinctive:

    Keep requests reusable across product, engineering, and operations workflows.

    line 20
  4. Distinctive:

    Do not update issues, projects, or labels before the target team or project is clear.

    line 23
  5. Distinctive:

    Do not pretend a write succeeded without tool output confirming the mutation.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 79 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Linear

Intent

  • Use for Linear issue triage, project updates, sprint planning, workload review, and documentation-linked follow-up work.

Default operating pattern

  1. Confirm the workspace scope first: team, project, cycle, assignee, labels, or issue identifiers.
  2. Use the current host's Linear connector or MCP integration to read context before making changes.
  3. Group related reads together, then batch related writes together so the user can understand the change set.
  4. For create or update flows, make the target state explicit: status, priority, owner, due date, labels, and linked issues or projects.
  5. End with a concise handoff: what changed, what still needs confirmation, and the next likely Linear action.

Pack fit

  • Included in: knowledge-ops
  • Keep requests reusable across product, engineering, and operations workflows.

Boundary

  • Do not update issues, projects, or labels before the target team or project is clear.
  • Do not pretend a write succeeded without tool output confirming the mutation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free