Claude Skills by staticaland

Reference for writing any document an agent consumes - a skill, an `AGENTS.md` / `CLAUDE.md`, a doc reached by a pointer. The packaging differs; the writing does not: the same levers make each one predictable - the agent taking the same _process_ every run, not producing the same output. When the document you're writing is a skill, read [`SKILL-MECHANICS.md`](SKILL-MECHANICS.md) for frontmatter, invocation choice, and router skills.

Reference for writing any document an agent consumes - a skill, an `AGENTS.md` / `CLAUDE.md`, a doc reached by a pointer. The packaging differs; the writing does not: the same levers make each one predictable - the agent taking the same _process_ every run, not producing the same output. When the document you're writing is a skill, read [`SKILL-MECHANICS.md`](SKILL-MECHANICS.md) for frontmatter, invocation choice, and router skills.

A cooldown holds back package versions published less than N days ago, so researchers catch a compromised release before it reaches the project. A cooldown binds at **resolution** - the moment a version range becomes a concrete version. Installing from an existing lockfile resolves nothing, and an update bot's cooldown only delays its pull requests. Cover every site that resolves, not only the one the user asked about. [cooldowns.dev](https://cooldowns.dev/) is the source of truth. Consult it...

An install command either **resolves** - reads the ranges in the manifest, picks versions, and writes the lockfile - or is **frozen**: it installs the lockfile exactly and fails when it cannot. `npm install` resolves even with a lockfile sitting beside it. `npm ci` is frozen. Sort every install site by intent. A site that reproduces an environment - CI, an image build, a deploy, a contributor's first setup - belongs on the frozen side. Anything that moves the lockfile forward is a **resolving...

Installing a package should copy files. A `preinstall`, `install`, or `postinstall` script makes it run code instead - with your shell, your environment, your CI token, and your `~/.ssh`, before anyone has read a line of the package. The Shai-Hulud worm propagated exactly this way, out of a transitive dependency nobody chose. Almost no package needs it. In one 437-package tree, two do: `esbuild` and `fsevents`, both distributing native binaries. That ratio is what makes the fix cheap - **deny...

Add or extend Renovate with a seven-day minimum release age and immutable updates: lock files and integrity hashes, GitHub Action SHAs, and container digests. Use when adopting Renovate, replacing another update bot, covering missing manifests, or updating tools, images, actions, or custom files.

Transform content into Anki flashcards optimized for long-term retention, following Andy Matuschak's [prompt-writing principles](https://andymatuschak.org/prompts/).

Look at a module, config, workflow, or design with fresh eyes: ignore how it works today, propose the simplest design that could serve the same purpose, and keep the proposals that survive the constraints that shaped the current one. Use when the user asks why something is so complicated, wants a first-principles or fresh-eyes review, or asks "why don't we just...".

GitHub Actions runs the steps of a job in sequence. The `background` keywords change this. The model is the shell: `background: true` is `&`, and `wait` is `wait`. This document obeys ASD-STE100 Simplified Technical English. Write all prose that you add to it in the same style.

GitHub Actions shows a fallback wherever a name is missing: - a workflow falls back to its file path - a job falls back to its job id - a step falls back to its `run` command or action reference A name turns the log line into documentation, while the fallback leaves it as source code.

GitHub Actions parses workflow YAML with anchors and aliases since [18 September 2025](https://github.blog/changelog/2025-09-18-actions-yaml-anchors-and-non-public-workflow-templates/). GitHub rejects the merge key (`<<`), so an alias overrides nothing: a copy that differs by one key is out of an anchor's reach.

Kontrollert norsk er teknisk norsk med et fast begrepsapparat og faste skriveregler. Skriv bokmål, med mindre brukeren ber om nynorsk.

Cite the factual claims a skeptical reader would challenge, using sources found through web search and Markdown footnotes. The user's request sets the scope; without one, cite the claims the argument rests on, not every fact. Preserve the text's wording and structure apart from the citations.

Strip references the reader cannot see from prose and code comments.

Revise text for clarity, scannability, and direct action by busy readers.

Create a GitHub pull request. Use when the user asks to open, create, or submit a PR, when work is ready for review, or whenever gh pr create would otherwise be run.

Upload an image or video to a GitHub issue, pull request, or comment with the GitHub CLI's `--attach` flag, and control where it renders in the body. Use when attaching or embedding a screenshot, screen recording, diagram, or GIF through `gh`, when a body already written references a local image path, or when a `gh` attachment upload fails.

Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.

Conduct a retrospective on a coding session.

Refactor one target skill so its core workflow stays in `SKILL.md` and conditional detail loads only when it applies. Every fact, example, and caveat in the old files survives the move. Apply the refactor. When the user asks for analysis only, stop after step 2 and report the proposed layout.

Delete the sentences in a skill that change no behavior - asides,

Classify every step of a target skill as `SCRIPT` (deterministic) or `LLM` (judgment), then propose a script interface and a simplified SKILL.md. Deliver the analysis in the response. Write the script and simplified SKILL.md to disk only when the user asks to apply the changes.

[mise](https://mise.jdx.dev/) declares a project's whole toolchain in one committed `mise.toml`, so a laptop, a container, and CI run the same versions. Writing the TOML takes minutes. Taking **inventory** is what takes time: the toolchain already exists, spread across CI workflows, Dockerfiles, task runners, READMEs, and one version file per language. <!-- vale ai-tells.FigurativeOwns = NO --> <!-- The second bullet defines "owns" as a term for the version this file is the source for, so the...

Use when setting up or running hooks with prek in any repository. prek is a Rust drop-in alternative to pre-commit for running Git hooks that check, format, lint, and validate code and repository files. Prefer it when speed, workspace mode, built-in hooks, shared toolchains, or native TOML configuration matter.