housekeeping SKILL.md skillA
housekeeping from langfuse/langfuse is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add langfuse/langfuse/housekeeping@git:20260911.a85d3ecPins git:20260911.a85d3ec in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- langfuse/langfuse
- Path
.agents/skills/housekeeping/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260911.a85d3ec, committed Sep 11, 2026
- First version recorded
- Jun 15, 2026
- Size
- 8,539 bytes
- Repository stars
- 37,634
- License
- a license file GitHub does not identify
Triage an engineer's work queue across Linear, Pylon, and GitHub. Use for assigned, urgent, waiting, or stale issues, support follow-ups, and PR reviews.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Housekeeping ## Scope Review live work queues and recommend what the engineer should do next. Triage is a recommendation, not an action: every state change this skill produces — assigning, moving, closing, cancelling, re-prioritising — belongs to the engineer, so the output is a table they act on. Use this skill for: - Linear issue triage, assigned work, waiting issues, urgent-priority issues, and stale cleanup candidates. - Pylon customer issues that need an engineer response, engineering follow-up, linked-ticket check, or stale close recommendation. - GitHub pull requests where the engineer is a direct or team reviewer. Do not use this skill for deep root-cause debugging, implementation, incident response, or broad roadmap planning unless the user explicitly asks to continue from a recommendation into that work. ## Required Behavior Every reviewed item must include an action recommendation. If evidence is insufficient, recommend the next inspection step rather than leaving the action blank. Use these action labels: - `act-now`: needs attention today. - `quick-win`: likely under 15 minutes. - `todo`: should be picked up in the next 1-2 weeks. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2dzt4ijnbwqrk73z/16d1d0c819d18d8df4452e269fba4355db8e7626af10560023508ae0b866e964.json
Then /plugin install housekeeping@markdownregistry-2dzt4ijnbwqrk73z in Claude Code. It installs git:20260911.a85d3ec, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add langfuse/langfuse/housekeeping@sha256:16d1d0c819d18d8dThe line at the top of this page pins the label git:20260911.a85d3ec, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2dzt4ijnbwqrk73z)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in langfuse/langfuse/housekeeping since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of housekeeping from somewhere else? Ask it: where did my housekeeping come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Jun 15, 2026 and Sep 11, 2026, about one every 29 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260911.a85d3ec latest | 2026-09-11 | a85d3ec | 8,539 B | A | view · diff |
| git:20260904.0b8d7eb | 2026-09-04 | 0b8d7eb | 8,568 B | A | view · diff |
| git:20260729.6d2988f | 2026-07-29 | 6d2988f | 7,735 B | A | view · diff |
| git:20260615.9856a4c | 2026-06-15 | 9856a4c | 7,920 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/housekeeping/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8539 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
langfuse/langfuse · 37,634 stars · license a license file GitHub does not identify · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2dzt4ijnbwqrk73z GET https://markdownregistry.com/api/v1/resolve?ref=langfuse/langfuse/housekeeping GET https://markdownregistry.com/api/v1/blob/16d1d0c819d18d8df4452e269fba4355db8e7626af10560023508ae0b866e964
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from langfuse/langfuse
Every file in langfuse/langfuse
Other files named housekeeping
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.