Agent skill

Linear Maintenance

by evloghq in evloghq/evlog

Bi-weekly housekeeping pass over the evlog team's Linear backlog: labels, projects, priorities, stale triage, work that is done but still open, and anything misfiled next to its siblings.

MITAuto-check passedFrontend & Design

Install Linear Maintenance

skills CLI
$ npx skills add evloghq/evlog --skill linear-maintenance -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install evloghq/evlog linear-maintenance --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/evloghq/evlog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/evi/agent/skills/linear-maintenance .claude/skills/linear-maintenance && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
linear-maintenance
GitHub stars
1.9k
Token cost
~1.1k tokens
SKILL.md length
671 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Bi-weekly housekeeping pass over the evlog team's Linear backlog: labels, projects, priorities, stale triage, work that is done but still open, and anything misfiled next to its siblings.

  • Tasks that involve Static sites and blogs
  • SKILL.md covers Two halves, in order, The lenses, Grounding and Deliver
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Linear Maintenance is an agent skill from evloghq/evlog. Bi-weekly housekeeping pass over the evlog team's Linear backlog: labels, projects, priorities, stale triage, work that is done but still open, and anything misfiled next to its siblings. Applies the mechanically verifiable fixes and surfaces the rest as decisions. Load this when the linear-maintenance schedule fires, or when Hugo asks for a Linear clean-up, a backlog pass, or a triage consistency check.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Static sites and blogs. The repository describes itself as: Digging through logs is not observability. It's hope — wide events, structured errors, TypeScript-first, every runtime. The licence is MIT.

When your agent uses it

  • Tasks that involve Static sites and blogs

Example prompts

  • “/linear-maintenance”

What it can do on your machine

Read from SKILL.md and the folder at commit 59a105f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Linear Maintenance loads about 1.1k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 671 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from evloghq/evlog at commit 59a105f, republished under its MIT licence (© evloghq). 671 words, ~1,123 tokens.

Download SKILL.mdSave it as .claude/skills/linear-maintenance/SKILL.md (or your agent's skills folder).
name
linear-maintenance
description
Bi-weekly housekeeping pass over the evlog team's Linear backlog: labels, projects, priorities, stale triage, work that is done but still open, and anything misfiled next to its siblings. Applies the mechanically verifiable fixes and surfaces the rest as decisions. Load this when the linear-maintenance schedule fires, or when Hugo asks for a Linear clean-up, a backlog pass, or a triage consistency check.

Linear maintenance

A regular housekeeping sweep over the evlog team's Linear backlog so it stays readable and current between passes. The goal is a tidy, trustworthy backlog, not a census. Listing every issue is not the point; correcting the drift and flagging what needs a decision is.

Where the other skills draw the line: self-review owns the coherence and reach of the agent's own surface, repo-health-sweep owns the repository and docs, cost-watchdog owns gateway spend. This skill owns Linear housekeeping only, and stops there. When a pass finds evidence that shipped work is now live (a schedule, a skill, a merged PR), the finding belongs to this skill's "close it" bucket, not to building anything.

Two halves, in order

Apply what is mechanically verifiable. These are the unambiguous fixes, and they are the point of the run: the sibling set or the issue history is evidence enough that a write is correct. Apply them directly via linear__save_issue.

Surface what needs a judgement call about intent. Anything you cannot verify, or whose correct value is a matter of taste, stays open and is written down as a finding for Hugo. Never guess a decision that a sibling set or the issue history cannot support.

The lenses

Enumerate the open surface first: linear__list_issues on the evlog team, across states. Then for each item check:

  • Project: every open issue sits in the project its title and content point to, or in Triage if it is genuinely unplaced. An issue whose peers carry a project but it does not is a fix, not a finding.
  • Priority: an item In Progress should carry a priority consistent with its siblings; a Backlog item with no priority next to prioritized peers is inconsistent. A priority change that relies on an estimate of intent is a finding.
  • Label: every open issue carries one of the team's labels. A feature request with no label is a fix. A label that duplicates another, or has a single use, is a hygiene finding.
  • Stale: triage older than several months with no movement, parked next to a canceled sibling, or an investigation that outlived its question, is a finding (close it or kick it to the community).
  • Done but open: an item whose work already shipped in another issue, a schedule, or a merged PR, and is still open, is a close. Only when the shipped evidence is verifiable from the issue history or linked work.
  • Consistency: a true duplicate of a completed or archived sibling, a sub-issue misread as a duplicate, work whose state contradicts its neighbors.
Show full SKILL.md (245 more words)Show less

Grounding

  • Absence is proven by listing, never by recall. Before writing that a project, label or priority is missing, enumerate the real surface with linear__list_issues and the label list. A value you do not remember seeing is not a value that is absent.
  • Run before you assert. A "this is shipped" close is grounded in the issue history, a linked PR, or a live schedule that the issue thread or the repo confirms. If it could not be verified, it is a finding written as a question, not a close.
  • One counter-example kills a claim of inconsistency. Check the sibling set in the same project and state before declaring something misfiled.

Deliver

The report is a Linear document per run: the fixes already applied, and the open decisions each with the evidence and the question to resolve. Post one line per artifact to the thread, links inline. Then stop; do not read the report back to confirm it.

  • Mechanical fix, unambiguous → apply it with linear__save_issue and list it in the report under "applied".
  • Decision → a finding in the report under "left open", naming the evidence and the exact call to make. A finding that needs a decision Hugo has not asked you to take stays open; do not close it unilaterally.

Never invent a fix to fill the run, and never report a lens as clean when it ran and found nothing of note. A quiet pass is a real result: one line saying so.

© evloghq, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in apps/evi/agent/skills/linear-maintenance of evloghq/evlog.

Open the folder on GitHubat commit 59a105f

Compare with similar skills

Linear Maintenance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Linear Maintenance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linear Maintenance this skillevloghq/evlog1.9k—~1.1kAutomated safety check: PassMIT
Tabler Astro Dev Servertabler/tabler42k—~1.2kAutomated safety check: PassMIT
Create Docsvictorgarciaesgi/nuxt-typed-router4132 repos~2.8kAutomated safety check: PassMIT
Tabler Astro Component Scriptstabler/tabler42k—~2.1kAutomated safety check: PassMIT
Paperclip Pagepaperclipai/paperclip99k—~1kAutomated safety check: PassMIT
Kill AI Slopyetone/kill-ai-slop1.3k—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Starts the right Tabler dev server, keeps it from clashing with builds and verifies changes in the browser before a page or component is handed back.

    42k GitHub stars~1.2k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Create Docs

    victorgarciaesgi/nuxt-typed-router

    Create complete documentation sites for projects. An agent skill from victorgarciaesgi/nuxt-typed-router.

    413 GitHub starsUsed in 2 repos~2.8k tokens
    Frontend & DesignAuto-check passed
  • Rules for adding or fixing client-side scripts in Tabler's Astro components so the copied preview HTML stays readable, self-contained and runs in the right order.

    42k GitHub stars~2.1k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Paperclip Page

    paperclipai/paperclip

    Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host.

    99k GitHub stars~1k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Kill AI Slop

    yetone/kill-ai-slop

    Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project.

    1.3k GitHub stars~1.4k tokensUpdated 23 days ago
    Frontend & DesignAuto-check passed
  • Official

    Audit a documentation site for agent-friendliness: discovery, markdown delivery, crawlability, semantic structure, machine-readable surfaces, and content legibility.

    4.7k GitHub stars~1.8k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from evloghq/evlog

All 20 skills in this repo
  • Walks through adding a new built-in evlog drain adapter for an observability platform: source, build config, exports, tests, docs and PR scope.

    1.9k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Guides adding a new built-in enricher to the evlog package, covering the source, tests, docs, README, a related skill and a changeset.

    1.9k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Walks a contributor through adding a new HTTP framework integration to the evlog logging package: middleware source, build entry, exports, tests, example app and docs.

    1.9k GitHub stars~5k tokensUpdated yesterday
    Auto-check: notes
  • Walks through adding a new rule or framework adapter to `evlog map` in @evlog/cli, from the rule source and registry to types, tests, docs and the published skill.

    1.9k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Rules for writing and reviewing evlog docs, blog posts, READMEs, skills and AGENTS.md files, with separate review and rewrite roles, a house voice and a catalog of AI-sounding tells.

    1.9k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Before After

    evloghq/evlog

    Produce a before/after visual comparison of an evlog surface (landing, docs, telemetry, playgrounds) and share it as public Blob URLs.

    1.9k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

Questions about Linear Maintenance

What does Linear Maintenance do?

Bi-weekly housekeeping pass over the evlog team's Linear backlog: labels, projects, priorities, stale triage, work that is done but still open, and anything misfiled next to its siblings. Linear Maintenance is an agent skill from evloghq/evlog. Bi-weekly housekeeping pass over the evlog team's Linear backlog: labels, projects, priorities, stale triage, work that is done but still open, and anything misfiled next to its siblings.

When should I use Linear Maintenance?

Linear Maintenance fits situations like: tasks that involve Static sites and blogs.

How do I install Linear Maintenance in Claude Code?

Run `npx skills add evloghq/evlog --skill linear-maintenance -a claude-code`. Or copy the skill folder (apps/evi/agent/skills/linear-maintenance in evloghq/evlog) into .claude/skills/linear-maintenance in your project. Claude Code loads it when a task matches its description.

How do I install Linear Maintenance in Codex?

Run `npx skills add evloghq/evlog --skill linear-maintenance -a codex`. Or copy the skill folder (apps/evi/agent/skills/linear-maintenance in evloghq/evlog) into .agents/skills/linear-maintenance in your project. Codex loads it when a task matches its description.

Can I use Linear Maintenance in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add evloghq/evlog --skill linear-maintenance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linear-maintenance, .gemini/skills/linear-maintenance, .github/skills/linear-maintenance and .opencode/skills/linear-maintenance in your project.

What does Linear Maintenance need to run?

SKILL.md names no scripts, command-line tools or credentials: Linear Maintenance is instructions for the agent only.

Does Linear Maintenance access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Linear Maintenance safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Linear Maintenance use?

Linear Maintenance is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Linear Maintenance use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Linear Maintenance?

Skills that share tags, products or a category with Linear Maintenance: Tabler Astro Dev Server (tabler/tabler, 42k stars), Create Docs (victorgarciaesgi/nuxt-typed-router, 413 stars), Tabler Astro Component Scripts (tabler/tabler, 42k stars) and Paperclip Page (paperclipai/paperclip, 99k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linear Maintenance?

evloghq (a GitHub organization) maintains it in evloghq/evlog, which has 1,887 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 7, 2026.

Source: evloghq/evlog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.